Firmware Upgrade fails again and again

[dmitri]

Well. The Erase worked but sending the FW failed - so I did the PIC fix which of course means hardware and software. Since then I have had other symptoms

You said you'd had "Tormentors symptom even with the PIC fix". Am I misreading?

(like the blank LCD coming to life only when a key is pressed) and indeed most of the other oddities which people have been posted in the last couple of months!

Can you create a topic so that we could address the problems you have?

[Ken Forgettable]

Can you create a topic so that we could address the problems you have?

My board is stable except for problems relating to flashing so I'm not too concerned.
If these problems are related to the overall design of Megadrum - it would be a useful exercise.
Have you experienced similar issues with your builds?

[dmitri]

Have you experienced similar issues with your builds?

What issues?

[Ken Forgettable]

What issues?

I refer to problems at the bootloader stage.
There have been many posts outlining issues with buttons not working as expected, blank LCD displays, firmware corruption and failed updates.

Not all of these are due to human error as they do not affect the running FW.

Also problems often arise on a seemingly functioning unit - at boot time.

Code: Select all

while (verify == ERASE_VERIFY) {    //humm

My own headless code on a Synthex v2.8 board is still in beta

[dmitri]

What issues?

I refer to problems at the bootloader stage.
There have been many posts outlining issues with buttons not working as expected, blank LCD displays, firmware corruption and failed updates.

Not all of these are due to human error as they do not affect the running FW.

Please, provide the links to the posts/topics that you're referring to and not being caused by human errors. Please include the links to topic/posts with problems I have not addressed/helped to resolve. I will address it now since apparently I missed them.

Also problems often arise on a seemingly functioning unit - at boot time.

Again, create a separate topic and raise the problem there. I don't think Tormentor was very interested in our unrelated to the topic conversation.

[Ken Forgettable]

I don't think Tormentor was very interested in our unrelated to the topic conversation.

Sorry Tormentor,
Dmitri is right - ignore my rants and follow his advice. The PIC fix is certainly worth while and may indeed fix your problem

[Tormentor]

Well, I've ordered the needed components for building the cable. Hope this will fix it

[Tormentor]

Well, back again. I bought a brand new pic 18f2550 and managed it to flash the newest firmware version for the pic. I also added a 38 kΩ resistor between pin 3 and 6. Megadrum is again successfully recognized as "Megadrum USB" but the firmware flash fails again Same symptoms.
Any new idea?

[dmitri]

Well, back again. I bought a brand new pic 18f2550 and managed it to flash the newest firmware version for the pic. I also added a 38 kΩ resistor between pin 3 and 6. Megadrum is again successfully recognized as "Megadrum USB" but the firmware flash fails again Same symptoms.
Any new idea?

I'm afraid you need to list all your steps in detail again here.
Did you read through http://www.megadrum.info/forums/viewtopic.php?f=3&t=790?
Tried anything suggested there?

[Tormentor]

I didn't change anything in my procedure. I left my settings as I used for the last trys. I used my listing as a step by step list for my current try.

1. Plug in Megadrum by holding down left button.
2. I load Midi-OX and go to "Options" --> "Configure Buffers" and set "LowLevel Output Buffers" to 60000.
3. Under "Options" --> "Midi Devices" I select Megadrum USB as Midi Output
4. Pushed the down button to confirm 16mhz clock. The Display now shows "Send sysex now" and the LED glows steady.
5. In "Midi-Ox" --> "View" --> "Sysex". In "Sysex" window I select "Command window" and "Load file". I select erase_firmware.syx.
6. Then "Send sysex". The LED lights up. A few seconds later, the Display shows "ERASED". Now the LED is off.
7. I close the window and select again in the Midi-OX window "View" --> "sysex"
8. In sysex window, I go to "Command Window", then "Load file" --> megadrum32_16_32_20090609.syx
9. In "Command Window" I click on "Send sysex"

Then nothing happens. LED is not flashing, the Display still shows "ERASED".

So when I repeat these steps without erasing the firmware before, I can see that on Midi-OX
http://img3.imagebanana.com/view/3wbdc6kg/Unbenannt.jpg

I can wait up to 10 minutes, nothing changes. The Megadrum display still shows "Send sysex now"

Even my screenshot is still up to date. It stops at offset "39"

What I've changed to my last setup is:

1. Added 38k Resistor to pin 3 and 6. (I hope I've done it right)
http://img3.imagebanana.com/view/yxadecgv/CIMG0149.JPG

2. Bought a new Pic 18f2550 and flashed it with the firmware mentioned here:
viewtopic.php?f=3&t=268

3. After few days of trying flashing the pic firmware, it was successful and my Megadrum is again recognized as "Megadrum USB"

4. I tried steps mentioned above on 3 machines. 2 Vista and one xp machine. I got the same results. The LED still isn't flashing.

Did you read through viewtopic.php?f=3&t=790?

I didn't test a usb to midi cable. But I think this will be my next step.