Skip to main content
Topic: Upgrade to firmware V6 failed - BP bricked (Read 350 times) previous topic - next topic

Upgrade to firmware V6 failed - BP bricked

Hello everyone,,
I tried upgrading my BP v3a to the latest firmware (v6) and it is somehow bricked.
The BP had never been upgraded before so the bootloader had to be upgraded.
These are the steps I followed.

- downloaded firmware pack V6
- downloaded v2 to v4 bootloader upgrader
- put a jumper on ICSP header - started BP - mode led went on
- started P24QP.exe - connection to BP at 115200 ok
- erased the chip
- wrote the firmware file BPv3-v2blupdaterVa3-v4.1.hex
- clicked on Normal Exec Mode
- removed the jumper - turned BP on
- connected to it with Putty - typed yes - saw the success message
- put the jumper back - started DS30 loader - connection to BP ok
- loaded file BPv3-frimware-v6.hex - pressed download

DS30 showed "looking for bootloader" for a few seconds, then "failed"...


Since then, I have no connection to the BP, either from terminal (putty), bootloader upgrader or DS 30, at any speed.
When I put the jumper, the mode led is on. USB COM port is ok (from windows manager).

I have no idea what could have gone wrong.
I don't have much equipment for testing.
I have a AVRISP, but no PIC programmer.
I work on a Windows 7 system.



Thanks for helping.

Re: Upgrade to firmware V6 failed - BP bricked

Reply #1
Hi Wanhedaking.
Unfortunately as things are now I guess you need to use a programmer like PICKit (http://http://dangerousprototypes.com/docs/Bus_Pirate_v4_and_Pickit2_(bootloader_and_firmware_updates)), ICD2, or something similar to that in order to rewrite the bootloader, since your Bus Pirate is no longer able to communicate with the computer.
I think that even a different working Bus Pirate can be used to program the bootloader into the PIC of your bricked Bus Pirate.
Anyway about the firmware the latest one is v7.1, do not v6 (http://http://dangerousprototypes.com/forum/viewtopic.php?f=28&p=65284#p65290) and the latest bootloader is the v4.5 (http://http://dangerousprototypes.com/forum/viewtopic.php?f=28&t=8498&start=75).
Am I pushy if I ask you if when you ran P24QP.exe did you put flag on the "Program Memory" and "Preserve Flash Configuration Words on Erase" items?
P24QP.exe application (or Python script) erases the whole chip, including the 'configuration words' that determine how the PIC behaves on start-up.
The v4 firmware does not contain replacement "configuration words", so the Bus Pirate will not start from the correct clock after programming a v4 firmware to a v2 bootloader with a not correctly set P24QP.exe or the Python script p24qp.py (with P24QP.PY only Upload v2 firmware or BPv3-v2blupdaterVa3-v4.1.hex):

http://dangerousprototypes.com/blog/201 ... 4-upgrade/

http://dangerousprototypes.com/docs/V2_to_v4_upgrades

Be seeing you.

U.Sb

Re: Upgrade to firmware V6 failed - BP bricked

Reply #2
I think that even a different working Bus Pirate can be used to program the bootloader into the PIC of your bricked Bus Pirate.

That is correct. PIC24F series doesn't need high voltage programming mode so you can use another BP to program it. Details: http://dangerousprototypes.com/docs/Pirate_PIC_Programmer#Programming_a_24FJ64GA002