Other Parts Discussed in Thread: SYSCONFIG
Team,
My customer who employs the CC2642R for BLE products is suffering from strange behavior of the AES driver in the SDK(3.40, 4.10,4.20).
The issue is appeared in AESCCMCC26XX.c ::AESCCM_startOperation as below:
--- AESCCMCC26XX.c ::AESCCM_startOperation ---
if (operation->aadLength) {
/* If aadLength were 0, AESWaitForIRQFlags() would never return as the AES_DMA_IN_DONE flag
* would never trigger.
*/
AESStartDMAOperation(operation->aad, operation->aadLength, NULL, 0); ------ (1)
AESWaitForIRQFlags(AES_DMA_IN_DONE | AES_DMA_BUS_ERR); ------ (2)
}
------
The program has got stuck in process “AESWaitForIRQFlags” since another AESxxx_hwiFxn has clear the crypto interrupt sources using AESIntClear at between (1) and (2). This issue is not appeared in case that those two functions are executed in the critical section (Disable Interrupt).
Customer thinks the above phenomenon is not as intended, also the execution of AESxxx_hwiFxn() immediately after (1) is unusual.
Could I have your comment and any workaround for this?
Regards,
Nonaka
