napierzaza

Okay, looking at this schematic: http://ucapps.de/mbhp/mbhp_sid_c64_psu.pdf Is this going to be adequate voltage for the 6851 or is this only for the lower voltage varieties?

I'm talking to the MMJ developer, which is a free version of Mandolane (the java-midi port plugin). He needs information on what's being garbled. If you look at this post below Smash gives a good report of one Sysex message (upload request) that ends up being garbled to a note-on command. This is no longer a bug, but there are others. If anyone can help determine which Sysex messages are not working, I can forward them to the dev and he is willing to take a look. Thanks. http://www.midibox.org/forum/index.php/topic,9153.msg65336.html#msg65336 NOTE: Please make sure you have installed MMJ 0.85 from the humatic.de website. I was having trouble successfully uploading but now am having no problems whatsoever with the software. I thought I was using the most current before. So I'm relying on everyone else for any reports, I think it's worth it for a free midi-java plugin. http://www.humatic.de/htools/mmj.htm

Works perfectly.

Okay, it worked well, I was able to upload MIOS successfully, and then was able to upload the new software as well. Also I'd just like to say that the standard Detented2 setup of 1.1c works perfectly! There is not longer any strange seizing or jittering!!! I'm very excited now and I can begin learning how to use my FM. I guess I might have to do a little re-wiring for the core <--> USB module to work at its best, but anyways I think I'm mostly out of the woods now! THANKS VERY MUCH STRYD, AUDIOCOMMANDER AND TK!!!

Sorry, I know it's happening that way, but there are dual purposes to each post. But I agree, they are kind of merging.

Okay, I'll try it. Thanks TK. Heehee, it didn't occur to me about refreshing the page *slap myself*

Uploaded Midi128 firmware via the Sysex Librarian and it just hangs on startup. It says "MIOS V1.9f © 2007 T.Klose" and just stays there forever. Could this have been the reason that I bricked my FM? I used the out of date version of the hex2syx script and used the os_upload value

Yayy! This is good news, I was trying everything I could and double checking and felt like an idiot. It looks like I will have to reflash a PIC though, as I said it's now bricked since I uploaded MBHP 128 using the out of date script. Thankfully this is not that big a problem. BTW it still says 1_1b on the page, and it still downloads only that, but if you change the download link in your browser to "C" it works. Thanks TK

I saw that suggestion, and understand your recommendation (notes sent when not moved bad). However I don't really see what I can do IF IT IS doing that. And as of now I can't easily upload applications as I am still discussing the MMJ bugs with the developer. ... Uploaded Midi128 firmware via the Sysex Librarian and it just hangs on startup. It says "MIOS V1.9f © 2007 T.Klose" and just stays there forever.

Actually, I am using a PIC18F452. Okay, so I uploaded it with no problem using the Sysex librarian. I'll use it in the future. Sounds like it's MMJ that is a problem. Thanks very much. Does the 4620 provide any improvement for a FM based synth?

ERROR: you are trying to overwrite the MIOS address range Check your main.asm file -- code should be included *after* mios_tables.inc! If it was your intention to convert a MIOS .hex file, add -os_upload! I tried using that and I get this, I don't really want to keep following these additions to the commands: Block 000000-0003FF allocated - Checksum: 14 Block 003000-0033FF allocated - Checksum: 24 Block 003400-0037FF allocated - Checksum: 6E Block 003800-003BFF allocated - Checksum: 2D Block 003C00-003FFF allocated - Checksum: 03 Block 004000-0043FF allocated - Checksum: 6A Block 004400-0047FF allocated - Checksum: 5F Block 004800-004BFF allocated - Checksum: 33 Block 004C00-004FFF allocated - Checksum: 37 Block 005000-0053FF allocated - Checksum: 61 Block 005400-0057FF allocated - Checksum: 29 Block 005800-005BFF allocated - Checksum: 52 Block 005C00-005FFF allocated - Checksum: 5B Block 006000-0063FF allocated - Checksum: 67 Block 006400-0067FF allocated - Checksum: 3E Block 006800-006BFF allocated - Checksum: 20 Block 006C00-006FFF allocated - Checksum: 6E Block 007000-0073FF allocated - Checksum: 59 Block 007400-0077FF allocated - Checksum: 0F Block 007800-007BFF allocated - Checksum: 54 ERROR: you are trying to overwrite the Bootstrap Loader range! If you are using a 64k PIC device, add -mem_64k!

it's in neither the FM nor the SID application folders. Nor is it linked anywhere in the hex2syx howto.

Okay well, I tried the libararian, but I'm not uploading a syx file, I'm uploading a hex file. So it just doesn't allow me to load the hex file at all.

So far I have tried all the possible DETENTED types and they all behave negatively. 2 and 3 more or less behave the same and the 1 have not worked whatsoever (more spastic). At this point I really have no idea what I can do. Argh, it's unfortunate you say that, as I wired it not to... and I happened to fasten the USB module to the side of the casing. Hrmmm.

I will check out the librarian. Also, I emailed the developer at Humatic (MMJ developer):

It works fine on my side. My Midibox FM appears to be sending and receiving MIDI messages with not issues at all. The only problem is that it's very troublesome uploading firmware. I've had a hell of a time. I actually posted that problem in another thread, but no one really mentioned anything. Anyhow I have been able to upload at times, I really don't know what I do differently. But I have just uploaded over and over and over and it eventually allows it. But as I said, I can trigger sounds with the keyboard. And MIOS Studio says it gets and upload request, it tries to send the software, but it just never follows through. Is there anything you'd like me to test?

Okay, well I did as you suggested. The USB module is now powered by the core. But it is still reluctant to receive the file for some reason. I get an upload request and the MIOS reboots when I ask, but it's still not accepting the file. Also, now that it is powered from the main power, the startup message is not received when I first start the unit (as the USB module must still be booting). No more LEDs left on, no change in uploading behaviour

From what I can tell there's not much I can do about the core problem. I try to upload a hex, it reboots, but does not upload the file (I think it's not accepting it). I just keep trying until it works. I'm of the opinion that it's my MBHP USB but like I said, it's reliable at all other times (sending notes or receiving and upload request). What can I really check? There is one problem with it. That's that if my usb cable is attached, some of the LEDs of my CS remain on even after I turned off the unit's power. This is strange as I only have Mi, MO and VS connected between the units, so I'm guessing there's something fishy going on. Is it better if I just make my USB unit not powered by USB?

Responses are becoming more and more cryptic! So far I've flashed all the 3 different type of detented encoders, and none of them work. Type 1 worked the least well as it just screamed with clicks without me touching it even. Thanks to my Midibox being very testy about accepting mios app uploads I'm becoming more and more frustrated with it. I should have just foregone the control surface in the firstplace.

I reviewed the datasheet and have in fact wired them backwards. Is this an issue, or is it that everything is just going to move backwards? The Midibox FM sheet does not really differentiate between A and B so I'm still not sure. Like I said before it's not an issue of confusing the ground and data line, that's fine. But I have confused A & B. I'll try when I get home.

Thanks for the continued help. I understand that they're detented, but there are 3 types of detented encoder settings Okay, well, I'm certain the center is ground, and that's how it's wired. But wouldn't it being backwards just make a right turn move left, and a left turn move right? Or is it some other crazier problem?

Those two pictures above that you posted are topsides. I'm confused

Okay, I was hoping there was some way to tell on paper. :-\

Okay, but what encoder type should I be configuring in the asm? The default is #2 ( think) and I've also recompiled and tried 3, and it still doesn't work.

What? I didn't notice the soldering mention. Is this serious? I did the work a while ago so do not know how well I did it or what temp. I thought they were chiefly physical anyways.