mr_chombee

uuuuhhh oohhh uhhhh....all blame goes to me! I found out that the 6th bridge at the bottom side of the core has been connected to a wrong pin. how embarrassing. displays are working fine now. yeehaw! thanks for your time...

hehe...I was about to reply, but then saw your 2nd post. cheers for helping me out! hope jdutcher will not be upset if I hijack this thread, but we seem to have the same problem, don't we? btw, the PIC is not from you. I ordered it here in germany from mike. I think he does a great job as well, but maybe there's a slight possibility that the bootstrap is defective somehow(?). is it possible to upload mios with a defective bootstrap? however, let's start from the beginning: the other (2x16) LCD I tried, has been connected with a different cable. I'm pretty sure that the wiring is ok on both cables. interesting: I again uploaded the mbox64 code, got the random data stream, but then, after I switched back to the mbox seq application, the display shew something like "rebooting Mios" or "updating Mios". this makes me think that the display connection should be fine. right? other ideas? cheers, nico

correction: this seemed to be an error of my voltmeter. I've got 5V here as well.

I have exactly the same problem here. I do the midibox seq and use the same displays which thorsten uses (from reichelt). I already saw some data on screen when I uploaded other applications (i.e. midibox64 main.syx) to the PIC, but these were totally messed up and the core sends out strange sysex strings. also connected a 2x16 display to the core - same problem. I think it's definitely not the LCD. is there probably a problem with a wrong burned bootstrap loader? (I got a pre-burned PIC).

hi all, I've got another lcd problem. I've already made it throught hundreds of posts, but none seemed to help me. I use two 40x2 LCD modules from reichelt, which were recommended on thorstens orderlist. after I turn on the core module (mios1.7, setup_mbseq_v2.syx & main.syx successfully uploaded), the display lights up and shows: - 1 row of blocks for 2 seconds - then the blocks disappear (as if it wants to display the mios copyright note?) - blocks come back again (sometimes it shows 1 and a half row of blocks for a short time) I tried the trimpots to adjust backlight and contrast, but the display stays blank (apart from the blocks). I connected some buttons to the DIN module. the input monitor of MIDI-OX reacts to them, so I assume that mios and the application are running properly. I also did the sysex send/receive test. It seems to work fine - I get prompt response, but strangely there's a slight difference between the input string and the output string: input string: F0 00 00 7E 40 00 0F F7 return sring: F0 00 00 7E 40 00 0F 00 F7 something wrong here?? the connections between core and display should be ok. I also tried another small 16x2 LCD module...same problem here. I measured all the pins suggested in the midi debug article. all are fine, apart from this: J2 Vd (GND) <-> PIC Pin 20 = 4.85 V something wrong here?? I also tried to upload the midibox64 application (main.syx). after that, the display shows some strange hyroglyphs and the module sends a continuous sysex stream. can someone help me out?

hey JE:5, just found that post and thought I say hello. how's the progress of your box? btw, I'm new here as well, so hello everyone! I started to build one of these old midiboxes a few years ago, but never finished it due to a lack of time. but I still have all the parts so I'll give it another chance. the mbhp concept is awesome! it makes it so much easier. most of my modules are already soldered...hope I can go for a test run next week. cheers!