Differences

This shows you the differences between two versions of the page.

--- en:uhsdr_dev:segger_j_link [27.02.2018 06:00] – df9ts_user
+++ en:uhsdr_dev:segger_j_link [27.02.2018 07:38] – df9ts_user
@@ Line 1: / Line 1: @@
-Segger Tools require a Segger probe to be used. For non-commercial use Segger offers the low priced "J-Link Edu" probe
+==== Segger J-Link Introduction ====
+Segger provides a probe - J-Link - that can be used for programming and debugging. For non-commercial use Segger offers the low priced [[https://www.segger.com/products/debug-probes/j-link/models/j-link-edu/|J-Link Edu]] probe.
 Segger supports the Cortex M7 SWV interface used on OVI40 UI and offers plug-ins for MCU eclipse.
-For Debug output Segger offers two options in MCU eclipse:
+For Debug output Segger offers an two options in MCU eclipse:
   * TRACESWO output as defined by CORTEX M7. This requires a dedicated pin, currently used for M3 pushbutton switch
-  * Segger Real Time Tracing (RTT) with outputs debug messages in high speed via SWV debug lines (CLK and SWData). No need for an additional line to printout debug messages
+  * [[https://www.segger.com/products/debug-probes/j-link/technology/real-time-transfer/about-real-time-transfer/|Segger Real Time Tracing (RTT)]] with outputs debug messages in high speed via SWV debug lines (CLK and SWData). No need for an additional line to printout debug messages (as is the case with TRACESWO).
+The J-Link makes use of the Cortex-M feature, which allows accessing the memory via the debug interface while the target is running.
+How this works in general is described [[https://www.segger.com/jlink-rtt.html|here]].
 The speed advantage of RTT - according to Segger data - is impressive: