Firmware - Stuck at Send SysEx w/ solution.

[gabriel1712]

If you get really frustrated with this, erase then re-flash the PIC?!

Hey Ken
I have zero knowledge of this dark magic you speak of. Doesn't it involve a specialized cable and a few programs the aliens brought with them to earth?

[dmitri]

If you get really frustrated with this, erase then re-flash the PIC?!

PIC doesn't have anything to do with it.

[Firelord]

If you get really frustrated with this, erase then re-flash the PIC?!

I think the PIC is not responsible for the problem. More like the flash memory in which the bootloader resides has been somehow altered and the bootloader got damaged. Thus I guess the only solution is to re-flash the ATMega via a programming cable and then update the firmware by means of MIDI-OX or MCT. At least that's the way I see it, I could be wrong of course.

[dmitri]

I really don't know. Normal boot, no button press takes me straight to the 'FW update clock' screen'. Same goes for boot with left button pressed. I can't get passed the 'Send SysEx' screen, thus I can't erase or install new. I'm stuck.

All has been fine on my MD for months till I try to upgrade FW via MCT to day (no offence, elrules )

You claim that you have v3 or v4 bootloader which requires ‘erase_firmware.syx’ to erase an old firmware. These bootloaders erase an old firmware only after receiving ‘erase_firmware.syx’ and will show 'Erased' when they do it! The fact that you've never seen 'Erased' means that the old firmware is still intact and the reason you cannot boot into MegaDrum firmware means that LEFT button is stuck.

So, one of these must be true:
1. You really have v3/v4 bootloader but the pin for LEFT button is shorted to ground.
2. You really have v3/v4 bootloader and when you first time sent ‘erase_firmware.syx’ it did show 'Erased'.
3. You have v1/v2 bootloader.

[gabriel1712]

The fact that you've never seen 'Erased' means that the old firmware is still intact and the reason you cannot boot into MegaDrum firmware means that LEFT button is stuck.

So, one of these must be true:
1. You really have v3/v4 bootloader but the pin for LEFT button is shorted to ground.
2. You really have v3/v4 bootloader and when you first time sent ‘erase_firmware.syx’ it did show 'Erased'.
3. You have v1/v2 bootloader.

I can safely rule out no.3. I bought the 2.8 kit from Synthex in april 09. I have up to 15 times succesfully updated my MD w/ erase_fimware etc..AND on all those occations seen 'Erased' on the bottomline of the LCD.

As for no.2, unless 'Erased' flashed over the screen in a splitsec. and got replaced by 'Send SysEx now' again I can rule it out. I looked for it, expecting it and it wasn't there.

I realize now my MCT was set to bootloader v.2 in MCT config and that may well be why everything got screwed up. I don't know. I did of cause then set it to v.3 and retried MCT update. Now things are really screwed up, which in the way of problem-shooting is good, no? None of the buttons respond before, under and after boot. No matter what I do, the screen is a superbright topline, with near-invisible garble reading: " pdat# Send S " and nothing in the bottomline.

I'm chasing no.1, but making readings at the buttons pins showed the button have 5v and pressing the button cut the power. Should I take the reading at some pin on a chip or is the read-out at the buttons pins enough?

[Ken Forgettable]

I flash the AVR all day - no problems.
PC goes off for the weekend.
Next time PC is up, MegaDrum is found - no problem.

Sometimes though there's no MIDI in to the PC - 'scope shows AVR to PIC activity *and* PIC to PC activity.

WinPIC verifies PIC OK.
PonyProg verifies AVR OK.

Serial MIDI devices work but I do not have any other USB MIDI to test.
In this state MegaDrum will not work on my other box either!

... so I've taken to erasing then re-flashing the PIC which has *always* got me going again.

I'm not expecting anyone to follow this advice - I know I'm in the Twilight Zone ... the Flux thing is bloody weird too!

[dmitri]

As for no.2, unless 'Erased' flashed over the screen in a splitsec. and got replaced by 'Send SysEx now' again I can rule it out. I looked for it, expecting it and it wasn't there.

'Erased' is only ever shown after 'Send SysEx now'.

I realize now my MCT was set to bootloader v.2 in MCT config and that may well be why everything got screwed up. I don't know. I did of cause then set it to v.3 and retried MCT update. Now things are really screwed up, which in the way of problem-shooting is good, no? None of the buttons respond before, under and after boot. No matter what I do, the screen is a superbright topline, with near-invisible garble reading: " pdat# Send S " and nothing in the bottomline.

I'm chasing no.1, but making readings at the buttons pins showed the button have 5v and pressing the button cut the power. Should I take the reading at some pin on a chip or is the read-out at the buttons pins enough?

This is really very chaotic description. Can you make it easier to read and understand?

[dmitri]

Also, bootloader is meant to be protected from being corrupted/overriden provided Atmega fuses are set correctly. If bootloader got corrupted, then the only way to restore it is by following instructions from http://www.megadrum.info/content/progra ... bootloader

[gabriel1712]

As for no.2, unless 'Erased' flashed over the screen in a splitsec. and got replaced by 'Send SysEx now' again I can rule it out. I looked for it, expecting it and it wasn't there.

'Erased' is only ever shown after 'Send SysEx now'.

I realize now my MCT was set to bootloader v.2 in MCT config and that may well be why everything got screwed up. I don't know. I did of cause then set it to v.3 and retried MCT update. Now things are really screwed up, which in the way of problem-shooting is good, no? None of the buttons respond before, under and after boot. No matter what I do, the screen is a superbright topline, with near-invisible garble reading: " pdat# Send S " and nothing in the bottomline.

I'm chasing no.1, but making readings at the buttons pins showed the button have 5v and pressing the button cut the power. Should I take the reading at some pin on a chip or is the read-out at the buttons pins enough?

This is really very chaotic description. Can you make it easier to read and understand?

I'll do my best.
In 'MCT>options>config' bootloader was set to v2 when I first try to update. Since I have a secured bootloader, v2 is a wrong setting, right? I then set it to v3, retried to update with MCT and became worst as described above.

Anyway after power off for 10 mins it's back to being stuck at 'Send SysEx now'.

Observations:
Boot w/ left button held, led flash like expected untill I release left button. When led turns off. I would say Left button is fully functional.
I press down to 'OK' (16MHz), 'Send SysEx now' and constant led goes on. From then on there's no response.

Should I take the left button reading at some pin on a chip or is the read-out at the buttons pins enough?

[dmitri]

As for no.2, unless 'Erased' flashed over the screen in a splitsec. and got replaced by 'Send SysEx now' again I can rule it out. I looked for it, expecting it and it wasn't there.

'Erased' is only ever shown after 'Send SysEx now'.

I realize now my MCT was set to bootloader v.2 in MCT config and that may well be why everything got screwed up. I don't know. I did of cause then set it to v.3 and retried MCT update. Now things are really screwed up, which in the way of problem-shooting is good, no? None of the buttons respond before, under and after boot. No matter what I do, the screen is a superbright topline, with near-invisible garble reading: " pdat# Send S " and nothing in the bottomline.

I'm chasing no.1, but making readings at the buttons pins showed the button have 5v and pressing the button cut the power. Should I take the reading at some pin on a chip or is the read-out at the buttons pins enough?

This is really very chaotic description. Can you make it easier to read and understand?

I'll do my best.
In 'MCT>options>config' bootloader was set to v2 when I first try to update. Since I have a secured bootloader, v2 is a wrong setting, right? I then set it to v3, retried to update with MCT and became worst as described above.

Please don't refer to 'messy above'. Do you want me to help finding the cause of the problem or do you want me to jump between posts to get a clear picture?

Anyway after power off for 10 mins it's back to being stuck at 'Send SysEx now'.

10s or 10min is irrelevant, MegaDrum doesn't have backup battery to wait for it to discharge.

Observations:
Boot w/ left button held, led flash like expected untill I release left button. When led turns off. I would say Left button is fully functional.

If after releasing LEFT button the MIDI led stops flashing would indicate the button is ok.

I press down to 'OK' (16MHz), 'Send SysEx now' and constant led goes on. From then on there's no response.

Should I take the left button reading at some pin on a chip or is the read-out at the buttons pins enough?

1. Try doing the update on another USB port, another PC.
2. Try doing the update over a standard MIDI port.
3. Follow my suggestion a few posts up: viewtopic.php?p=10513#p10513