search

CyberCircuits / the-bus-pirate

Automatically exported from code.google.com/p/the-bus-pirate
Other
0 stars 1 forks source link

I2C protocol sniffer #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Add a macro to the I2C library that reads activity from a bus and prints it
to the terminal until stopped with escape.

Since the hardware I2C module doesn't work this will be a bit challenging,
fortunately I2C isn't a high-speed protocol. Best solution is probably to
use the pin change notification interrupts to detect start and stop
sequences, and clock in the bits. This will need a buffer to hold decoded
bytes while the Bus Pirate converts the raw values to ASCII characters for
display.

Original issue reported on code.google.com by ianles...@gmail.com on 31 Mar 2009 at 2:18

GoogleCodeExporter commented 9 years ago

Original comment by ianles...@gmail.com on 28 Apr 2009 at 6:44

GoogleCodeExporter commented 9 years ago 
Added a function to I2C.c that starts to outline a I2C sniffer. The idea is to 
poll
the pin change notification using the new periodic service command (see SPI.c).

The function will:
Check for change notice,
Check for start or stop condition, reset the state machine,
In a state machine, collect data or ACK, display on terminal.

This really needs the terminal TX buffer described in issue 22:
http://code.google.com/p/the-bus-pirate/issues/detail?id=22

Original comment by ianles...@gmail.com on 28 Apr 2009 at 7:10

GoogleCodeExporter commented 9 years ago

Original comment by ianles...@gmail.com on 4 Nov 2009 at 12:41

GoogleCodeExporter commented 9 years ago

Original comment by ianles...@gmail.com on 15 Aug 2010 at 8:10

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
It is really flaky past 100KHz, it is a known issue.

Original comment by ianles...@gmail.com on 26 May 2011 at 5:25