Comments on: Bus Pirate: Firmware upgrades on Linux, OSX http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/ A new open source hardware project every month Fri, 30 Jul 2010 00:21:02 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: John http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-3349 John Mon, 26 Jul 2010 14:14:59 +0000 http://dangerousprototypes.com/?p=285#comment-3349 I panicked too soon. I continued to follow the instructions (derp) and ran this next (with the jumper in place): ./pirate-loader_lnx --dev=/dev/ttyUSB0 --hex=BPv3\&v2go/BPv3-Firmware-v5.0.hex and lo and behold, success. Sorry I got jumpy, thanks to the devs for making this more idiot-proof than I anticipated. John I panicked too soon. I continued to follow the instructions (derp) and ran this next (with the jumper in place):
./pirate-loader_lnx –dev=/dev/ttyUSB0 –hex=BPv3\&v2go/BPv3-Firmware-v5.0.hex

and lo and behold, success. Sorry I got jumpy, thanks to the devs for making this more idiot-proof than I anticipated.

John

]]> By: John http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-3348 John Mon, 26 Jul 2010 14:06:04 +0000 http://dangerousprototypes.com/?p=285#comment-3348 Well, I got impatient and it looks like I bricked my brand new BP within 20 minutes of unsealing it. I did the first part of the bootloader upgrade: python ./P24qp.py -a BPv3-v2blupdaterVa3-v4.1.hex -s /dev/ttyUSB0 -v ..... Reading 256 bytes from address 0x0000AB80 Write operation complete. Verified Okay. Verification complete, switching to user mode Then rebooted it with minicom attached and typed "yes" when it asked me if I was sure I wanted to overwrite the bootloader: Found bootloader v unknown (probably v2) Will install bootloader v4.1 Type 'Yes' to program the new bootloader. Disconnect power if unsure (no harm done). yes Erasing 0xA400... done Erasing 0xA800... done Writing row 0 1 2 3 4 5 6 7 done Erasing 0x0000... done Writing row 0... done Success! Upload new firmware with the ds30 Loader app to complete the upgrade. This is where I screwed up. I tried to upload a second .hex file: johng@bugsy:~/tmp/upgrader$ python ./P24qp.py -a ../v4firmware/BPv3-Firmware-v4.1.hex -s /dev/ttyUSB0 -v Using Serial Port /dev/ttyUSB0 @ 9600 Reading 4 bytes from address 0x00FF0000 RX Error: 0 bytes received Error reading from device! Device with ID: 65535 not listed in the config file! and now I've got nothing. even P24qp.py -i -s /dev/ttyUSB0 returns nothing but an error. I get nothing at the serial prompt, either. I don't own a PIC programmer (yet). Where do I go from here? John Well, I got impatient and it looks like I bricked my brand new BP within 20 minutes of unsealing it.
I did the first part of the bootloader upgrade:
python ./P24qp.py -a BPv3-v2blupdaterVa3-v4.1.hex -s /dev/ttyUSB0 -v
…..
Reading 256 bytes from address 0×0000AB80
Write operation complete.
Verified Okay.
Verification complete, switching to user mode

Then rebooted it with minicom attached and typed “yes” when it asked me if I was sure I wanted to overwrite the bootloader:
Found bootloader v unknown (probably v2)
Will install bootloader v4.1

Type ‘Yes’ to program the new bootloader.
Disconnect power if unsure (no harm done).

yes

Erasing 0xA400… done
Erasing 0xA800… done
Writing row 0 1 2 3 4 5 6 7 done
Erasing 0×0000… done
Writing row 0… done

Success!
Upload new firmware with the ds30 Loader app to complete the upgrade.

This is where I screwed up.
I tried to upload a second .hex file:
johng@bugsy:~/tmp/upgrader$ python ./P24qp.py -a ../v4firmware/BPv3-Firmware-v4.1.hex -s /dev/ttyUSB0 -v
Using Serial Port /dev/ttyUSB0 @ 9600
Reading 4 bytes from address 0×00FF0000
RX Error: 0 bytes received
Error reading from device!
Device with ID: 65535 not listed in the config file!

and now I’ve got nothing. even P24qp.py -i -s /dev/ttyUSB0 returns nothing but an error. I get nothing at the serial prompt, either.
I don’t own a PIC programmer (yet).

Where do I go from here?
John

]]> By: Ian http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-2623 Ian Mon, 31 May 2010 09:29:51 +0000 http://dangerousprototypes.com/?p=285#comment-2623 No problem, I glad you got it working. Thanks for the update. No problem, I glad you got it working. Thanks for the update.

]]> By: Tijs http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-2622 Tijs Mon, 31 May 2010 09:21:13 +0000 http://dangerousprototypes.com/?p=285#comment-2622 I downloaded the laters (4.2) bootloader hex into the BP with a pic programmer, used the bootloader to install the firmware. Everything is working fine again! (needed a programmer though, so for anybody else: DO NOT USE P24qp.py TO PROGRAM v4 firm, NEVER. Only the bootloader-upgrader. As stated above..) Thanx Ian. I downloaded the laters (4.2) bootloader hex into the BP with a pic programmer, used the bootloader to install the firmware. Everything is working fine again! (needed a programmer though, so for anybody else: DO NOT USE P24qp.py TO PROGRAM v4 firm, NEVER. Only the bootloader-upgrader. As stated above..)

Thanx Ian.

]]> By: Ian http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-2529 Ian Thu, 27 May 2010 11:55:23 +0000 http://dangerousprototypes.com/?p=285#comment-2529 the updater does, but you shouldn't use that, it installs the new bootloader using the old one. Download the latest firmware archive and use the bootloader.hex from there. the updater does, but you shouldn’t use that, it installs the new bootloader using the old one. Download the latest firmware archive and use the bootloader.hex from there.

]]> By: Tijs http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-2528 Tijs Thu, 27 May 2010 11:23:13 +0000 http://dangerousprototypes.com/?p=285#comment-2528 So the bootloader hex (BPv3-v2blupdaterVa3-v4.1.hex) does contain the config word? (I dont want to keep programming the pic with 5v... So hoping that once will be enough) So the bootloader hex (BPv3-v2blupdaterVa3-v4.1.hex) does contain the config word? (I dont want to keep programming the pic with 5v… So hoping that once will be enough)

]]> By: Ian http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-2527 Ian Thu, 27 May 2010 11:21:05 +0000 http://dangerousprototypes.com/?p=285#comment-2527 No problem, sorry about the confusion. The bootloader and firmware are separate. Program the bootloader .hex with the programmer, then connect with the bootloader and load the firmware. No problem, sorry about the confusion. The bootloader and firmware are separate. Program the bootloader .hex with the programmer, then connect with the bootloader and load the firmware.

]]> By: Tijs http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-2526 Tijs Thu, 27 May 2010 11:13:53 +0000 http://dangerousprototypes.com/?p=285#comment-2526 Thanx by the way ;) Thanx by the way ;)

]]> By: Tijs http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-2525 Tijs Thu, 27 May 2010 11:13:36 +0000 http://dangerousprototypes.com/?p=285#comment-2525 Yes i did try to upload the v4 firmware. (Because i thought the bootloader upgrade worked) After that i was able to connect to the BP once and it said "Firmware version 4.1, bootloader 255.255" Next powerup it was gone. I think the v4 fw try screwed the config word indeed and it now runs with the wrong clock in mind. Ill try to flash it with the 5v programmer... Does the v4 firmware contain everything? config+firmware+bootloader? I mean if i get that hex in, is the procedure then completed? Or should i just try to set the config word only and then install the bootloader again? (since 1.2 is obviously still in there..) And what is the config word then? Yes i did try to upload the v4 firmware. (Because i thought the bootloader upgrade worked)
After that i was able to connect to the BP once and it said “Firmware version 4.1, bootloader 255.255″ Next powerup it was gone.

I think the v4 fw try screwed the config word indeed and it now runs with the wrong clock in mind. Ill try to flash it with the 5v programmer…

Does the v4 firmware contain everything? config+firmware+bootloader? I mean if i get that hex in, is the procedure then completed? Or should i just try to set the config word only and then install the bootloader again? (since 1.2 is obviously still in there..)
And what is the config word then?

]]> By: Ian http://dangerousprototypes.com/2009/08/06/bus-pirate-firmware-upgrades-on-linux-osx/#comment-2524 Ian Thu, 27 May 2010 11:04:14 +0000 http://dangerousprototypes.com/?p=285#comment-2524 I'm not really sure, the updater contains the config bits and you should be able to bootload it as much as you want without problem. Did you try to upload the actual v4 firmware with the .py uploader as well? That will do it every time :( I'm not sure about the programmer. SparkFun shipped a bunch with 5volt regulators instead of 3v3 regulators, and they worked fine (for a while...). You might be able to get away with programming the PIC at 5volts if the programmer supports the 24fj64ga002. I’m not really sure, the updater contains the config bits and you should be able to bootload it as much as you want without problem. Did you try to upload the actual v4 firmware with the .py uploader as well? That will do it every time :(

I’m not sure about the programmer. SparkFun shipped a bunch with 5volt regulators instead of 3v3 regulators, and they worked fine (for a while…). You might be able to get away with programming the PIC at 5volts if the programmer supports the 24fj64ga002.

]]>