Firmware upgrade disaster!!!

[el-dr]

So, does this mean that if I upgrade a 20MHz fw file with a 20MHz crystal, but with the wrong clock speed selection in the menu, it can cause these symptoms?

You won't be able to upgrade with the wrong clock selected. The thing that you are not able to select the right clock tells that there is something wrong with the buttons. When you press the UP button the voltage on the pin 6 of Atmega must go from +5 to 0.

Something very nasty is going on here and I'm totally clueless and frustrated. Here's what I tried:

I have an Atmega32, so I downgraded the clock to 16MHz and tried this one. I worked perfectly well and the clock was selectable with the UP button on the fw update page.

Then I tried to update to the newest version with this MCU. The fw erase sysex worked fine, the md displayed the "erased" msg. Then I sent the 32_16_32 sysex file and the result was the same with the other MCU: it seems as if no sysex data arrived to the md. However, this cannot be the case, because the fw eraser can be rerun successfully at any time with both MCUs.

Then I thought, maybe it's MIDI-OX or the computer, so I tried to:
- receive and send sysex dumps from and to the Yamaha DTS70 without any problem, so MIDI-OX is probably OK and so is my MIDI interface.
- then I tried the same setup with md, so this time it was connected through the MIDI In instead of USB, but the result was the same.
-then I changed the computer and tried everything again, but it made no difference (fw erase worked, the update didn't, the Up button for clock selection worked on fw update with the Atmega32, but didn't with the Atmega644)

- then I tried to replace MIDI-OX with Cubase, the result was the same.

- then I noticed the output monitor of MIDI-OX doesn't show F7 at the end. The last 10-15% of the file was not displayed and probably was not transmitted either (and it was the same on both computers!!!).

I have MIDI-OX 7.0.0.365, I tried various output buffer settings (60000-64000 bytes/2-4-16 buffers).

So I tried: multiple MCUs, multiple softwares to send the sysex (MIDI-OX/Cubase), multiple computers and multiple ways to connect (MIDI/USB) firmware erase works everywhere, the update doesn't and I couldn't even locate where the problem can be. To make things even worse: last week I could update to fw 090528 in a minute with the exact same setup (same md, computer and MIDI-OX settings).

And to make the whole story even worse: there's difference between how the two MCUs behave:

The Atmega32 displays "Fw updater 16MHz Down-ok.Up-clock", while the 644 says something like "Firmware updater Press Down", the Atmega32 reacts to the Up button on the fw screen, the Atmega 644 doesn't.

????????

[kurtus420]

I have the exact same issue going on as well.
I'll let you know if I figure anything out.

So, does this mean that if I upgrade a 20MHz fw file with a 20MHz crystal, but with the wrong clock speed selection in the menu, it can cause these symptoms?

You won't be able to upgrade with the wrong clock selected. The thing that you are not able to select the right clock tells that there is something wrong with the buttons. When you press the UP button the voltage on the pin 6 of Atmega must go from +5 to 0.

Something very nasty is going on here and I'm totally clueless and frustrated. Here's what I tried:

I have an Atmega32, so I downgraded the clock to 16MHz and tried this one. I worked perfectly well and the clock was selectable with the UP button on the fw update page.

Then I tried to update to the newest version with this MCU. The fw erase sysex worked fine, the md displayed the "erased" msg. Then I sent the 32_16_32 sysex file and the result was the same with the other MCU: it seems as if no sysex data arrived to the md. However, this cannot be the case, because the fw eraser can be rerun successfully at any time with both MCUs.

Then I thought, maybe it's MIDI-OX or the computer, so I tried to:
- receive and send sysex dumps from and to the Yamaha DTS70 without any problem, so MIDI-OX is probably OK and so is my MIDI interface.
- then I tried the same setup with md, so this time it was connected through the MIDI In instead of USB, but the result was the same.
-then I changed the computer and tried everything again, but it made no difference (fw erase worked, the update didn't, the Up button for clock selection worked on fw update with the Atmega32, but didn't with the Atmega644)

- then I tried to replace MIDI-OX with Cubase, the result was the same.

- then I noticed the output monitor of MIDI-OX doesn't show F7 at the end. The last 10-15% of the file was not displayed and probably was not transmitted either (and it was the same on both computers!!!).

I have MIDI-OX 7.0.0.365, I tried various output buffer settings (60000-64000 bytes/2-4-16 buffers).

So I tried: multiple MCUs, multiple softwares to send the sysex (MIDI-OX/Cubase), multiple computers and multiple ways to connect (MIDI/USB) firmware erase works everywhere, the update doesn't and I couldn't even locate where the problem can be. To make things even worse: last week I could update to fw 090528 in a minute with the exact same setup (same md, computer and MIDI-OX settings).

And to make the whole story even worse: there's difference between how the two MCUs behave:

The Atmega32 displays "Fw updater 16MHz Down-ok.Up-clock", while the 644 says something like "Firmware updater Press Down", the Atmega32 reacts to the Up button on the fw screen, the Atmega 644 doesn't.

????????

[el-dr]

I have the exact same issue going on as well.
I'll let you know if I figure anything out.

Did it all begin with the 20090617 fw file?

[dmitri]

The Atmega32 displays "Fw updater 16MHz Down-ok.Up-clock", while the 644 says something like "Firmware updater Press Down", the Atmega32 reacts to the Up button on the fw screen, the Atmega 644 doesn't.

Where did you get both Atmega32 and Atmega644?
What exactly does the bootloader show with Atmega644?

When booting with the LEFT key pressed do you see the MIDI LED fast falsing until you release the key? Is it the same with both Atmega32 and Atmega644?

[kurtus420]

All I did was plug in my megadrum32 from synthex installed usb driver fine. It was working fine with the install firmware 20090529,
then I erased it however it took a few tries to send the sysex erase message. Megadrum showed erased went to load 20090609 and it would not send just like you. I to am experiancing the midi ox message issue of the sysex file not being complete on 20090609 and 20090617 in the message window using the same version of midi-ox on a vista based laptop. I have an atmega32 and am getting the same results as yours.

I have the exact same issue going on as well.
I'll let you know if I figure anything out.

Did it all begin with the 20090617 fw file?

[dmitri]

All I did was plug in my megadrum32 from synthex installed usb driver fine. It was working fine with the install firmware 20090529,
then I erased it however it took a few tries to send the sysex erase message. Megadrum showed erased went to load 20090609 and it would not send just like you. I to am experiancing the midi ox message issue of the sysex file not being complete on 20090609 and 20090617 in the message window using the same version of midi-ox on a vista based laptop. I have an atmega32 and am getting the same results as yours.

Have you tried with Windows XP?

[el-dr]

The Atmega32 displays "Fw updater 16MHz Down-ok.Up-clock", while the 644 says something like "Firmware updater Press Down", the Atmega32 reacts to the Up button on the fw screen, the Atmega 644 doesn't.

Where did you get both Atmega32 and Atmega644?
What exactly does the bootloader show with Atmega644?

When booting with the LEFT key pressed do you see the MIDI LED fast falsing until you release the key? Is it the same with both Atmega32 and Atmega644?

They're both from Synthex. The MIDI LED is flashing as you described with the 32 and isn't with the 644. The 32 display reads "Fw updater 16MHz Down-ok.Up-clock", the 644 reads "Firmware updater Press key Down"

Isn't it possible that it's sg to do with the latest fw? kurtus420 has the same issue.

[el-dr]

All I did was plug in my megadrum32 from synthex installed usb driver fine. It was working fine with the install firmware 20090529,
then I erased it however it took a few tries to send the sysex erase message. Megadrum showed erased went to load 20090609 and it would not send just like you. I to am experiancing the midi ox message issue of the sysex file not being complete on 20090609 and 20090617 in the message window using the same version of midi-ox on a vista based laptop. I have an atmega32 and am getting the same results as yours.

Have you tried with Windows XP?

I'm on XP and it's the same.

In the meantime I figured out that the problem is NOT with MIDI-OX. I sent the sysex file from MIDI-OX to Cubase, then saved the file from there and compared it with the original in MIDI-OX. They are identical. So it means that the MIDI-OX Output monitor is buggy because it truncates the data displayed, but the actual transmission is OK.

[dmitri]

the 644 reads "Firmware updater Press key Down"

This is not my version of the bootloader. I can only continue to help you with Atmega32 at 16MHz.
Install Atmega32, 16MHz crystal, make the changes to PIC18F2550 as I suggested before then repeat the whole update procedure using MIDI-OX and then step-by-step described what you did with smallest details.

[kurtus420]

I will do the same, I have made my iscp cable and just aquired a pc that has mellenium edition installed on it (hope thats not a problem)
so I will try it when I get home from work in about 7 hours and let you guys know the outcome.

the 644 reads "Firmware updater Press key Down"

This is not my version of the bootloader. I can only continue to help you with Atmega32 at 16MHz.
Install Atmega32, 16MHz crystal, make the changes to PIC18F2550 as I suggested before then repeat the whole update procedure using MIDI-OX and then step-by-step described what you did with smallest details.