Renesas RA6M2
This article covers the Renesas RA6M2 Family
Flash Banks
Internal Flash
| Flash bank | Base address | J-Link support | Flasher support | Loader | |
|---|---|---|---|---|---|
| Name | Bank size | ||||
| Internal program flash[1] | 0x00000000 |  |
|
Default | Up to 1024 KB |
| Internal option-setting memory[2] | 0x0100A150 | |
|
Default | 32 B |
| Internal data flash | 0x40100000 | |
|
Default | 32 KB |
External QSPI flash
| Flash bank | Base address | J-Link support | Flasher support | Loader | |
|---|---|---|---|---|---|
| Name | Bank size | ||||
| External QSPI flash[1] | 0x60000000 | |
|
CLK@P500_nCS@P501_D0@P502_D1@P503_D2@P504_D3@P505 | Up to 64 MB |
Other pin configurations are available on request. In such cases, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.
- ↑
QSPI flash programming requires special handling compared to internal flash. For more information about this, please see the QSPI Flash Programming Support article.
J-Link supports multiple pin configurations for this Device. The default loader is marked in bold. For details on how to select a specific flash loader, please see here.
Limitations
Security
- The device has a debug locking feature based on the 128 bit IDCODE, programmed into option-setting memory.
- During connection, the user will be asked to specify the IDCODE code to unlock debugging access if it was previously programmed.
- Use the following IDCODE to send the ALeRASE command, which triggers erasure of the user flash (code and data) area and the configuration area: FFFFFFFFFFFFFFFFFF45534152654C41
- Important: Make sure the byte order of the ALeRASE command is correct, as above shown above. A common mistake is using the wrong byte order, which will cause the command to fail.
Tracing on RA6M2 series
This section describes how to get started with trace on the Renesas RA6M2 MCUs. This section assumes that there is already a basic knowledge about trace in general (what is trace, what different implementations of trace are there, etc.). If this is not the case, we recommend to read Trace chapter in the J-Link User Manual (UM08001).
Note:
- The sample projects come with a pre-configured project file for Ozone that runs out-of-the box.
- The following sample project is designed to be used with J-Trace PRO for streaming trace, J-Link Plus for buffer tracing (TMC/ETB trace) and Ozone to demonstrate streaming trace.
- In order to rebuild the sample project, SEGGER Embedded Studio can be used.
Tracing on Renesas R7FA6M2AF
Minimum requirements
In order to use trace on the Renesas R7FA6M2AF MCU devices, the following minimum requirements have to be met:
- J-Link software version V7.88k or later
- Ozone V3.30a or later (if streaming trace and / or the sample project from below shall be used)
- J-Trace PRO for Cortex-M HW version V1.0 or later for streaming trace
- J-Link Plus V10 or later for ETB trace
To rebuild the project our IDE Embedded Studio can be used. The recommended version to rebuild the projects is V7.30. But the examples are all pre-built and work out-of-the box with Ozone, so rebuilding is not necessary.
Streaming trace
Example project: Renesas_R7FA6M2AF_TracePins.zip
There is currently no evaluation board available for streaming trace, so we recommend to use custom hardware instead.
The Trace board design recommendations should be followed.Trace buffer (ETB)
The project has been tested with the minimum requirements mentioned above and a Renesas EK-RA6M2 evaluation board.
Example Project: Renesas_R7FA6M2AF_TraceBuffer.zip
