This article covers the Renesas RA6M3 Family
- 1 Flash
- 2 Tracing on RA6M3 series
Internal option-setting memory
Option-settings memory is located at 0x0100A150 has a size of 32 Bytes.
The full 32 bytes must be provided in the data file for the option-setting memory when using Flasher's stand-alone mode. Gaps are not allowed.
Internal program flash
The size of the program flash is dependent on the device used.
|Device||Size (KiB)||Memory region|
|R7FA6M3AF||1024||0x00000000 - 0x000FFFFF|
|R7FA6M3AH||2048||0x00000000 - 0x001FFFFF|
Currently only single bank flash operations are supported. Dual bank mode is not supported.
Internal data flash
Internal data flash is located at 0x08000000 has a size of 8 KB.
External QSPI flash
External QSPI flash is located at 0x60000000.
Supported pin configurations
- CLK@P305_nCS@P306_D0@P307_D1@P308_D2@P309_D3@P310 (default)
Other pin configurations are avaialable on request. In such cases, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.
Tracing on RA6M3 series
This section describes how to get started with trace on the Renesas RA6M3 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).
- 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.
- All examples are shipped with a compiled .JLinkScriptfile (.pex), should you need the original source, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.
Tracing on Renesas R7FA6M3AH3C
In order to use trace on the Renesas R7FA6M3AH3C MCU devices, the following minimum requirements have to be met:
- J-Link software version V6.62 or later
- Ozone V3.10c 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 V6.30. But the examples are all prebuild and work out-of-the box with Ozone, so rebuilding is not necessary.
The project has been tested with the minimum requirements mentioned above and a Renesas EK-RA6M3 evaluation board.
Example project: Renesas_R7FA6M3AH_TracePins.zip
Trace buffer (ETB)
Example Project: Renesas_R7FA6M3AH_TraceBuffer.zip
Reference trace signal quality
The following pictures show oscilloscope measurements of trace signals output by the "Tested Hardware" using the example project. All measurements have been performed using a Agilent InfiniiVision DSO7034B 350 MHz 2GSa/s oscilloscope and 1156A 1.5 GHz Active Probes. If your trace signals look similar on your trace hardware, chances are good that tracing will work out-of-the-box using the example project. More information about correct trace timing can be found at the following website.
Trace clock signal quality
The trace clock signal quality shows multiple trace clock cycles on the tested hardware as reference.
The rise time of a signal shows the time needed for a signal to rise from logical 0 to logical 1. For this the values at 10% and 90% of the expected voltage level get used as markers. The following picture shows such a measurement for the trace clock signal.
The setup time shows the relative setup time between a trace data signal and trace clock. The measurement markers are set at 50% of the expected voltage level respectively. The following picture shows such a measurement for the trace data signal 0 relative to the trace clock signal.