Debugging CANbus For IoT Devices

Figure 1: Temperature data from
thermocouples is shown both
encoded and decoded on the
oscilloscope's display

A myriad of serial-data standards come into play when we're discussing Internet of Things (IoT) devices. We've talked about I2C, SPI, and UART in a previous post. Yet another serial-bus standard that comes under the IoT umbrella is the Controller Area Network (or CANbus) standard. CANbus enables microcontrollers and peripheral devices to communicate with each other in applications without an intervening host computer. In the past, it's been typically used in automotive applications, but CANbus has found its way into a wider scope of applications of late.

Debugging Low-Speed Serial Data on IoT Devices

Figure 1: Serial-data links handle traffic between ICs
and peripheral devices in the IoT world

Our last post discussed the difficulties in acquiring the many sensor signals that may be input to a deeply embedded system such as an IoT device as well as a hardware solution to the problem. Another aspect of IoT debugging and validation is the low-speed serial data standards used to facilitate communication between ICs and between controllers and peripheral devices (Figure 1). To that end, let's take a look at three such low-speed standards: I2C, SPI, and UART.

For UART Debugging, Triggering is Key

Figure 1: A typical screen capture of UART
serial decode/trigger software

In our survey of how modern oscilloscopes and trigger/decode software (Figure 1) can ease the task of debugging embedded systems, we've covered the I²C and SPI protocols. Now we'll turn to the UART format, where triggering capabilities are of particular importance.

Debugging I2C Buses in Embedded Systems

Figure 1: Debugging of I²C on a Teledyne LeCroy
WaveSurfer 3000 oscilloscope

Embedded systems became ubiquitous decades ago and are now found in everything from mobile devices to vehicles to the traffic lights that control their movements. These days, they're typically based on microcontrollers and perform some specific task(s) within a larger system, such as controlling your car's ABS system. They may or may not have any sort of user interface, and can range widely in terms of complexity and functionality.