I moved to Qt 5.3 and created a new executable. It still doesn't have a scripting engine. I also added an error message when a command reach the Bus Pirate limit of 255 characters. Wasn't there talk about raising this limit? Is it the same on the Bus Pirate V4? Anyway I made the limit configurable just in case. Google decided to remove downloads from Google code (quite a long time ago actually) so look for the external download link on the left section of the project home page http://https://code.google.com/p/buccaneers-den/
Don't worry (be happy)! I bought my Bus Pirate in April 2010. If it didn't worked flawlessly, you would have walked the plank and met Davy Jones a long long time ago ;)
No, I never saw that problem on my Bus Pirate but I have seen similar problem on other devices and it was always power related. Either the port didn't provide enough or the device wanted too much.
I took a quick look at the core USB driver and I'm quite sure this is a hardware problem. The "port x disabled by hub (EMI?)" message appear when the USB host controler raise an interrupt telling the driver that one of the hubs disabled a device. There is no way for the host controler to give a reason so the driver just reset the device and hope for the best. A comment suggest it is usually caused by Electro-Magnetic Interference but it's definitely not the only thing that can cause garbage on the USB wire. I believe a USB hub can also disable a device if it's drawing to much power. When you enable the power supplies, is there any way for the Bus PIrate to report how much amps you are using?
For the Bus Pirate to work, your serial port must be configured in 115200bauds, 8bits data, 1 stop bit, no parity and no flow control. You also need to make sure the receiver is enabled and disable all modem stuff. cfsetspeed take care of the baud rate, cfmakeraw take care of 8bits data and no parity and some of the modem settings. To do the rest, you need to add these lines:
cfsetspeed and cfmakeraw only modify the termios structure. If you want these changes to take effect, you have to send that structure to the serial driver by calling tcsetattr. Officially, you should call tcsetattr after each modification so that if it fail, you know which modification was rejected but for standard speeds and settings it's overkill. Simply add:
I realized compiling QSerialDevice under Windows is somewhat annoying. (You need to copy a header from the Qt source to your SDK installation's include directory.) Maybe that problem will appear on some Linux distro too. Anyway, I just uploaded a Windows binary to the project's download section. Direct link. No installer, just a zip file and I'm hopeful it work on every flavor of Windows.
[quote author="sqkybeaver"]are there plans to make a more graphical interface, say to be able to change settings and run scripts?[/quote]
Lots of ideas but not so many detailed plans. Scripting is something I will definitely implement although I haven't decided how and it will take a long time to do. I also want to do a scope tab and a complete vt102. As for other things, I'm not sure, I'm open to suggestions.
[quote author="electronplay"]This a good soft, but i doesn't get source from google svn I want to compil in windows XP and QT
thanks for all[/quote]
You don't need a Google id to do a checkout so unless you use a proxy blocking subversion you shouldn't have any problem getting the source. As of r8, it should link and work properly under Windows (XP and hopefully others).
Since the Bus Pirate v3 use generic vid/pid, auto-detection is impossible without talking to the device but if we talk to every FT232 and some are not Bus Pirate, who knows how they will react. Hopefully it would never initiate an auto-destruct sequence but it's still a bad idea. On the other hand, if the v4 vid/pid are truly unique, auto-detection is indeed possible although it will have to be coded in an OS specific manner.
Here is a minor update. I fixed a bug apparent when leaving binary mode and added saving/restoring of the main window geometry and the last used serial port.
Here is a little gui I'm writing for my Bus Pirate and as an exercise in Qt. It is far from finish but I thought some of you might find it useful. At the moment, It's nothing more than a modified console with support for the firmware upgrade (which might work on a v4 but I can't test it yet). I use Qt and QSerialDevice so, in theory, it should work under Linux, Windows and Mac but I only work under Linux. Compiling it should be as easy as opening the all.pro file in QtCreator and clicking run or the usual (if you know Qt) qmake/make. If enough of you are interested, I will open a repository somewhere. So what do you think?
