Skip to main content

Messages

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - ipatch

16
Bus Pirate Support / Firmware 5.8 what's new?
I just stopped by the google code page and saw that a new firmware 5.8 is up, and has only been up for three days.  I noticed the size of 5.8 is almost double the size of its predecessor.  Didn't really see a feature list or any info on what FW 5.8 is bringing to the table.  I didn't see any topics added here in the forum so I thought I would start one.
17
Bus Pirate Support / Re: Getting started
[quote author="pwillard"]
A nice free muti-purpose serial terminal is PUTTY.  Though mainly intended as a telnet/SSH terminal... it was updated to support serial comms.  Very customizable and just a teeny bit less "klunky" than Realterm.  Realterm has a lot more fiddly things to play with but as with all fiddly things... that are just as likely to cause you headaches as they are to help you out.

http://www.chiark.greenend.org.uk/~sgtatham/putty/
[/quote]

[dancing banana] :P
18
Bus Pirate Support / Re: Don't recommend upgrading the BP @ 2AM in the morning :-/
[quote author="ian"]
hey ipatch - Did p24qp.py connect correctly and upload the v4 firmware? I thought that the updater erased the old bootloader after the upgrade in a way that it wouldn't connect.
[/quote]

Hey ian I am/was under the impression that the p24qp.py python script was only designed to update the bootloader on pre v4 bootloader BPs.  When I tried to use it to upload the Firmware for the BP it just crapped out and gave me a 65xxx error or something along those lines.  So, I ended up using pirate-loader_mac to update the firmware after the bootloader was updated using the p24qp.py script.

I must say that I was I glad I could do all this updating using my native OS, which is OS X because trying to use the BP via virtualbox with Windows XP was becoming a nuisance.
21
Bus Pirate Support / Don't recommend upgrading the BP @ 2AM in the morning :-/
Well, I started messing around with the BP again the other day, and the first thing I remember wanting to do when I walked away from it a couple of months ago was to upgrade the firmware.  In order to do that I have to upgrade the bootloader because I have BPv3a which came preloaded with firmware v2.4-Seed according to the i command issued in ZTerm.  I did some googlefu and came across a couple links discussing the upgrade process for v2 bootloaders.

This video: http://blip.tv/file/2780303

and this website: http://s9y.ereet.st/index.php?/archives ... -OS-X.html

were both helpful in instructing how to upgrade a BP bootloader in OS X.

I downloaded pySerial modulde and began upgrading the bootloader.  (Yes I had a jumper connecting PGC and PGD).  The bootloader seemed to handle the upgrade sucessfully because I removed the jumper and went into ZTerm after the upgrade and typed yes when prompted, and then exited ZTerm.

I think this is where I started to venture off in the wrong direction.  I then decided to use the same P24qp.py script to install the firware that came with the bootloader/Firmware upgrade zip file.  I was copying and pasting in terminal and when I pasted Terminal decided to run the command without even waiting for me to hit return/enter. *Thanks :-/*  I think this didn't really make a difference because the P24qp.py script was not designed to load v4 firmware onto the BP, so I think this is how I bricked my BP.  After doing some more reading I found out that I should have used the pirate-loader_mac to install the v4 firmware after upgrading the bootloader.  I tried using the pirate-loader_mac to install the v4 firmware, but it was unable too, and this it what it is telling me.

Code: [Select]
capin@betty upgrader $ ./pirate-loader_mac --dev=/dev/tty.usbserial-A700dzDq --hex=BPv3-Firmware-v4.1.hex 
+++++++++++++++++++++++++++++++++++++++++++
+ Pirate-Loader for BP with Bootloader v4 +
+++++++++++++++++++++++++++++++++++++++++++

Parsing HEX file [BPv3-Firmware-v4.1.hex]
Found 21503 words (64509 bytes)
Fixing bootloader/userprogram jumps
Opening serial device /dev/tty.usbserial-A700dzDq...OK
Configuring serial port settings...OK
Sending Hello to the Bootloader...ERROR
No reply from the bootloader, or invalid reply received: 0
Please make sure that PGND and PGC are connected, replug the devide and try again

I tried seeing if I could access the BP via ZTerm, but I am unable.  Am I going to have to go the PicKit2 route to get the BP out of brick mode?
23
Bus Pirate Support / Re: BP Bus Pirate Probe Kit, this way or that way?
[quote author="ian"]
Hey ipatch - I usually use it the second way, and that's how the signals are labeled on the help menu. There's a bit about this in the manual here:
http://dangerousprototypes.com/docs/Bus ... le_pinouts

And some case stickers/labels here:
http://dangerousprototypes.com/docs/Com ... le_pinouts

The vb update was a very minor manufacturing update, there's no functional difference between the v3a and v3b.
[/quote]

Thanks.
24
Bus Pirate Support / BP Bus Pirate Probe Kit, this way or that way?
I bought a BPv3a a couple months back before version BPv3b came out :-/ and decided to purchase the probe kit that seeedstudio.com sells with it.  I asked this question before but did not get a real cut and dry answer, so I thought I would try again.  There are two different ways to hook up the probe kit as the pin outs are not keyed on either the probe kit or BP.  From an earlier post, I read the way the probe kit is installed onto the BP depends upon what purpose the probe kit is going to be used for.  I interpret that as meaning that the probe kit is designed to be installed in both ways as shown in the pictures below.

Here is the first way:


Here is the second way:


Also, I decided to lengthen the separation between the probe cables.  Here is a picture.  And yes I fixed the brown wire.  That was the first one I tried to lengthen the separation on.
25
Bus Pirate Support / Re: Noob with some simple questions
[quote author="Sjaak"]
It sure can be connected backwards, but if you take care how you connect the BP it is ok. The pins of the buspirate and also the voltage regs can tolerate quite much, so it will be ok.

Happy hacking with it! ;)
[/quote]

So your saying it can be connected backwards, to perform different readings with the probes?
26
Bus Pirate Support / Re: Noob with some simple questions
[quote author="Sjaak"]
No problem :)

It is the mini usb-b variant. It is supplied with external HD, MP3/4players, photocamera's and such, so, unless you didn't bought an usb device for a long time, you have it already. ;)
[/quote]

Hey so I received my bus pirate today, my first reaction was wow the packaging box had been to hell and back.



Second reaction, wow this thing is a lot smaller than I expected (*insert joke here*)

And my third thought, this thing connects using a mini-b http://en.wikipedia.org/wiki/File:Types-usb_new.svg which is the same type of connector the ps3 controller uses, so I am good to go :)



And finally one last thing, is it possible to connect the probe cables backwards?  This is how I connected the probes to the bus pirate, neither the pins on the bus pirate, or the connector block on the probe were keyed, so the probes could be connected two different ways.



cheers
-ipatch
28
Bus Pirate Support / Re: Noob with some simple questions
[quote author="Sjaak"]
Hi,

The FTDI chip is already on the buspirate, so you only need to have an USB cable to mini USB (which most people have lying around) or on their website: http://www.seeedstudio.com/depot/mini-u ... l?cPath=34

The probe kit is suitable for hobby use (they use cheap probes, which can wear or get loose easily). I personally prefer the http://www.seeedstudio.com/depot/1-pin- ... l?cPath=34 to connect to a breadboard (together with http://www.seeedstudio.com/depot/breadb ... l?cPath=34 or some headers)

They (seeed) will be assembling new buspirates, but you can backorder them (see also the frontpage of dangerousprototypes.com)

edit: like ian says :D
[/quote]

hey on that usb cable i couldn't tell why type of connector connects to the bus pirate.  I know there are several different connector types.
http://en.wikipedia.org/wiki/File:Types-usb_new.svg

cheers

and thanks for the helpful information.

-ipatch
29
Bus Pirate Support / Noob with some simple questions
Alright, so I recently ordered a bus pirate V3 from seeedstudio.  I have been waiting for about tens days to receive the item in the mail.  I am aware that the item is being shipped from Hong Kong, and the website said it could take up to 30 days to receive the item.  So my first question is, since I placed an order for the bus pirate V3, I am going to need a USB FTDI cable to interface it with my computer.  I did not see any for sale on the seeedstudio website, but I did find this http://www.sparkfun.com/commerce/produc ... ts_id=9717 <- is that the cable I need to interface the bus pirate through the USB port on my computer?

And if so, is that the best deal I am going to find on that cable?

Also, I ordered this -> bus pirate probe kit Is this a good probe kit for connecting to various components of integrated circuits?

And, my last question, I noticed that on the seeedstudio that it says the bus pirate is out of stock, so I am going to be waiting indefinitely to receive my product, or is there a new batch being made? Thanks for reading and I look forward to being an active member of this message board.

cheers
-ipatch

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01872450920session_write_close ( )...(null):0
20.01902582536ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01902583312Database_MySQL->query( ).../DatabaseHandler.php:119
40.08872722072Database_MySQL->error( ).../Db-mysql.class.php:273