Difference between revisions of "Renesas RZ/V2L"
(Created page with "__TOC__ The Renesas RZ/V2L is equipped with a Cortex-A55 (dual or single) CPU + a Cortex-M33 CPU. ==Specifics== ==Connect== By default, the Cortex-M33 core is not enabled. In...") |
|||
(3 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
+ | [[Category:Device families]] |
||
__TOC__ |
__TOC__ |
||
The Renesas RZ/V2L is equipped with a Cortex-A55 (dual or single) CPU + a Cortex-M33 CPU. |
The Renesas RZ/V2L is equipped with a Cortex-A55 (dual or single) CPU + a Cortex-M33 CPU. |
||
==Specifics== |
==Specifics== |
||
− | ==Connect== |
+ | ===Connect=== |
− | By default, the Cortex-M33 core is not enabled. In order to establish a connection, the J-Link performs a device specific connect sequence. After executing the sequence, the Cortex-M33 is executing a test loop in the SRAM. |
+ | *By default, the Cortex-M33 core is not enabled. In order to establish a connection, the J-Link performs a device specific connect sequence. After executing the sequence, the Cortex-M33 is executing a test loop in the SRAM. This way, the Cortex-M33 can be debugged out-of-the-box without the need of having a application running on the main core which enables the Cortex-M33. |
− | ==Reset== |
+ | ===Reset=== |
− | A device specific reset is performed which resets the M33 + performs the Cortex-M33 enable sequence. The Cortex-A55 is not affected by the reset. |
+ | *A device specific reset is performed which resets the M33 + performs the Cortex-M33 enable sequence. The Cortex-A55 is not affected by the reset. |
+ | |||
==Limitations== |
==Limitations== |
||
The J-Link software supports the Cortex-M33 core, only. |
The J-Link software supports the Cortex-M33 core, only. |
Latest revision as of 13:30, 15 May 2024
The Renesas RZ/V2L is equipped with a Cortex-A55 (dual or single) CPU + a Cortex-M33 CPU.
Specifics
Connect
- By default, the Cortex-M33 core is not enabled. In order to establish a connection, the J-Link performs a device specific connect sequence. After executing the sequence, the Cortex-M33 is executing a test loop in the SRAM. This way, the Cortex-M33 can be debugged out-of-the-box without the need of having a application running on the main core which enables the Cortex-M33.
Reset
- A device specific reset is performed which resets the M33 + performs the Cortex-M33 enable sequence. The Cortex-A55 is not affected by the reset.
Limitations
The J-Link software supports the Cortex-M33 core, only.
Evaluation Boards
TBD
Example Application
TBD