Buspirate issues solved?

Posted on Friday, December 20th, 2013 in BP v3, Bus Pirate by Sjaak


Recently the forum is flooded with people that are experiencing troubles with the Buspirate v3.6. Pieter in the forum was no exception. He first tried the Buspirate on his Windows 8.1 and Vista machine and went to the forum after finding out hise buspirate didn’t respond to anything. The supportteam in the forum suspected the PIC was not programmed or counterfeit FTDI chips were used. In the mean time Pieter tried the buspirate on more different machines and was dazzled it did work on a Crunchbang (Debian flavour) workstation. He investigated it further and tracked the error down to the latest FTDI driver (2.08.30), after de-installing and installing an earlier version of the driver (2.08.28) (scroll down to find the older version).

More info about the process on his blog and please report if this also works for you.

This entry was posted on Friday, December 20th, 2013 at 11:00 am and is filed under BP v3, Bus Pirate. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

5 Responses to “Buspirate issues solved?”

  1. Jack says:

    It’s totally possible there’s other reasons, but requiring older versions of drivers to work is a common sign of counterfeit chips, when the real vendor adds in checks for known counterfeits in the latest version. E.g. is an example of counterfeit FT232RLs which only worked when downgrading drivers (the thread then veers off into confusion over the vendor’s replacement adapters using a CP2102).

  2. Samual says:

    The FTDI driver (2.08.30) works in Windows 7 there is nothing wrong with it.

    • Pieter says:

      Samual, do you have the latest board (Bus Pirate v3.6 (apr 2012) Seeed 10/09/13)?

      Jack, makes a point. Might contact FTDI to ask them how we can detect this chip from an original.

      • Samual says:

        My board was manufactured in May,2013 but I ordered it a month ago. It the same BP v3.6 apr 2012. If the FTDI are counterfeits than Seeed should send you a replacement. I don’t think that is the case here. Can you uninstall the old driver that work and install the latest one and try again. Use this tool to unistall the driver

      • Pieter says:

        Hi Samual,

        I used the tool (that is much better then doing it manual in the device manager). Uninstalled the older version (.28) and installed the latest driver (.30). That did not work. Uninstalled (with the tool) the newer, installed the older and the Bus Pirate works again..
        The question is, did FTDI changed something in their latest .30 drivers to prevent counterfeit chips from working. If that is the case then I am sure Seeed will send a replacement.

Leave a Reply

Notify me of followup comments via e-mail. You can also subscribe without commenting.

Recent Comments

  • Daniel: Do I comment here or on FB?
  • Craig B: Shouldn't the default be 00xxx010? Note that bit 0 appears out of order in the documentation. In that case I think the initial value is...
  • JJM: From the datasheet extract you are showing, the power up status should be 00xxx010, not 000xxx01. Bit numbering is misleading since 'measurement resolution' is apparently...
  • Jan Ciger (@janoc200): Hmm, that could actually explain why the three sensor IMU breakout I have bought a few years ago had all sorts of issues - I...
  • Travis: Is it preset to the windows 3 fingered salute?