Equipment/Bus Pirate: Difference between revisions

From London Hackspace Wiki
No edit summary
 
(8 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{EquipmentInfobox
| name = Bus pirate <!-- Name of the item. -->
| image = Hackspace_Unknown.png <!-- Image of the item. Leave with placeholder image if none exists. -->
| model = Unknown <!-- Model -->
| category = Equipment <!-- Main category. Please leave alone to keep item in this category -->
| subcat = Test equipment <!-- Sub-category if one exists. Please check main listing to see other categories contained within the main one -->
| status = Good working order <!-- Set to one of; Good working order, Faulty, Out of order, Under construction, Out of consumables, Scrapped, or Unknown -->
| consumables = Unknown <!-- Any items used up in normal operation, such as; ink, paper, saw-blades, cutting disks, oil, etc.. -->
| accessories = Unknown <!-- Any items associated with the equipment but not consumable, such as; drill bits, safety gloves, goggles, etc.. -->
| reqtraining = <!-- Is training required to use this equipment? Yes or no. -->
| trainlink = Unknown <!-- If training is required, provide a link to training signup or contact page. Otherwise leave blank. -->
| acnode = <!-- Is the equipment ACnode locked? -->
| owner = Unknown <!-- Provide a link to owners members page if other than LHS -->
| origin = Unknown <!-- If via pledge, please link to the completed pledge page on the wiki -->
| location = Ground floor, electronics bench<!-- Floor, room/zone and location within that area -->
| maintainers = <!-- NO LINKS PLEASE; it currently breaks the template. If someone is nominated as managing the upkeep of this item, please list them here. -->
| template_ver = 1.1 <!-- Please do not change. Used for tracking out-of-date templates -->
}}
== Bus Pirate ==
=== Description ===
The Bus Pirate is a low-level interface to:
The Bus Pirate is a low-level interface to:


Line 14: Line 37:
It includes an ADC and can bit bash these protocols at the wire level.  It can also be put into UART bridge mode, acting as a simple serial port.
It includes an ADC and can bit bash these protocols at the wire level.  It can also be put into UART bridge mode, acting as a simple serial port.


Reference:
=== Reference ===
 
* [http://dangerousprototypes.com/category/bus-pirate/ Bus Pirate]
* [http://dangerousprototypes.com/category/bus-pirate/ Bus Pirate]
* [http://dangerousprototypes.com/bus-pirate-manual/ Bus Pirate manual]
* [http://dangerousprototypes.com/bus-pirate-manual/ Bus Pirate manual]
* [http://code.google.com/p/the-bus-pirate/ Latest firmware] & [http://code.google.com/p/the-bus-pirate/wiki/TOC documentation]
* [http://code.google.com/p/the-bus-pirate/ Latest firmware] & [http://code.google.com/p/the-bus-pirate/wiki/TOC documentation]


Our connector:
=== Our connector ===


  brown - GND
  brown - GND
Line 32: Line 56:
  black - MISO
  black - MISO


AVRDude bus pirate mappings:
NB This order depends on attachment as connector is symmetrical and may be inverted.
 
===Sparkfun Connectors===
 
I have noticed that the sparkfun connector and buspirate uses the following mappings
 
black – gnd
white – 3.3V
grey – 5V
purple – ADC
blue – VExtern
green – aux1
yellow – clk
orange – MOSI
red – CS
brown – MISO
 
=== AVRDude bus pirate mappings ===


  + * BusPirate      AVR Chip  
  + * BusPirate      AVR Chip  
Line 42: Line 83:
  + *      MISO  <->  MISO
  + *      MISO  <->  MISO
  + *  SCL/CLK  <->  SCK
  + *  SCL/CLK  <->  SCK
Information about the schematics to use with any of the supported protocols can be found here [http://dangerousprototypes.com/docs/images/1/1b/Bp-pin-cable-color.png]
=== How to get a shell anything UART ===
Follow this step to get a shell using the bus pirate to you UART devices.
* First find the UART baud rate for the device. You can generally find this information from the constructors manual or using an oscilloscope.Note it on a piece of paper.
* Find the connecting plug for it. Need some magic here. It mostly trying to find the GND first using tester and trying to find the voltage pin and data pin.
* Connect you bus pirate to your device.
* Find the new device using 'ls /dev/tty*'
* Start a shell. Either trough minicom or screen.
* m ( for mode)
* 3 (for selecting the UART but you can select another mode if you need another protocol)
* select your baud rate ( most common baud rate are 9600 or 115200)
* default work in most of the case to get your shell on any devices 8
* select stop bits is 1 most of the case
* enjoy your shell.
== Real life example ==
As it happened at the LHS, the bus pirate interacting with a Hitachi HM55B compass module:
[[Projects/HM55B]]
[[Category:Equipment]]
[[Category:Electronics]]

Latest revision as of 12:12, 8 August 2022

Bus pirate
Hackspace Unknown.png
Model Unknown
Sub-category Test equipment
Status Good working order
Last updated 8 August 2022 12:12:30
Consumables Unknown
Accessories Unknown
Training link Unknown
Owner Unknown
Origin Unknown
Location Ground floor, electronics bench

Bus Pirate

Description

The Bus Pirate is a low-level interface to:

  • 1-Wire
  • UART
  • I2C
  • SPI
  • JTAG
  • raw 2-wire
  • raw 3-wire
  • PC keyboard
  • HD44780 LCDs
  • MIDI

It includes an ADC and can bit bash these protocols at the wire level. It can also be put into UART bridge mode, acting as a simple serial port.

Reference

Our connector

brown - GND		
red - +3.3			 
orange - +5	
yellow - ADC		 
green - VPU		
blue - AUX
purple - CLK		
grey - MOSI		
white - CS			
black - MISO

NB This order depends on attachment as connector is symmetrical and may be inverted.

Sparkfun Connectors

I have noticed that the sparkfun connector and buspirate uses the following mappings 

black – gnd
white – 3.3V
grey – 5V
purple – ADC
blue – VExtern
green – aux1
yellow – clk
orange – MOSI
red – CS
brown – MISO

AVRDude bus pirate mappings

+ * BusPirate       AVR Chip 
+ * ---------       --------
+ *       GND  <->  GND
+ *       +5V  <->  Vcc
+ *        CS  <->  RESET
+ *      MOSI  <->  MOSI
+ *      MISO  <->  MISO
+ *   SCL/CLK  <->  SCK

Information about the schematics to use with any of the supported protocols can be found here [1]

How to get a shell anything UART

Follow this step to get a shell using the bus pirate to you UART devices.

  • First find the UART baud rate for the device. You can generally find this information from the constructors manual or using an oscilloscope.Note it on a piece of paper.
  • Find the connecting plug for it. Need some magic here. It mostly trying to find the GND first using tester and trying to find the voltage pin and data pin.
  • Connect you bus pirate to your device.
  • Find the new device using 'ls /dev/tty*'
  • Start a shell. Either trough minicom or screen.
  • m ( for mode)
  • 3 (for selecting the UART but you can select another mode if you need another protocol)
  • select your baud rate ( most common baud rate are 9600 or 115200)
  • default work in most of the case to get your shell on any devices 8
  • select stop bits is 1 most of the case
  • enjoy your shell.

Real life example

As it happened at the LHS, the bus pirate interacting with a Hitachi HM55B compass module:

Projects/HM55B

Retrieved from ‘https://wiki.london.hackspace.org.uk/w/index.php?title=Equipment/Bus_Pirate&oldid=55241’