SEGGER官方整理的一些JLINK配合MDK的问题解决办法

eric2013

https://www.segger.com/products/ ... eil-mdk/#tab-4285-3

MDK V5.18 or earlier

• Problem: When using ETM trace functionality with J-Trace for Cortex-M, status bar in uVision showed "Trace: No synchronization".
  

• Problem: When using ETM trace functionality with J-Trace PRO for Cortex-M, sometimes the error "Failed to read trace data" appeared.
  

• Problem: When using ETM trace functionality with J-Trace PRO for Cortex-M, uVision sometimes crashed when large amounts of trace data were read.
  

Solution: Copy this version (V2.99.20) of the JL2CM3.dll to $MDK_INST_DIR$\ARM\Segger.

MDK V4.60 or earlier

• Problem: Some SW-DP Ids of Cortex-M0+ devices were not recognized correctly, resulting in an error message when trying to start a debug session. For example the Freescale Kinetis L-series devices showed this problem.
  

Solution: Copy this version (V2.74) of the JL2CM3.dll to $MDK_INST_DIR$\ARM\Segger.

MDK V4.54 or earlier

• Problem: For some Cortex-M devices debug register base address detection did not work properly which messed up flash download using the J-Link flashloader.
  

• Problem: When selecting a device in the J-Link device selection dialog, the selection was not saved, so the dialog popped up again at the start of the next debug session.
  

• Problem: When using ETM trace, under special circumstances, uVision could crash.
  

Solution: Copy this version (V2.71) of the JL2CM3.dll to $MDK_INST_DIR$\ARM\Segger.

MDK V4.53 or earlier

• Problem: In case multiple J-Links are connected to the PC, uVision was not able to recognize them correctly.
  

Solution: Copy this version (V2.68) of the JL2CM3.dll to $MDK_INST_DIR$\ARM\Segger.

eric2013

J-Link built-in flashloader

yumeng