diff options
| author | hathach <[email protected]> | 2021-10-13 17:31:57 +0700 |
|---|---|---|
| committer | hathach <[email protected]> | 2021-10-13 17:32:34 +0700 |
| commit | 5cfe2930012d1dbec85e0923e0eda2d9aec867e6 (patch) | |
| tree | 0cb085ef234c696baab7ebd291e3ae4d7e386837 /docs/reference | |
| parent | 9da234cd7c73786624970206d7b7b7361275a6b7 (diff) | |
update changelog and increase version for 0.12.0
Diffstat (limited to 'docs/reference')
| -rw-r--r-- | docs/reference/getting_started.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/reference/getting_started.rst b/docs/reference/getting_started.rst index 044792993..875372c81 100644 --- a/docs/reference/getting_started.rst +++ b/docs/reference/getting_started.rst @@ -122,7 +122,7 @@ 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 debugger, it would be more efficient to use it for logging. There are 2 protocols: -* `LOGGER=rtt`: use [Segger RTT protocol](https://www.segger.com/products/debug-probes/j-link/technology/about-real-time-transfer/) +* `LOGGER=rtt`: use `Segger RTT protocol <https://www.segger.com/products/debug-probes/j-link/technology/about-real-time-transfer/>`_ * Cons: requires jlink as the debugger. * Pros: work with most if not all MCUs |