I got my BPv4 some time ago and unfortunately I don't get around using it much because my V3.Xes lay on my bench anyway. Long sotry short, I updated to the 6.1 firmware release today (which was successful) and tried to use the BP with my Win7 PC (32bit win on 64 bit AMD). After installing the supplied .inf-file (using device manager > update driver), Windows is showing me a COM12 named Bus Pirate v4 in device manager. I can also successfully connect to the COM-port, but no matter what I send to it in no matter which baud rate (115200 also ;) ) with no matter which CR or LF or both, it does not respond in any way.
Using my Android 4.? Tablet it works like a charm...
So i suppose it is a Problem with my PC (or the USB-stack of the BP??). I tried both Putty and hTerm with no luck at all. Maybe there is a fix which I didn't find? I tried the 6.2 beta1 firmware out of the forum but that one doesn't work at all, the USB LED is on all the time and Win7 is telling me to connect it to a USB 2.0 port (wtf?). So I downgraded to 6.1 again...
I would really appreciate some help, thanks in advance, Tobi DK7SCH
I got my sniffer a few weeks before and I am pretty impressed. It is a really neat tool but I think there are some issues (I've searched but havent found anything so I hope I'm not preaching to the choir):
1) Firmware updates are a mess: I wanted to use the new 2.12 test release. To do so I noticed (!) that I had a completely old PIC-firmware. So I wanted to update it but as a matter of fact it turned out that this isn't quite ... intuitive. I needed to do the following things: a) search for actual (stable) firmware image b) search for update how-to c) find the right firmware in the bunch of files d) run update script (that was easy) Wouldn't it be nice if there was a tool which automatically checked the sniffer firmware and bitstream version and compared it to the latest available files online? And then automatically updates the sniffer? Just like apt? And/or in which you could choose which bitstream you wanted to use? What do you think?
2) Now I'm using the v06-16MHz firmware with the 2.12 bitstream. It works really nice on my XP machine but I noticed when I use really slow sample frequencies (like 1kHz) the shiffer captures data but the client runs the capturing-progress-bar when the capturing has finished. Is that on purpose or is it not? I thought the bar was indicating capturing progress...