diff options
| author | hathach <[email protected]> | 2020-04-22 17:13:40 +0700 |
|---|---|---|
| committer | hathach <[email protected]> | 2020-04-22 17:13:52 +0700 |
| commit | 7784b9c48f9e77d740ccc7e4929c5e944cdb1afd (patch) | |
| tree | f611ce0a18301169bae433886de1febcbcb754e4 /examples | |
| parent | afc4042375f7fa283cf912f019e832aaf659e314 (diff) | |
more rtt software
Diffstat (limited to 'examples')
| -rw-r--r-- | examples/readme.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/examples/readme.md b/examples/readme.md index 45746cc75..092787221 100644 --- a/examples/readme.md +++ b/examples/readme.md @@ -44,12 +44,14 @@ $ make LOG=2 BOARD=feather_nrf52840_express all ### Logger -By default log message is printed via on-board UART which is slow and take lots of CPU time comparing to USB speed. If your board support on-board/external JLink debugger, it would be more efficient to use it with RTT protocol for logging. To do that add option `LOGGER=rtt` to build command e.g +By default log message is printed via on-board UART which is slow and take lots of CPU time comparing to USB speed. If your board support on-board/external JLink debugger, it would be more efficient to use it with [RTT protocol](https://www.segger.com/products/debug-probes/j-link/technology/about-real-time-transfer/) for logging. To do that add option `LOGGER=rtt` to build command e.g ``` $ make LOG=2 LOGGER=rtt BOARD=feather_nrf52840_express all ``` +The log can be retrieved by JLink RTT Viewer/Client/Logger software which is bundled with their JLink driver. + ## Flash `flash` target will use the default on-board debugger (jlink/cmsisdap/stlink/dfu) to flash the binary, please install those support software in advance. Some board use bootloader/DFU via serial which is required to pass to make command |