Problem with updating firmware

[thramul]

no, nothing happens in this chart, but under "usb-controller", called "unknown device".

[thramul]

Also see this: http://www.megadrum.info/forums/viewtopic.php?f=3&t=268

thank you, I will try this tomorrow. But I still wonder, how this could happen, since it did work before ... since the sysex file transmission did not work, I had to power off megadrum while still beeing in the "send sysex file now" dialog. Could the bootloader be screwed up?

Edit: only when I'm in the bootloader and press down, my computer recognizes megadrum ... strange oO

[dmitri]

Once you've sorted out USB detection and if you have the latest bootloader you must not skip step 6 from http://www.megadrum.info/forums/viewtopic.php?f=3&t=622

[thramul]

ok, I thought this would only be neccessary for old bootloaders, so I didn't do it. thanks for the advice!
but is there any way, I can sort out whether my megadrum is able to recieve data or not? and I suppose, I will need to programm the bootloader without the usb cable via lpt cables ...

[dmitri]

ok, I thought this would only be neccessary for old bootloaders, so I didn't do it. thanks for the advice!
but is there any way, I can sort out whether my megadrum is able to recieve data or not?

If you can program it via the bootloader, then it can receive data.

and I suppose, I will need to programm the bootloader without the usb cable via lpt cables ...

Sorry, why do you want to program the bootloader if you already have it programmed?

[thramul]

Sorry, why do you want to program the bootloader if you already have it programmed?

in this post http://www.megadrum.info/forums/viewtopic.php?f=3&t=268 you posted a firmware to update in order to fix the usb problem. since its not working for me, I think I will have to programm it via lpt, or am I wrong here? sorry, I'm not to certain about those things.
thank you

[dmitri]

Sorry, why do you want to program the bootloader if you already have it programmed?

in this post http://www.megadrum.info/forums/viewtopic.php?f=3&t=268 you posted a firmware to update in order to fix the usb problem. since its not working for me, I think I will have to programm it via lpt, or am I wrong here? sorry, I'm not to certain about those things.
thank you

Firmware in this topic is for PIC18F2550. You may not need to program it since just a resistor could be enough to fix the issue with the USB detection(if you still have this issue). But if you still need to re-program PIC18F2550, have a look at http://www.megadrum.info/content/progra ... pic18f2550 for instructions.

[thramul]

ok, the additional resistance worked very well, windows is able to detect megadrum again. I also was able to erease the firmware, but still, I cannot send the new firmware. When I sent the erase programm, the midi led was blinking and very soon the LCD showed: "ERASED". But when I try to send the new firmware, the midi LED is just alight and nothing happens at all.
I'm sending the megadrum32_16_32_20090326.syx file, since I have the Atmega 32 with 32 inputs and a 16mhz clock. The outputbuffer is at 60000 Bytes, "Num" at 16. Do I have to chance anything else in Midi-OX? The erease-firmware was very small, so maybe thats why it could be transfered. But I have no idea if this helped, I really don't know what I still can try.

[dmitri]

This is how macca2004 solved it by increasing delays:

I changed it from the syx view window. I selected the sysex/configure menu and changed the delay from 60ms to 100ms in both boxes.

It may work for you. It's kinda hard for me to suggest anything else because with my devboard and all modules I've built I've never had any problems updating firmware using MIDI-OX as long as I follow the steps exactly as I described in 'Updating MegaDrum firmware via bootloader with MIDI-OX'. It's just I cannot reproduce the problem.
1. Try on another USB port?
2. Try on another PC?
2. Try another USB cable?

[thramul]

increasing the delays didn't work for me, I will try your other suggestions later.
For now, I tried an other program to send the sysex file. Sending the erase program worked well again, but when I tried to load the firmwarefile, I got this error message:

Is this important to the problem?

I have an other idea to identify the problem: Could you please send me the file of the 20090211 firmware so I can test, whether this one works or not?

Should nothing of those work, I will build the LPT connector and program the atmega via the ponyprog program.

thanks for your help again!