The Renesas RA8M1 are Cortex-M85 based microcontrollers.
- 1 Flash Banks
- 2 Watchdog Handling
- 3 Device Specific Handling
- 4 Limitations
- 5 Evaluation Boards
- 6 Example Application
- 7 Tracing on RA8M1 series
|Code flash option-setting memory (secure)
|Code flash option-setting memory (non-secure)
|Data flash option-setting memory
|Code flash (secure)
|Up to 2048 KB
|Code flash (non-secure)
|Up to 2048 KB
|Data flash (secure)
|Up to 12 KB
|Data flash (non-secure)
|Up to 12 KB
QSPI flash programming requires special handling compared to internal flash. For more information about this, please see the QSPI Flash Programming Support article.
Flash programming in OSPI mode is supported for Infineon S28HL512T and S28HS512T only. Other flashes are handled in single/quad mode.
|Supported pin configuration
|External OSPI flash CS0
|External OSPI flash CS1
- The device has two watchdogs: Watchdog Timer (WDT) and Independent Watchdog Timer (IWDT).
- Both watchdogs are fed during flash programming.
Device Specific Handling
During connect the current security state of the device is determined. Depending on the state J-Link will use different RAM areas for operations that require RAM (flash programming, clock speed measurements):
- OEM_PL2: 0x22000000-0x2200FFFF
- OEM_PL1: 0x320D0000-0x320DFFFF
- The devices uses normal Cortex-M reset, no special handling necessary, like described here.
Using OEM_PL1 state with J-Flash
Since OEM_PL1 state requires the use of non-secure RAM (0x320D0000-0x320DFFFF), the user has to ensure that the J-Flash project is set up to use this RAM area instead of the secure RAM. By default J-Flash projects are created with secure RAM area (0x22000000-0x2200FFFF) selected.
Renesas EK-RA8M1 evaluation board: http://wiki.segger.com/Renesas_EK-RA8M1
Renesas EK-RA8M1 evaluation board: http://wiki.segger.com/Renesas_EK-RA8M1#Example_Project
Tracing on RA8M1 series
Tracing on R7FA8M1
In order to use trace on the Renesas R7FA8M1 MCU devices, the following minimum requirements have to be met:
- J-Link software version V7.92I or later
- Ozone V3.30c or later (if streaming trace and / or the sample project from below shall be used)
- SEGGER Embedded Studio V7.32
- J-Trace PRO for Cortex-M HW version V3.0 or later for streaming trace
- J-Link Plus V12 or later for TMC/ETB trace
To rebuild the project our IDE Embedded Studio can be used. The recommended version to rebuild the projects is V7.32. 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-RA8M1.
Example project: Renesas_RA8_TracePins.zip
Note: The example is shipped with a compiled .JLinkScriptfile, should you need the original source, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.
To create your own .JLinkScriptfile you can use the following guide as reference: How_to_configure_JLinkScript_files_to_enable_tracing
Trace buffer (TMC/ETB)
Example Project: Renesas_RA8_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.