Sjaak: I've just noticed Ril3y's version before reading your comment. I think his version is the best from a usability and aesthetic standpoint. I let Seeed know about Ril3y's case and hopefully they can team up and provide lower shipping prices. As for the PCB porn, yeah, I'm dying for it.
Ian: Until Seeed doesn't team up with Ril3y I think it'd make sense to place a link to some relevant place like http://code.google.com/p/the-bus-pirate/ where buyers could order his superior cases.
The case has a very serious usability problem: The LEDs cannot be seen.
How about providing a translucent case instead of the opaque case? The LEDs could be seen and the vision of the PCB is pure geek porn. The injection mold must be already ready for the case, so it's a matter of using a different plastic which shouldn't cost a dime manufacturing-wise, right?
The correct udev rule that worked for me and for my friend is: SUBSYSTEM==â€tty†ATTRS{idVendor}==â€0403″ ATTRS{idProduct}==â€6001″ ATTRS{serial}==â€A7004IdU†MODE=â€0660″ SYMLINK+=â€bus_pirateâ€
So the hardware works perfectly, sorry for the false alarm.
I don't even get any LED flashing when pressing a key in minicom. Such discussions make me wonder whether any in house testing is done before shipping. I'd gladly pay some extra dollar just to not have to deal with such issues.
Thank you very much for the offer, but my friend is pretty skilled regarding electronics, so let's see whether he can make it work or fix it and if everything fails I'll send it to you.
I've just tried it with Windows and I got essentially the same results. When I plug it in COM3 appears as a USB serial port and I can connect to it using teraterm but no matter what I type I can't see a damn thing in the terminal.
A good friend of mine has a bus pirate working so I'll send mine to him and will see whether it's alive.
I'm not sure where should I look for the Hardware Handshaking option. Do you mean the Hardware Flow Control option? My configuration is the same as Mike's on his screenshot, except I use /dev/buspirate (which does exist on my system).
laci@nitehawk:~/download/buspirate$ ./P24qp.py -i -s /dev/buspirate Using Serial Port /dev/buspirate @ 115200 Reading 4 bytes from address 0x00FF0000 Traceback (most recent call last): File "./P24qp.py", line 696, in p = PIC24F_Prog(Config, SerialPort) File "./P24qp.py", line 294, in __init__ device = self.GetDevice() File "./P24qp.py", line 335, in GetDevice device_data = self.ReadFlash(0xFF0000, 4) File "./P24qp.py", line 637, in ReadFlash data += self.BootloaderCMD("RD_FLASH", args) File "./P24qp.py", line 481, in BootloaderCMD self.TX_PKT(data) File "./P24qp.py", line 360, in TX_PKT self.ser.write(STX) File "/usr/lib/python2.6/dist-packages/serial/serialposix.py", line 328, in write if self.fd is None: raise portNotOpenError serial.serialutil.SerialException: Port not open
Of course, Bus Pirate sits on /dev/buspirate. As I mentioned minicom detects whether or not it's plugged in.
In minicom only VT102 and ANSI terminal emulation is possible, no other choices are present, but it shouldn't be a problem because Mike Szczys succeeded using VT102.
Unfortunately there's very little documentation out there about using Bus Pirate on Linux, but it shouldn't be a difficult task I guess.
Just as the subject says. I ordered this BPv3a from Seeed and "SEP 2009" is printed on the PCB. I tried to get it working by following the instructions in the blog posts of Mike Szczys.
Minicom detects if I plug out the Bus Pirate because it reports me that it cannot access /dev/buspirate in this case. The power LED is on when the Bus Pirate is plugged in. My minicom status line is CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.3 | VT102 | Offline
The injection mold must be already ready for the case, so it's a matter of using a different plastic which shouldn't cost a dime manufacturing-wise, right?