Hello E2E Support Team!
In our application, the TDA3 processor boots from a NOR FLASH chip.
As the QSPI devices are not capable of booting in the XIP mode, the boot scheme includes copying the FLASH memory contents into the system RAM - both for the Secondary Bootloader and for the main application stages.
Therefore, during the runtime the executable code resides in the RAM, which presents a risk of program memory corruption.
We are required to ensure that the program memory is non-writable after the boot-up.
I have analysed the RM chapter devoted to the MMU configuration, however I cannot find any specific translation entry property that regulates the R/W access.
Is there a way to set up the MMU to disallow a memory region from being written to?
Best regards,
Michał Kobuszewski
Software Engineer
APTIV