After installing the new Netduino Go firmware and Shield Base firmware released earlier today, you can use the serial analyzer to view the protocol between the Netduino Go mainboard and the Shield Base module. Using a breakout board (for example, the GoBus Breakout Module), simply connect your logic analyzer to GoBus pins 4, 5, and GND and you'll be able to capture and view the serial GoBus traffic between the module and the mainboard. (On the GoBus Breakout Module pins 4 and 5 are labeled with the STM8 functions SWIM and NRST.)
Download: Beta 1
Includes compiled files for Windows and Mac OS X, as well as the source code for both analyzers.
Here's what the analyzer looks like:
When you zoom in you can see a few more details about each byte:
Here's what the SPI analyzer looks like. At the moment I only have sample ("fake") data to display but it should work correctly with actual GoBus SPI traffic when that is available
Installation:
Windows:
Copy the following files:
- GoBusAsyncSerial.dll
- GoBusSPI.dll
If the GoBus analyzers don't show up within the Logic software, make sure you have the Microsoft Visual C++ 2010 Redistributable Package installed. This can be downloaded from: http://www.microsoft...ls.aspx?id=5555
Mac OS X
Copy the following files:
- libGoBusAsyncSerial.dylib
- libGoBusSPI.dylib
Right click Logic.app and select "Show Package Contents" to access the "Contents" folder.
Limitations:
- The analyzers currently only support CRC8 frames. This is due, in part, to CRC8/16 being a transport setting that is not indicated within each packet. This will be fixed in the future, either from a change in the protocol or through a setting in the analyzer.
- The SPI analyzer currently uses the Enable line to determine frame length (and therefore where the CRC byte is located) as well as where each new frame begins. This could cause issues if the Enable line is not cycled between frames.
- For both analyzers, the CRC value is only displayed and not actually verified by the analyzer. The CRC value in simulated data is not accurate and will always be set to 0xFF.
- I haven't worked on the export function yet, these features are purely for displaying GoBus traffic at the moment. That will be fixed later
Enjoy, and let me know what you think!
Matt