EK-RA8P1 board reference also covers its parallel graphics, MIPI graphics, and OV5640 camera expansion boards.
Select RA8P1 or a matching EK-RA8P1 platform to make that board skill available. Other RA platform selections do not enable it. See board-skill setup.
Check the project setup picker for current availability. Flashing and debugging depend on the tools and connections supported by your board.
EK-RA8P1 board family
Embedder includes a board-aware skill for the EK-RA8P1 evaluation kit and its display and camera expansion boards. The skill covers connector pinouts, the SW4 configuration switches and their resource conflicts, jumpers, boot modes, debug and VCOM routing, and the fitted Ethernet, USB, OSPI, SDRAM, and audio peripherals. Select a matching platform as described above to make the skill available for these boards:
The RA8P1 carrier is a dual-core device: CPU0 is a Cortex-M85 at up to 1 GHz and CPU1 is a Cortex-M33 at up to 250 MHz. The device includes 1 MB MRAM, 2 MB ECC SRAM, and an Ethos-U55 NPU.
FSP and e2 studio workflow
Embedder runs the installed Renesas tooling headlessly instead of opening the e2 studio GUI:- Derives the board, device, core, FSP version, RTOS, toolchain, and debugger from an existing project’s
configuration.xml,.cproject, and.launchfiles. - Creates new projects and multicore solutions through the e2 studio headless scripting interface, discovering the boards, templates, toolchains, and debuggers supported by the installed FSP before choosing them.
- Treats
ra/,ra_cfg/, andra_gen/as generated content and runs Generate Project Content after anyconfiguration.xmlchange, since a CDT build alone does not update generated FSP sources. - Builds through the e2 studio managed-build or standard CDT headless builder and verifies the final error count and output artifacts.
Dual-core flash and debug
For RA8P1 multicore solutions, Embedder generates, builds, and programs the core projects in dependency order: CPU0 first, then CPU1. A later core consumes the preceding core’s smart-bundle artifact. Embedder derives flash and debug arguments from the project’s.launch and J-Link metadata rather than hardcoded examples, and never reuses CPU0 launch metadata for the CPU1 debug session. Before programming multicore images, Embedder checks that the ELF load ranges do not overlap.