Page 1 of 5

Problem with firmware getting erased by random!!!

PostPosted: Wed Mar 12, 2008 8:45 pm
by slayer666
I have to reinstall the firmware every couple of reboots of the megadrum.
I Update the firmware with midiox and the megadrum reboots, all ok.
I unplug the usb and leave it for at minute to rest and then plug usb in and I get the firmware update menu from start.
It's like it gets erased as soon as the power is cut off.

Firmware or hardware error?

Edit: I noticed that It doesn't erase the firmware, it simply starts in Update mode sometimes.
Anyone else experience this?

Re: Problem with firmware getting erased by random!!!

PostPosted: Wed Mar 12, 2008 10:31 pm
by Synthex
slayer666 wrote:I have to reinstall the firmware every couple of reboots of the megadrum.
I Update the firmware with midiox and the megadrum reboots, all ok.
I unplug the usb and leave it for at minute to rest and then plug usb in and I get the firmware update menu from start.
It's like it gets erased as soon as the power is cut off.

Firmware or hardware error?

Edit: I noticed that It doesn't erase the firmware, it simply starts in Update mode sometimes.
Anyone else experience this?

It's a problem with buttons or it's a problem with the firmware.
Dmitri, is there a waiting time before check if a button is pressed after the boot ?
(I think about electrical parasites (noise) at boot)

Re: Problem with firmware getting erased by random!!!

PostPosted: Wed Mar 12, 2008 10:37 pm
by slayer666
Synthex wrote: It's a problem with buttons or it's a problem with the firmware.


I've measured my keyboard and the megadrumboard and I can't find anything that could short out.
In midiox there's constant footcontroller activity, and I have nothing attached. No piezo and no hihat pot.

Re: Problem with firmware getting erased by random!!!

PostPosted: Wed Mar 12, 2008 10:46 pm
by Synthex
slayer666 wrote:In midiox there's constant footcontroller activity, and I have nothing attached. No piezo and no hihat pot.

If you connect pin4 of 32inputs connector to GND, what's happen ?

Re: Problem with firmware getting erased by random!!!

PostPosted: Thu Mar 13, 2008 1:35 am
by slayer666
Synthex wrote:
slayer666 wrote:In midiox there's constant footcontroller activity, and I have nothing attached. No piezo and no hihat pot.

If you connect pin4 of 32inputs connector to GND, what's happen ?


It made no difference.
This seems only to occur after a firmware update directly after the megadrum rebooted itself. It keeps on scrolling forever..

Take a look at the screenshot.

Re: Problem with firmware getting erased by random!!!

PostPosted: Thu Mar 13, 2008 9:52 am
by dmitri
slayer666 wrote:I have to reinstall the firmware every couple of reboots of the megadrum.
I Update the firmware with midiox and the megadrum reboots, all ok.
I unplug the usb and leave it for at minute to rest and then plug usb in and I get the firmware update menu from start.
It's like it gets erased as soon as the power is cut off.

Firmware or hardware error?

Edit: I noticed that It doesn't erase the firmware, it simply starts in Update mode sometimes.
Anyone else experience this?


Try to pull pin 8 of Atmega to +5 over a 10k-100k resistor. Does it make a difference?

Re: Problem with firmware getting erased by random!!!

PostPosted: Thu Mar 13, 2008 9:57 am
by dmitri
slayer666 wrote:
Synthex wrote:
slayer666 wrote:In midiox there's constant footcontroller activity, and I have nothing attached. No piezo and no hihat pot.

If you connect pin4 of 32inputs connector to GND, what's happen ?


It made no difference.
This seems only to occur after a firmware update directly after the megadrum rebooted itself. It keeps on scrolling forever..

Take a look at the screenshot.

Did you leave "Levels" as Auto for HiHat controller? If so, try setting them manually so that there are no MIDI activity when the pedal is fully pressed and when it is fully depressed.

Re: Problem with firmware getting erased by random!!!

PostPosted: Thu Mar 13, 2008 11:00 am
by slayer666
dmitri wrote:
slayer666 wrote:I have to reinstall the firmware every couple of reboots of the megadrum.
I Update the firmware with midiox and the megadrum reboots, all ok.
I unplug the usb and leave it for at minute to rest and then plug usb in and I get the firmware update menu from start.
It's like it gets erased as soon as the power is cut off.

Firmware or hardware error?

Edit: I noticed that It doesn't erase the firmware, it simply starts in Update mode sometimes.
Anyone else experience this?


Try to pull pin 8 of Atmega to +5 over a 10k-100k resistor. Does it make a difference?


I routed atmega pin8 through 47k to +5V and It didn't startup in update mode at all.

What's the next step?

Synthex asked if you have a keypress delay at startup?

Re: Problem with firmware getting erased by random!!!

PostPosted: Thu Mar 13, 2008 11:09 am
by dmitri
slayer666 wrote:
dmitri wrote:
slayer666 wrote:I have to reinstall the firmware every couple of reboots of the megadrum.
I Update the firmware with midiox and the megadrum reboots, all ok.
I unplug the usb and leave it for at minute to rest and then plug usb in and I get the firmware update menu from start.
It's like it gets erased as soon as the power is cut off.

Firmware or hardware error?

Edit: I noticed that It doesn't erase the firmware, it simply starts in Update mode sometimes.
Anyone else experience this?


Try to pull pin 8 of Atmega to +5 over a 10k-100k resistor. Does it make a difference?


I routed atmega pin8 through 47k to +5V and It didn't startup in update mode at all.

I did catch the meaning of the last sentence.

What's the next step?

Synthex asked if you have a keypress delay at startup?


There is no delay. I've posted the source code for the Bootloader and you're welcome to look at it. I can put the delay at the beginning but how are you going to write the new bootloader into Atmega?

Re: Problem with firmware getting erased by random!!!

PostPosted: Thu Mar 13, 2008 11:13 am
by Synthex
dmitri wrote:Try to pull pin 8 of Atmega to +5 over a 10k-100k resistor. Does it make a difference?

What is the period of pressure on a button to be taken into account by the Atmega (for the bootloader and the firmware) ?