The development shield allows easy access to the RuuviTag's test points.
This enables easy debugging with a logic analyzer while developing drivers for sensors onboard or attaching external sensors to RuuviTag.
We recommend attaching RuuviTag to the developer shield with a single zip tie. Use the holes marked in red.
It's highly recommended to keep the development board unpowered while adjusting the connections to avoid any short circuits.
If you're interested only in making a connection to RuuviTag's SWD (Serial Wire Debug) port for debugging purposes, this can also be done without a DevShield. See RuuviTag's pinout for more info.
You can use Segger's J-Link RTT viewer and read the log messages in code through USB, or you can attach a USB-serial adapter to pins on the board and redirect the log messages to the USB port. Using SEGGER JLINK is detailed here. To get started, just set up the pins and RTT/UART as a log backend in project/sdk_application_config.h or project/board/config/sdk_board_config.h.
One interesting possibility is to activate GPIO pins during tasks in the program and then check those pins with a logic analyzer. This helps you to visualize where the program is spending most of its time and allows you to optimize parts of the code that matter the most.
When your code is ready, don't forget to check the power consumption with Nordic Power Profiler Kit. Example on using power profiler can be found here. Once you're happy with the application, you can release the program binaries to wild.
Ruuvi Innovations Ltd (Oy) / FinlandWeb Design Niku Creative