Oberon Ocrypto: Lockup with S/W Only stack in FSP v5.9.0

[GodavarthyAravinda]

Issue

Ocrypto H/W acceleration source files are being brought into the S/W Only stack. This can cause some AES API calls to compile and link against the accelerated implementations rather than those of the Ocrypto library.

When this happens, the project will build successfully but at runtime, will wait indefinitely for a crypto engine register. But in the case of the Ocrypto S/W Only stack, calls to initialize HW SCE RM_OCRYPTO_PORT_Init() -> HW_SCE_McuSpecificInit() are not necessary and this register will never be set.

Note: Oberon Ocrypto is only supported on RA2E1 devices.

Workaround

To resolve this lockup and use the library functions as intended, FSP users will need to exclude the following files from the build:

ra/fsp/src/rm_ocrypto_port/rm_ocrypto_port_cbc_mode.c
ra/fsp/src/rm_ocrypto_port/rm_ocrypto_port_ctr_mode.c
ra/fsp/src/rm_ocrypto_port/rm_ocrypto_port_aes_encrypt.c
ra/fsp/src/rm_ocrypto_port/rm_ocrypto_port_aes_decrypt.c
ra/fsp/src/rm_ocrypto_port/rm_ocrypto_port_aes_helpers.c

To exclude from the build, for each file listed above,

1. Navigate to the Project Explorer
2. Right click the filename
3. Select Resource Configurations -> Exclude from Build