The example demonstrates the MCU firewall isolation in the use case when the MCU domain is running a safety application. The MCU-R5 application configures a firewall to the MAIN domain I2C by allowing access only to the MCU-R5 core and locks this firewall configuration ownership to the MCU core. After configuring the firewall, it reads data from the main domain I2C to check the access from MCU-R5 core. Then it will a send a ipc notify message to the Wkup-R5 core to trigger a firewall exception. The Wkup-R5 application waits for ipc notify message from the MCU core. Upon receiving the message, it triggers a firewall exception by accessing the I2C0 register config and it will go to data abort. The MCU-R5 receives a interrupt for firewall exception. If the interrupt is not received the test fails.
Parameter | Value |
---|---|
CPU + OS | mcu-r5fss0-0 nortos |
r5fss0-0 freertos | |
Toolchain | ti-arm-clang |
Board | am62ax-sk |
Example folder | examples/drivers/safety/fwl_isolation |
Shown below is a sample output when the application is run,