Introduction
This example demonstrates the injection of a high priority CPU error on CPU3. There is IPC communication between CPU1 and CPU3, when CPU3 receives IPC notification then it injects high priority CPU error which causes NMI occurance and default NMI handler registered for CPU3 is invoked in which the error logged into CPU3 ESM is queried.
Watch Variables
- The variable Globalerroreventnumber in CPU3 holds the error logged in CPU3 ESM.
External Connections
Steps to Run the Example
- When using CCS projects to build, import the CCS project for the required combination and build it using the CCS project menu (see CCS Build Project).
- Launch a CCS debug session, connect to CPU1 and load only the c29x1.out.
- After the program is loaded, run CPU1.
- Once c29x1 configures and releases CPU3 out of reset, the program stops.
- Connect to CPU3 target now. c29x3.out would have started execution as soon as it is released from reset.
- In case of RAM configuration, restart the CPU3 target and load the symbols.
- Note: For FLASH configuration, this example is run in FLASH BANKMODE2, where CPU3 has access to FLASH (FRI-2). Refer to the Flash Plugin documentation to know about changing FLASH BANKMODEs and more.
- View the watch variable in CPU1 to know the result of IPC message passing between CPU1 and CPU3.