Difference between revisions of "TI RMxxL"

From SEGGER Wiki
Jump to: navigation, search
(Created page with "The J-Link DLL must be informed about the correct device (e.g. RM57L843ZWT) because for the RM4xL and RM5xL series a special connect sequence must be realized so the ICEPick w...")
 
(Different JTAG-chain)
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
  +
== ICEPick ==
The J-Link DLL must be informed about the correct device (e.g. RM57L843ZWT) because for the RM4xL and RM5xL series a special connect sequence must be realized so the ICEPick will be configured correctly and a stable connection to the target device can be established.
 
  +
The RMxxL series features a so called ICEPick which requires a special connect sequence. This sequence is executed by default by the J-Link DLL if the proper device (e.g. RM57L843ZWT) is selected. How to select the correct device: https://wiki.segger.com/Selecting_the_correct_device
   
  +
'''Note:''' By default, the J-Link DLL assumes one RMxxL device in the JTAG-chain (TDI -> RMxxL -> TDO).
Generally IDE's (e.g. SEGGER Embedded Studio, ...) pass the device name automatically to the J-Link DLL. The J-Link Commander needs the device needs to be selected by the user e.g. by passing the device name via command line option. A command line can look like this:
 
  +
===Different JTAG-chain===
 
  +
If a different JTAG-chain is used, a adapted J-Link Script File is required which contains the updated configuration. Please find below two script files for a setup where two RMxxL devices are chained in a JTAG-chain (TDI -> RMxxL (#0) -> RMxxL (#1) -> TDO).
JLink.exe -device RM57L843ZWT -if JTAG -jtagconf -1,-1 -speed 4000
 
  +
*[[File:TI_RM57L_SelDev0.pex]]
  +
*[[File:TI_RM57L_SelDev1.pex]]
  +
'''Note:''' If your JTAG-chain configuration differs from the default and the above one, please get in contact with SEGGER.
   
 
== RAM initialization on connect ==
 
== RAM initialization on connect ==
Line 12: Line 16:
   
 
*[[File:TI_RM4xL_RM5xL_SkipECCInit.JLinkScript]]
 
*[[File:TI_RM4xL_RM5xL_SkipECCInit.JLinkScript]]
  +
Please note, that the script file has been tested with version V6.12b of the J-Link software and documentation package

Revision as of 11:53, 25 April 2019

ICEPick

The RMxxL series features a so called ICEPick which requires a special connect sequence. This sequence is executed by default by the J-Link DLL if the proper device (e.g. RM57L843ZWT) is selected. How to select the correct device: https://wiki.segger.com/Selecting_the_correct_device

Note: By default, the J-Link DLL assumes one RMxxL device in the JTAG-chain (TDI -> RMxxL -> TDO).

Different JTAG-chain

If a different JTAG-chain is used, a adapted J-Link Script File is required which contains the updated configuration. Please find below two script files for a setup where two RMxxL devices are chained in a JTAG-chain (TDI -> RMxxL (#0) -> RMxxL (#1) -> TDO).

Note: If your JTAG-chain configuration differs from the default and the above one, please get in contact with SEGGER.

RAM initialization on connect

The RM4xL and RM5xL device series comes with an ECC protected RAM. To make sure that no ECC errors are generated when reading from the ECC protected RAM region, the J-Link DLL has to initialize this region before reading it in order to make sure that the ECC is valid. Prior the initialization is issued, a reset of the MCU is performed in order to bring the device into a proper state and to make sure that hardware units like for example DMAs are halted during the RAM init. The actual ECC init is performed by using the Memory Hardware Initialization of the MCU.

Whereas this RAM init is required for most setups, there are some setups where this could cause issues (e.g. when attaching to a running session). In order to prevent the J-Link DLL from executing the RAM initialization, an command string must be passed to the J-Link DLL. This can be done by using a J-Link script file. Further information regarding the J-Link script file can be found in the J-Link User Manual (UM08001).

Please note, that the script file has been tested with version V6.12b of the J-Link software and documentation package