Dangerous Prototypes Open Source Hardware

V4 firmware doesn't work, *Unable to connect to device...*, etc

January 20, 2010, 05:42:37 pm

Hi!
I got my BPv3, updated the firmware to v3.5 and used it afterwards successfully. Now I've tried to upgrade to 4.1 and thats where it fails.

• I connect the BP to USB
• start the PIC24F Quick Programmer
• select the correct port
• hit *Connect to Device*
• the MODE LED lights up

A few seconds later the utility says *Unable to connect to device...*. The MODE LED stays on.
Tested on 2 WinXP PCs without any difference. Anyone any clues what might be wrong?

Re: Programmer: *Unable to connect to device...*

Reply #1 – January 20, 2010, 05:47:29 pm

Hi uhze! V4 firmware requires an upgrade to the v4 bootloader:
http://dangerousprototypes.com/2010/01/ ... 4-upgrade/

After you update,  P24QP is not compatible with the new bootloader. Use the ds30 Loader instead.

Re: V4 firmware doesn't work, *Unable to connect to device...*, etc

Reply #2 – January 20, 2010, 07:54:45 pm

Hi Ian,

I think the title should read "Cannot Connect to V2 Bootloader".

When connecting in "Step 2" of How-to: Bus Pirate bootloader v4 upgrade, it wouldn't connect under Virtualbox non-free, but now it works.

I'm not sure exactly why it works now, but the only thing I can think of is that I restarted after installing the FT232R drivers.

Re: V4 firmware doesn't work, *Unable to connect to device...*, etc

Reply #3 – January 20, 2010, 10:10:58 pm

I'm having the same problem on a v3 and a v2.go. It will not find the buspirate when using the P24QP to try to install the bootloader as stated in the install file. If I run the ds30 loader it says
Found unknown device id(192) fw ver.9.9.9 This is because I don't think I've upgraded to the bootloader which is what I'm trying to do. Help?

Re: V4 firmware doesn't work, *Unable to connect to device...*, etc

Reply #4 – January 20, 2010, 10:29:26 pm

AAARRRWWWW  I this step:

• place jumper on PGC/PGD pins!

The upgrade to v4 went fine afterwards.
Sorry for the noise!

Re: V4 firmware doesn't work, *Unable to connect to device...*, etc

Reply #5 – January 21, 2010, 12:31:19 am

No problem uhze. I think this project needs an update faq Since I'm (a bit) involved in the development of the new bootloader and utils around it some steps are logical to me, but not to other people I guess. Following the steps (precisely) should do the trick.

Franklin, what did you try and which step from the blog are you at?

For v3 the steps basicly are:
- unplug the buspirate
- place jumper (pgc-pgd), plug the buspirate in
- load the upgrader to the buspirate using P24Q loader (old program)
- unplug the buspirate
- place jumper in normal position (gnd-pgd)
- plug the buspirate in
- connect using terminal program
- type yes
- wait til the mode led blinks (make sure the mode led works)
- unplug the buspirate
- place jumper (pgc-pgd)
- use the new program (ds30loader or the commandline util) to upload an v4+ buspirate version
- place jumper back normal position (pgd-gnd)
- unplug buspirate
- plug buspirate in
- you're now at v4+

for v2.go the pinout is a bit different, and should be checked (i don't have a v2.go and have no experience with it!!)

Re: V4 firmware doesn't work, *Unable to connect to device...*, etc

Reply #6 – January 21, 2010, 08:16:13 am

@Franklin97355 - Did you put a jumper over the PGC and PGD pins before plugging in the Bus Pirate? Do you see the MODE LED light? Are you using the v2 to v4 upgrade package?

You're correct, the ds30 Loader utility is only compatible with the v4 bootloader, it won't connect to the existing v2 bootloader.

NOTE: Sjaak's instructions are correct, except that "place jumper in normal position (gnd-pgd)" will also enter the bootloader on a v2go. Just remove the jumper on v2go.

Re: V4 firmware doesn't work, *Unable to connect to device...*, etc

Reply #7 – January 23, 2010, 11:43:27 pm

Well... After re-reading the F$%#ing instructions (you know what an ego buster that can be) and the other posts here I was sucessful in getting both my devices up to date. Except for a few timeouts when trying to find the device with ds30 all went painlessly. Now I need to get to using the thing (tutorials)
Thanks for the help and a very useful product.