Firmware development updates

General
142

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.

1 Like
143
Mode FALA Syntax FALA Commands
1-WIRE :heavy_check_mark: :heavy_check_mark:
UART :heavy_check_mark: :heavy_check_mark:
HDUART :heavy_check_mark: :heavy_check_mark:
I2C :heavy_check_mark: :heavy_check_mark:
SPI :heavy_check_mark: :heavy_check_mark:
2WIRE :heavy_check_mark: :heavy_check_mark:
DIO :heavy_check_mark: :heavy_check_mark:
LED :heavy_check_mark: :heavy_check_mark:

Verification of the Follow Along Logic Analyzer in all modes is complete.

  • During the verification I spotted several small issues in several modes, be sure to get the latest firmware with the fixes
  • FALA bug when the capture buffer is full is fixed
  • All modes and mode commands have been updated and tested to support FALA

Immediate next steps:

  • INFRARED mode + IRTOY compatible binmode
  • Library of 3rd party firmware in a nice maintainable repo with autobuild (DirtyJTAG, etc)
  • Documentation updates (to v1 + scripting/macro/tutorial docs)
  • v1.0 celebration
2 Likes
144

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.

1 Like
145

I will add code to consume all leading spaces.

146

Pushed a fix for the space issue.

2 Likes