lemonhorse

Hi TAG What kind of error message?

Hi * Got a problem with installing the MIOS32 Bootloader. I'm not sure if there is a USB problem. I changed the USB cable. No difference. I changed the XP Workstation - same result. Found this: http://support.code-red-tech.com/CodeRedWiki/LPCLinkDiagnostics Here is the dfuapp.log output: ***************************************************** *** DFU LOG FILE *** Creation Time : dfuapp.log ***************************************************** Open Device Get Device Descriptor successful Get Configuration Descriptor successful DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is operating in the DFU mode and is waiting for requests. Device Descriptor bLength: 0x12 bDescriptorType: 0x01 bcdUSB: 0x0200 bDeviceClass: 0x00 bDeviceSubClass: 0x00 bDeviceProtocol: 0x00 bMaxPacketSize0: 0x40 idVendor: 0x0471 idProduct: 0xdf55 bcdDevice: 0x0001 iManufacturer: 0x00 iProduct: 0x00 iSerialNumber: 0x00 bNumConfigurations: 0x01 DFU Get State successful ---> DFUState: Device is operating in the DFU mode and is waiting for requests. Download Block Nb 0 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 1 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 2 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 3 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 4 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 5 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 6 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 7 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 8 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 9 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 10 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 11 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 12 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 13 (2048 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 14 (1544 Bytes) DFU Get State successful ---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS. DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests. Download Block Nb 15 (0 Bytes) DFU Get State successful ---> DFUState: Device has received the final block of firmware from the host and is waiting for receipt of DFU_GETSTATUS to begin the Manifestation phase; or device has completed the Manifestation phase and is waiting for receipt of DFU_GETSTATUS. (Devices that can enter this state after the Manifestation phase set bmAttributes bit bitManifestationTolerant to 1.) DFU Get Status successful ---> DFUStatus: No error condition present. ---> DFUState: Device has programmed its memories and is waiting for a USB reset or a power on reset. (Devices that must enter this state clear bitManifestationTolerant to 0.) Device Reset after Download successful *** END OF FILE *** Any Ideas? - Contemplating Lemonhorse Annotation: LED2 is always blinking - and it's my first LPCXpresso ;-)

Wow. I will have a try. Yes, the SEQV4 project is on the top of my todo-list now. :)

Ahoi Param1! Anmerkung: Ich weiß nicht welches Projekt bei dir konkret geplant ist - bei der MB SID & MB FM würde ich generell stark von Schaltnetzteilen abraten. Ich habe es versucht, die Audio-Signale waren von Oberwellen verunreinigt. Gruß, - Lemonhorse

Wow! I was very lucky with my good old outdated MB SEQ V2.1 - till now. Euclidean Rhythm - I feel a kick in for the ludic drive... - Lemonhorse

Yes sure. But it always depends on Your needs. As far as I know, there is no 4x4 or 8x8 MIDI-Router project on LPC17 base yet. I thought for a MIDIbox Newbie it would be a good starting point to take a look at a finished project.

Hello Soren! Just in case You haven't found the MIDI Router Project yet (Core8/IIC MIDI 4x4): http://ucapps.de/midi_router.html

Thanks Antix! Btw I will stuff the PIC18F4620 You send me in the Ju Ctrl Core8! ;-)

Hello dnhstv! Ten minutes - I think the period is too long...

Found The Nice Knobs Thread! :)

The IIC MIDI module (Juno MIDI I/O port) is up and running. Because of the Juno Patch Load/Store functionality I will exchange all POTs. The MIDIbox Ju Ctrl will be stuffed with ENCs instead. Any recommendations for ENCs and Control-knobs? (found no good knobs yet...)

With MIOS8/asm I will try to use a IIC MIDI Module [http://www.ucapps.de/mbhp_iic_midi.html] as a second MIDI Interface.

Updated: List of checked Soundchips: http://www.midibox.org/dokuwiki/doku.php?id=midibox_ay_ym_v2#tested_soundchips Thanks to mrspring ;-)

Hi und willkommen im Forum! Für das SID V2 Projekt benötigst du das Core8 Modul. Wie viele Core8 & SID Module du brauchst hängt davon ab, wie viele SID Chips angesteuert werden sollen. Für den Anfang (beim ersten Projekt) ist es sinnvoll mit einem Core8/SID Modul zu beginnen. Ein 2x20 LCD ist auf jeden Fall zu empfehlen plus einem "Step A Surface": http://ucapps.de/midibox_sid_manual_fp.html Von da aus kann man sich dann Stück für Stück weiter vor wagen (größere CS, mehr SID's)... Ja man kann den SysEx Editor nehmen (die MIDIbox SID wird dann über MIDI (in/out) mit dem PC verbunden). Den Klang kann man auch direkt über die CS (Control Surface) - oder über CC (MIDI Control Change Befehle) modulieren.

Year right. :) Great. I will do.

Hi mrspring! No, in worst case there is no "noise" (pseudo random square wave output) but Tone ABC. This is a good sign... There is no such method of quick and easy noise testing as far as I know. I was confused by this noise problem by my self. There was no difference or notice about the "no noise" issue in the AY38910A Datasheet from Microchip. If You want want me to, I can do some testing. (I just did a AY/YM chip interchange with IGI - because he had the AY "no noise" type from Microchip.) In the end is good for all MBAY builder to know which chips are acceptable. So I'm very interested in the results.

hi mrspring, wow 33 AY chips! :) are the chips from microchip? i ask because some of them (AY38912A/P, AY38910A/P) have no noise - just tone abc. no problems with: GI AY38912 CDA, Yamaha YM2149F (let me know if you have successfully tested other chip devices!)...

Great news TK! 512 Pots... Unendliche Weiten ;-)

Nice! And You got a lot of CPU-Power/Resources @ MIOS32! I just love to do some (spare time) asm-coding. But You're right - as far I got the Time - I got to explore the MIOS32 world. And of course I will keep an eye on Your Roland Juno 106 and Alpha Juno 2 Sysex Translator Project! :)

Welcome to the MIDIbox Forum Adrian :-) Looks like a MIDIO128 V2 Project. Can You confirm this? I can only guess. http://ucapps.de/midio128_v2.html With V3 You will have a lot more options... MIDIO128 V3 http://ucapps.de/midio128.html

Hi Julien, my code is pic/asm (not in MIOS8 C) - it's another world I guess. But I'm interested in Your CS/Future Plans! Are You interested to implement a Controller CS to Your Project?

Hello julienvoirin, Nice - great Project (Roland Juno 106 and Alpha Juno 2 sysex translator)! I got no mios32 HW yet. But it's very interesting. :-) Best Regards, - Lemonhorse

Please update to MBAY V2.1 * MIDI Program Change implemented (0 = Load Internal Patch, 1-127 = load Bankstick Patch) * Found a Bug in Fx Function (Note#1-3 ABC) * Some MIDI CC LCD Screen refresh improvements * GATE (0V / +5V) - Core8 J14 @TONE A MIDI CH » Note ON (+5V) Note OFF (0V) => http://www.midibox.org/dokuwiki/doku.php?id=midibox_ay_ym_v2#software

Project Status @ 03.11.2011 || || --- Project Start! :-) || --- 100% Ju Control MBHP HW || --- 100% [Ju Control CS(POTs, BTNs/LEDs)]--->[CC / SYSEX MIDI OUT (INDIVIDUAL TONE PARAMETER (IPR MODE))]--->[Juno] || --- 100% Note On/Off ---MIDI IN --->[Ju Control]---> Note On/Off --->MIDI OUT---> [Juno] || --- 0% Program Change (Sound Patch) via CS ENC || --- 0% CC MIDI IN --->[Ju Control: MIDI CC to SYSEX Conversation] --->MIDI OUT--->[Juno] || --- 0% "Tone" (Sound Patch) Upload [via Sysex (All PARAMETER (APR MODE)] || --- 0% "Tone" (Sound Patch) Download [via Sysex (All PARAMETER (APR MODE)] || --- 0% "Tone" (Sound Patch) Handling (Bankstick) [a lot to do...] || \/

> do they sound the same? I think so, yes. But I can't tell. I had fun with both chips, but not at the same time. I just got one MB AY(YM) and did no comparative soundtest yet. No preference on my side.