The IAR Embedded Workbench runs two instances of the IDE, one for each core, in a master-slave-
system to share the access to the board keeping both instances synchronous.
The usage and setup of the multicore debugging will be exemplary described for the Simple IO example
running on the application core under ThreadX using the CM3 for handling the PROFINET device stack
as the communication core.
Note: It is recommended to maintain a consistent boot order of the communication and the
application core. Therefore it is advised to always start the R-IN engine / Cortex-M3
(communication core) first and boot the Cortex-A7 (application core) after the
communication core has finished its initialization.
To run the core to core variant of the Simple IO example please perform the following steps:
1. Power up the board.
2. Open the corresponding AC IAR project workspace, e.g.:
projects\goal_pnio_rpc\01_simple_io\iar\renesas\rzn1s_a7_threadx\rzn1s_a7_threadx.eww
3. Open the project options and navigate to the subcategory “Multicore” in the category
“Debugger”.
4. Enable Multicore master mode and select the slave workspace to use. Please note, that the
“slave project” and the “slave configuration” is already preconfigured for the GOAL slave
projects.
The core to core variant requires the 00_goal_rpc_demo project running on the CM3 which is
the same project as for the core to core variant under Linux on the RZ/N1-D but for the RZ/N1-S
demo board. This slave application can be used also for the other PROFINET application core
demo applications.
The slave workspace rzn1s_demo_board.eww is located in the following project directory:
projects\goal_pnio_rpc\00_goal_rpc_demo\iar\renesas\rzn1s_demo_board\
Figure 3-6: Multicore Debug Option
When using the RZ/N1S expansion board, please ensure to select the correct CC project located
at the projects rzn1s_demo_board_eb directory. Additionally, adjust the entry “Slave project”
To Next Page
Loading...
Need help?
General
