Renesas RZ/T2N

The Renesas RZ/T2N is an high-performance multi-function MPU featuring two Cortex-R52 and -A55 cores.

Supported devices

Refer to the supported device list for a full list of all supported RZ/T2N family devices, their corresponding names and connection diagrams.

Target interfaces

Interface	J-Link support	Flasher support
JTAG
SWD

Flash Banks

Flash bank	Base address	J-Link support	Flasher support	Loader
				Name	Bank size
External QSPI (XSPI0)	0x40000000			Default	Up to 256 MB
External QSPI (XSPI1)	0x50000000			Default	Up to 256 MB

The pin configuration is the following:

Flash loader	CS	CLK	IO0	IO1	IO2	IO3	IO4	IO5	IO6	IO7
XSPI0	P17_4	P17_2	P17_7	P18_0	P18_1	P18_2	P18_3	P18_4	P18_5	P18_6
XSPI1	P15_7	P15_6	P16_2	P16_3	-	-	-	-	-	-

Multi-Core Support

Before proceeding with this article, please check out the generic article regarding Multi-Core debugging here.
The RZ/T2N family comes with a a variety of multi-core options (two Cortex-R52 cores and up to two Cortex-A55 cores)
In below, the debug related multi-core behavior of the J-Link is described for each core:

Cortex-R52_0 (main core)

Init/Setup

• Enables debugging

Reset

• Device specific reset is performed:

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/T2N Authentication process if necessary
4. Power core if necessary
5. Enable debug mode if necessary
6. Clear the reset catch bit (EDECR.RCE == 0)

Attach

• Attach is supported

Cortex-R52_1

Init/Setup

• If the core is not enabled yet, it will be enabled / released from reset
• If the core is already enabled, a simple attach will be performed

Reset

No reset is performed.

Attach

• Attach is supported / desired

Cortex-A55_0

Init/Setup

• If the core is not enabled yet, it will be enabled / released from reset
• If the core is already enabled, a simple attach will be performed

Reset

No reset is performed.

Attach

• Attach is supported / desired

Cortex-A55_1

Init/Setup

• If the core is not enabled yet, it will be enabled / released from reset
• If the core is already enabled, a simple attach will be performed

Reset

No reset is performed.

Attach

• Attach is supported / desired

Reset

A device specific reset is performed for the main core (R52_0) only. The reset contains the following steps:

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/T2N Authentication process if necessary
4. Power core if necessary
5. Enable debug mode if necessary
6. Clear the reset catch bit (EDECR.RCE == 0)

Debug Authentication

The RZ/T2N 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:
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.

RTT

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

• Supported since V8.46 of the J-Link software version, when selecting a RZ/T2N device.
• 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.

• Supported since V8.46 of the J-Link software version, when selecting a RZ/T2N device.
• 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

Supported since V8.46 of the J-Link software version, when selecting a RZ/T2N device.
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