Renesas RZ/T2ME

The RZ/T2ME family are R52 based microcontrollers.

Flash Banks

Flash Bank	Base address	J-Link Support	Loader
			Name	Size
External QSPI (XSPI0)	0x60000000		Default	up to 64 MB
External QSPI (XSPI1)	0x68000000		Default	up to 64 MB
Parallel CFI NOR	0x70000000		Default	32 MB

Watchdog Handling

• The device has a watchdog.
• The watchdog is fed during flash programming.

Multi-Core Support

Before proceeding with this article, please check out the generic article regarding Multi-Core debugging here.

Core	J-Link Support
Main core CPU0
Secondary core CPU1

In below, the debug related multi-core behavior of the J-Link is described for each core:

Main core CPU0

Init/Setup

• Executes debug authentication, see Debug_Authentication
• Enables debugging

Reset

• Device specific reset is performed, see Reset

Attach

• Attach is supported.

Secondary core CPU1

Init/Setup

• If the secondary core is not enabled yet, it will be enabled / release from reset

Reset

No reset is performed. The Target is halted.

Attach

• Attach is supported / desired.

Device Specific Handling

Reset

• The device uses custom reset:

1. Make sure that the device halts immediately after reset (before it can execute any instruction of the user application) by setting EDECR.RCE == 1
2. Reset the core and peripherals by toggling the reset pin
3. Pass through the RZ/T2ME Authentication process if necessary
4. Power core if necessary
5. Enable debug mode if necessary
6. Clear the reset catch bit (EDECR.RCE == 0

RTT

J-Link uses the AXI-AP of the device for RTT accesses.

• RTT control block and buffers must be placed in a memory that is accessible via AXI-AP.
• ATCM and BTCM are not suitable because they are not accessible via AXI-AP.
• AXI-AP bypasses the cache of the CPU, so RTT control block and buffers need to be in a non-cached memory area.
• RTT auto-detection: By default, J-Link scans the first 32 KB of the system RAM @ 0x1000_0000 for a RTT control block.
• Regarding cache etc., the RTT Cortex-R specifics apply.

HSS

• J-Link uses the AXI-AP of the device for HSS accesses.
• Variables to monitor must be placed in a memory that is accessible via AXI-AP.
• ATCM and BTCM are not suitable because they are not accessible via AXI-AP.
• AXI-AP bypasses the cache of the CPU, so variables need to be in a non-cached memory area. (Otherwise only sporadic or no updates will be seen at all)

Zoned memory access

For more information about what zoned memory accesses are: Dedicated Knowledge Base article
The following zones are available for these devices:

Zone	Description
Default	Default memory view (memory is accessed through the core)
AP0	APB-AP. Not usable for the user
AP1	APB-AP view that connects to the debug registers and other CoreSight components. Not usable for the user
AP2	AXI-AP. Allows DMA-like access (bypasses MMU/MPU/caches) to system memory and most peripheral registers

Security

Debug Authentication

The RZ/T2ME supports different authentication levels. Depending on the authentication level, debug access can be granted if the correct key is passed. How this is possible is described below.

Note:
Only available on CPU0.
For security products, the MDD pin must be set to the correct state.

Specifying the authentication code using J-Link Command String

This is the recommended method as the specified authentication key will be used for the whole session. This way, the key must not specified multiple times (e.g. if a reset is performed). The J-Link Command String needs to be passed to the J-Link DLL before establishing the target connection. The J-Link Command String SetCPUConnectIDCode <AuthKey> has to be used (see example below).

Example authentication key:

• AuthenticationKey0: 0x01234567
• AuthenticationKey1: 0x89ABCDEF
• AuthenticationKey2: 0x00224466
• AuthenticationKey3: 0x88AABBCC

 exec SetCPUConnectIDCODE 67452301EFCDAB8966442200CCBBAA88

Specifying the authentication code using the ID Code dialog

If the authentication key has not been specified using the Command String although it is required to enable debug access, the following message box will pop up which allows specifying the authentication key.