I agree with that. The workflow on my current project is to connect up the BP for UART, start bridge (or my new “glitch” command), and then power up the device and let the command execute.
In my personal branch I disabled the sanity checks to be able to do this.
| Mode | FALA Syntax | FALA Commands |
|---|---|---|
| 1-WIRE |  |
|
| UART | |
|
| HDUART | |
|
| I2C | |
|
| SPI | |
|
| 2WIRE | |
|
| DIO | |
|
| LED | |
|
Verification of the Follow Along Logic Analyzer in all modes is complete.
Immediate next steps:
I just reported a new minor bug in github, but one that I think is important to the 1.0 release. Beginners will copy/paste examples. In the process, they may copy an extra space. This causes a syntax error in the bus commands.
Example:
[]
[]
The second line causes a syntax error. This can cause confusion as someone may think they pasted the correct command from the example.
I will add code to consume all leading spaces.
Pushed a fix for the space issue.
The latest Bus Pirate firmware has a number of fixes, and a new mode.
Infrared mode sends and receives NEC and RC5 remote control protocols. You’ll need to bring an IR LED and demodulator, or use something like the Infrared Toy plank. Soon I will add a binary mode compatible with LIRC (is that still a thing?), AnalysIR, etc.
An RTT debug channel is now available over the SWIO port.
I failed at my first attempt to port DirtyJtag to the Bus Pirate with a reusable “SDK”. I learned a lot about how it needs to be structured though, another attempt is on the way.
Fixes:
I’m anxiously awaiting the AnalysIR compatibility.
There is a new 3WIRE mode, which is like SPI but you can manipulate the clock and MOSI pins independently using the /-_ syntax. This is useful for oddball devices that use reset, start bits, and opcodes that are not 8 bit bytes. For example, the 93LC66B uses a start bit and 2 bit opcodes which are not compatible with the typical 8bit I2C bus.
The latest firmware has some massive updates to infrared mode to get the IR Toy plank going:
irrx - Receive, retransmit, and save IR signals in AIR formatted packetsirtx - Transmit AIR formatted packets from the command line or a filetvbgone - Plays 100+ TV “power off” signals to disable any obnoxious TVs in your vicinityThe latest firmware now supports AnalysIR, popular infrared signal analysis software for Windows. It is a paid program, with Educational, Maker and Pro versions available. Note that the free version does not support external hardware.
You will need an infrared demodulator and infrared diode, or use the IR Toy plank.
Use the binmode command and select the AIR capture mode.
Start AnalysIR and select A.IR Shield Nano as the source.
Now you can:
If send doesn’t work, be sure that A.IR Shield Nano is selected as the source.
This is not free software. Our relationship with AnalysIR consists of the following:
I’m about to post about the I2C sniffer, and see I missed a huge addition: bluetag JTAG and SWD pin finder is now integrated in the main Bus pirate firmware.
It can scan for both JTAG and SWD pins:
bluetag command to access the blueTag interface.bluetag is also available from the Bus Pirate command line.
Command usage.
The latest firmware auto build supports I2C sniffing up to 500kHz via the pico-i2c-sniffer project.
The output is similar to the I2C command syntax. Sniffed packets can be pasted into the command line and replayed.
The q quiet flag hides the ACK (+) indicator to make it easier to replay commands without editing the sniffer output. NAKs (-) will still be displayed.
A minor convenience change for the mode command.
m 5
You can already bypass the mode menu by specifying the mode number.
m i2c
Now you can also specify the mode by name (case insensitive). This should help scripts stay stable long term, even if the order of modes changes.
I think the mode: indication should probably be moved to the start of the output. Then we can consolidate the “XXX speed:” translation to a single “Speed:”. Will push asap.
