Difference between revisions of "Bus pirate"
From Fixme.ch
| Line 1: | Line 1: | ||
| + | == Information == | ||
| + | * Wikipedia : http://en.wikipedia.org/wiki/Bus_Pirate | ||
| + | * Bus pirate 3.6: http://dangerousprototypes.com/docs/Bus_Pirate | ||
| + | |||
== Connection == | == Connection == | ||
# do a dmesg to find which tty the bus pirate is connected to | # do a dmesg to find which tty the bus pirate is connected to | ||
Revision as of 12:31, 13 September 2012
Information
- Wikipedia : http://en.wikipedia.org/wiki/Bus_Pirate
- Bus pirate 3.6: http://dangerousprototypes.com/docs/Bus_Pirate
Connection
- do a dmesg to find which tty the bus pirate is connected to
- check if you have the write and read right on the tty before you connect to it
- do a screen /dev/buspirate 115200 8N1
- you will be prompt with a nice prompt.
- If you still don't have a prompt, type enter, you will have a shell.
logic sniffer
You can use the bus pirate as a logic sniffer. I would recommand using the Open bench logic for this. You can use this tutorial : http://dangerousprototypes.com/2012/02/12/sniffing-spi-data-with-bus-pirate/ Which is designed by the bus pirate constructor to sniff data Note that this can be used only up to 5 input.
