# recover bricked Bus Pirate after firmware upgrade

**URL:** <https://community.sparkfun.com/t/recover-bricked-bus-pirate-after-firmware-upgrade/45857>\
**Category:** Tools\
**Created:** [July 3, 2023, 2:46am UTC](https://community.sparkfun.com/t/recover-bricked-bus-pirate-after-firmware-upgrade/45857 "2023-07-03T02:46:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![eterX](https://avatars.discourse-cdn.com/v4/letter/e/97f17d/32.png) [@eterX](https://community.sparkfun.com/u/eterX)\
**Post date:** [July 3, 2023, 2:46am UTC](https://community.sparkfun.com/t/recover-bricked-bus-pirate-after-firmware-upgrade/45857/1 "2023-07-03T02:46:07Z")

</div>

Hi everyone,

Any clue on how to recover a Bus Pirate bricked by a (clumsy) firmware upgrade?

Board data: Bus Pirate v3a, Firmware v5.10 (r559) Bootloader v4.4, DEVID:0x0447 REVID:0x3046

I cloned [[this repo](https://github.com/DangerousPrototypes/Bus_Pirate.git), and “succesfully” flashed [[this .hex file](https://github.com/DangerousPrototypes/Bus_Pirate/blob/master/package/BPv3-firmware/BPv3-firmware-v6.2-r1981.hex) . After that, prompt is lost. Bootloader and USB chip FT232RL are working (I am able to flash new binaries and serial activity makes TX/RX leds blink), but nothing else works.

Please help!! 😕

I guess that a pointer to a compatible .hex would be enough to get mi going.

Thanks in advance]([Bus\_Pirate/package/BPv3-firmware/BPv3-firmware-v6.2-r1981.hex at master · DangerousPrototypes/Bus\_Pirate · GitHub](https://github.com/DangerousPrototypes/Bus_Pirate/blob/master/package/BPv3-firmware/BPv3-firmware-v6.2-r1981.hex))]([GitHub - DangerousPrototypes/Bus\_Pirate](https://github.com/DangerousPrototypes/Bus_Pirate.git))

---

<div class="post-metadata">

**Author:** ![TS-Russell](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/ts-russell/32/6092_2.png) [@TS-Russell](https://community.sparkfun.com/u/TS-Russell)\
**Post date:** [July 3, 2023, 10:39pm UTC](https://community.sparkfun.com/t/recover-bricked-bus-pirate-after-firmware-upgrade/45857/2 "2023-07-03T22:39:10Z")

</div>

This might not be a direct answer, but take a look at [http://dangerousprototypes.com/docs/Bus … g\_tutorial](http://dangerousprototypes.com/docs/Bus_Pirate_v3_PIC_24FJ_blinking_LED_programming_tutorial) (scroll through the whole thing, there’s a link to their forum and bootloader app near the bottom) and maybe click around both the site and forums to see if what you’re after is in there

---

<div class="post-metadata">

**Author:** ![eterX](https://avatars.discourse-cdn.com/v4/letter/e/97f17d/32.png) [@eterX](https://community.sparkfun.com/u/eterX)\
**Post date:** [July 4, 2023, 12:13am UTC](https://community.sparkfun.com/t/recover-bricked-bus-pirate-after-firmware-upgrade/45857/3 "2023-07-04T00:13:09Z")

</div>

Hi TS,

It worked!! 🙂

At first glance the section “Restore Original firmware” seemed to bring no new info, because it leads to the official documentation. But once there, I noticed this community repo I haven’t tried out:

[https://github.com/mikebdp2/Bus\_Pirate](https://github.com/mikebdp2/Bus_Pirate)

Some of the .hex files there work fine. At least BP prompt is back! (tested hex 6.1, 6.2beta and 6.3beta under package\_legacy/BPv3-firmware/old-versions)

Thank you very much!