Firmware v4, bootloader v4 probelms FAQ/help!

[ian]

*After I upgrade to v4+ firmware my Bus Pirate doesn't work, I don't see anything in the terminal, etc.
Firmware v4+ uses a new bootloader. Install the bootloader with the upgrade utility as described here:
http://dangerousprototypes.com/2010/01/18/how-to-bus-pirate-bootloader-v4-upgrade/

*The ds30 loader application (or Pirate-Loader) says "Found unknown device id(192) fw ver.9.9.9".
The ds30 Loader utility is only compatible with the v4 bootloader, it won't connect to the existing v2 bootloader. Upgrade to the new bootloader before trying to install firmware v4+:
http://dangerousprototypes.com/2010/01/18/how-to-bus-pirate-bootloader-v4-upgrade/

*ds30 Loader doesn't work in Linux/MaxOSX/etc.
Install Mono, or try the console upgrade utility for Linux/MacOSX/Windows:
http://dangerousprototypes.com/2010/01/19/bus-pirate-bootloader-v4-console-for-linux-mac/

*After upgrading to bootloader v4+ P24QP.exe (P24QP.py) will not connect.
P24QP.exe (P24QP.py) is only compatible with the v2 bootloader, use the ds30 Loader utility, or the Linux/MacOSX/Windows console utility.

*STK500v2/OpenOCD/USBPICPROG firmwares don't work after upgrading to bootloader v4.
The v4 bootloader uses a slightly different firmware. Updated versions are included in the v4+ firmware archive (BusPirate.firmware.v4.x.zip) at the Google Code page:
http://code.google.com/p/the-bus-pirate/downloads/list

*I can't complete the v2 to v4 upgrade.
Read the illustrated upgrade guide:
http://dangerousprototypes.com/2010/01/18/how-to-bus-pirate-bootloader-v4-upgrade/

make sure you follow all these steps:

- unplug the buspirate
- place jumper on pgc-pgd pins, plug the buspirate in
- load the upgrader to the buspirate using P24Q loader (old program)
- unplug the buspirate
- remove the jumper
- plug the buspirate in
- connect using terminal program
- type yes
- wait for "success!", the mode led should blink (make sure the mode led works)
- unplug the buspirate
- place jumper (pgc-pgd)
- use the new program (ds30loader or the commandline util) to upload a v4+ buspirate firmware
- unplug buspirate
- remove the jumper
- plug buspirate in
- you're now at v4+

*I found an upgrade to v4.2, how do I use it?*
V4.2 is the same as v4.1, but it is programmed directly with a PIC programmer instead of through the install process. The different version number is just to help us know who got the v4 bootloader by upgrade or direct install.

[MickM]

Hi;
  I am trying to upgrade to 5.6.
Shorted PGD and PGC.

This is the tera term log:

HiZ> i
Bus Pirate v3a
Firmware v5.5 (r464) Bootloader v4.1
DEVID:0x0447 REVID:0x3003 (A3)
http://dangerousprototypes.com
HiZ>

I quit Tera Term.

I downloaded the 5.6 package and unzipped it.
I ran the ds30-loader-gui  program that was in the zip.
I selected the 5.6.hex and also tried the bootloader 4.4.hex

The two buttons  "Write program and Write Eprom" are greyed out.
It parses either file fine.
The last lines are both: "0 eeprom words found, 0 config words found.
Pressing "download" gives a "nothing to do" box.

Ok so I tried pirate-loader.exe.

I get "no reply from bootloader"

So my question is, is this a bug or is my BP messed up?

Thanks
 Mick M.

[Sjaak]

You should not flash the bootloader4.4.hex! This is mend to be flashed with a real picprogrammer.

[ian]

Hi Mick - Here's the Bus Pirate upgrade instructions:
http://dangerousprototypes.com/docs/Ds30_Loader_GUI

There are two ways to enter the bootloader. Connect the PGC/PGD pins and then power up the Bus Pirate, or type $ into the terminal and then exit (after confirming with Y). In both the MODE LED should light.

The bootloader file is just for programming a new PIC (see !Bootloader-v4.4.txt in the upgrade archive for more).

When you loaded the bootloader with ds30Loader it triggered the overwrite protection in ds30Loader. ds30loader prevents writes now. You need to delete the upgrade folder and start from a new copy.

I think pirate loader says no reply because you are not actually in bootloader mode.

Please let us know if this helps.

[MickM]

HiZ>
Bus Pirate v3a
Firmware v5.6 (r473)  Bootloader v4.1
DEVID:0x0447 REVID:0x3003 (A3)
http://dangerousprototypes.com
Syntax error at char 2
HiZ>


Thanks !!
You guys are very quick to reply.
When or should I bother to update the bootloader?
Is 4.4 much better than 4.1?

Mick M.

[ian]

Thanks for the update, I'm glad you got it going.

Here's some info on the bootloaders:
http://dangerousprototypes.com/docs/V4.x_to_v4.3_upgrade

[Sjaak]

4.4 is the same as 4.3. The difference is that 4.4 is flashed with a picprogrammmer and 4.3 is uploaded by an installer.

4.3/4.4 is a bit better protected then 4.1/4.2 but both are perfectly capable of running the bp. :)

[thebroker]

I have load the last OpenOCD firmware in my bus pirate v3b. After this when I can connect using my terminal software to the bus pirate, but without response.

After I tryed to ds30 loader for recover the las firmware, but the loader return "Found unknown device id(0) fw ver. 9.9.9"

I tryed to install the firmware using P24QP with a jumper in PGD and PGC, but when I press the erase data or write device button I receive a "Failed to write device".

How can I change the firmware?

[ian]

That firmware is an old test part of the development process. There's no terminal or anything, it only works with openOCD. The OpenOCD support is integrated into the latest Bus Pirate firmware.

P24QP does not work with the new bootloader in v4+ firmware (factory installed in v3b).

Please try with the jumper but use the ds30 Loader. Here's the guide for changing firmware:
http://dangerousprototypes.com/docs/Ds30_Loader_GUI

[thebroker]

Do not work with ds30 loader.

I obtain the next message:

Code: [Select]

Initiating download...
      Searching for bl . (discarded null byte)
      Found unknown device id(0) fw ver. 9.9.9
      Tx 1 byte / Rx 2 bytes / 0,2s

Whe I try to check the bootloader I receive:

Code: [Select]

Searching for bl . (discarded null byte)
Found unknown device id(0) fw ver. 9.9.9


[ian]

What happens when you put a jumper between the PGD and PGC pins and then plug in the Bus Pirate? The MODE LED should light. Is the MODE LED on when you try to connect?

Is DS30 Loader pointing at the correct serial port?

What operating system are you using?

If you have a v3b it should have shipped with the v4 bootloader, and it should be impossible to brick the v4 bootloader once it's installed.

[thebroker]

The Mode led is always light with and without jumper.

About the DS30 loader I am very sure that have the right serial port configuration, because I used this configuration for upload the hex file. Otherwise I have only two serial ports and I tryed with both.

I am using windows.

Before to upload the the openocd hex file I updated the firmware to v5.7, and worked fine!

[ian]

Thank you for the details. I would like to examine the memory of your Bus Pirate to see what happened. I'll PM you with some instructions.