Hawkeye

Hm, sure you are ready for this? MIDI in general equals not to what you hear when your soundcard plays "MIDI" songs. You can use MIDI to drive samplers and any other instrument (virtual or real) you can dream of :-)

To get closer to 10 orders, i would take a second one, with color code 9421 (transparent grey) :-) Thanks!

powering ledz with anything below 7v is schoolboy business :whistle:

Mhm, now this does not sound good... aren´t there any MB6582 owners in your area, maybe someone willing to test your board before you flush it down the toilet? A second pair of eyes sometimes helps... edit: can´t you selectively lighten up the problematic leds without the baseboard attached, for debugging, with an external power source (no 9v block :-))? like this you could "close in" on the short...

And a demo pic can be found here (will add another one after it is installed in the PT-10): http://midibox.org/f...ewimage&img=837 Ah, lovely VFD... mmmm! :-)

Yup, I´d recommend the Mios32 tutorials, easy to understand, well documented... afterwards it is just about trying this and that and lots of reading :-) Have fun! :queen:

no problemo, thx for the nice coffee last time :)

Don´t forget Hawkeye, dude :-)

Hi there, well the MIDI synths are probably not part of the project, you should just buy/use standard synthesizers for that... you can also use one multi-timbral synthesizer (e.g. the waldorf micro q) for that and get away with only one midi cable and e.g. four instruments playing on four different channels in multimode. Regarding the LPCxpresso maximum midi interface capabilities... I only know the specs of the LPCxpresso predecessor, the STM32 (Core32)... It could provide you with with 3 onboard MIDI INs, 3 onboard MIDI Outs and could be expanded by a few MIDI IICs (4) to achieve a total of 7 MIDI OUTs. I guess the new platform will offer the same connectivity. Also you can of course use USB-Midi and use your MacBook for unlimited virtual instruments. Best regards, Peter

+1, the MBFM rocks!

If anyone else is also VFD hungry... the above-mentioned display from Noritake fits quite nicely into the MB6582 (its outer dimensions regarding components on the pcb differ from the schematics in the datasheet). I will update the mb6582 photo tutorial soon with pics and installation guidelines. The display needs a little bit of driver patching, though. I´ve updated a clcd driver, that works fine for me now, you can find it here: Best regards, Peter

Thx, dude... the "lcd ready" polling works now, too (fixed delays are not good for the performance). You can now haz Wilbas riser PCBs if wanted :) I´ve attached the updated driver for anyone interested. Ah... and the display is... NICE!!! :laugh: Picz later, gotta sleep nao :sleep: Best regards, Peter app_lcd.inc.txt

Science breakthrough :-) It appears the "lcd_busy checking" is the problem, plz don´t ask me why... I have removed the checks and replaced them with yet too long (still need to find minimum delays) wait loops for every character printed/command sent. As the "driver" is for a specific display with a given timing, I hope this approach is viable. Hawkeye :frantics: (with a vfd in the mb6582, yay! pics soon!)

SID-ilicious!!! :thumbsup:

100% coolness :-) I would be in for a red one (color code 6101, which is the only red transparent one), also it´s ok having to wait for more people :-)

Hi there, I am a bit out of luck these days, last week or so I burned a 4x20 OLED (looking for a good LCD replacement for the MB6582). Well, SID happens :-), as I always wanted a VFD in the MB6582 anyways, I have ordered the Noritake CU20045-UW5J. Good news is, it will fit the MB6582 quite nicely without the need for a riser card and also I did not burn it just yet :-)... I´ve connected and wired it up in 4-bit mode to the MB6582, as usual. When turning it on (with the default mb6582.hex firmware) it shows very scrambled characters, looks like it has not been switched to 4-bit mode by the default display initialization routine. Consulting the datasheet, the first thing that is being sent to the VFD apparently needs to be the "Function Set to 4-bit mode" command. Here is the relevant section: 7.7.1 Function Set Command 20H to 3FH This instruction initializes the system, and must be the first instruction executed after power-on. So, I´ve ported the 4-bit lcd display routines from the MIOS basic driver to modules/app_lcd/clcd/app_lcd.inc (which by default contains an eight-bit driver), changed the initialization sequence to really send 0x02 nibbles at first (4-bit mode), have included the changed app_lcd properly, set the DisplayType to 7 (in main.inc) and have verified that this code really is executed (tested that by playing around with the initialization stuff). With the changed driver, I do get improved character output, but only some characters look ok, other characters are wrong (the "big D" as in MIDIbox is ok). So, changing to "my" 4-bit driver improved things a little and that indicates that the display can take a late switch to 4-bit-mode... but now I am utterly confused, if a "D" was written properly to the display, doesn´t that mean I am in 4-bit mode? Maybe I´ve screwed up the driver? Could it be a timing issue, probably with the "LCD_Busy" checking? And is there any other "USER_LCD" 4-bit demo code available, so that I can verify things? Maybe some MIOS-base-level routine sends data to the display before the user initialization and screws things up? Hmm, sorry for all the questions and the confusion! Thanks for any help :sheep: Bye, Peter PS: Thorsten, I´ve also got a 256x64 OLED evaluation display lying around, so if you are into a little bit of display code hacking, just tell me and I´ll come over :-)

Hi Shuriken, thanks for your efforts! Two questions: 1) Two pieces? How are the connected together? 2) Different colors? Colored Acrylic? Cool! Would it be possible to get a red one? Bye, Peter

Very cool video! Ever played "Deflektor" on the C64 ? :thumbsup: