Difference between revisions of "RTT"
| Line 2: | Line 2: | ||
= Modes = |
= Modes = |
||
| − | SEGGER RTT ([https://www.segger.com/products/debug-probes/j-link/technology/real-time-transfer/about-real-time-transfer/ Real Time |
+ | SEGGER RTT ([https://www.segger.com/products/debug-probes/j-link/technology/real-time-transfer/about-real-time-transfer/ SEGGER Real Time Transfer]) can run in different modes where some modes are not available on all devices but other modes are which then have an impact on the real time behavior of the device. |
== Background mode == |
== Background mode == |
||
| + | This is the mode which RTT was initially introduced with. In this mode, J-Link can access the memory of the target system while the MCU + application keeps running (background memory access), effectively not impacting the real time behavior of the application. In order to use this mode, the target MCU needs to support background memory accesses. |
||
| − | TBD |
||
| + | |||
| + | The following cores (and therefore all devices based on them) support background memory accesses: |
||
| + | *Cortex-M |
||
| + | *Renesas RX |
||
== Stop mode == |
== Stop mode == |
||
Revision as of 15:42, 25 January 2018
Contents
Modes
SEGGER RTT (SEGGER Real Time Transfer) can run in different modes where some modes are not available on all devices but other modes are which then have an impact on the real time behavior of the device.
Background mode
This is the mode which RTT was initially introduced with. In this mode, J-Link can access the memory of the target system while the MCU + application keeps running (background memory access), effectively not impacting the real time behavior of the application. In order to use this mode, the target MCU needs to support background memory accesses.
The following cores (and therefore all devices based on them) support background memory accesses:
- Cortex-M
- Renesas RX
Stop mode
TBD
