Hi Ti Folks,
Taking case of AES ciphering + AES_CMAC auth and going by Ti SA UG, can i conclude the following.
1. In one-go [one qmss_queue push with appropriate command labels] packet being sent to encryption engine [AES] and automatically the same is routed to Auth engine [AES_CMAC] to do ?? Is this possible [looks like possible, as i see this in test1_1.c ], i just wanted confirmation by Ti folks ?
2. In one-go [i am looking at one qmss_queue push], it is NOT possible by using air cipher engine because of combined channel creation of cipher+auth not possible due to LLD limitations [based on my earlier post and Ti's reply].
3. I relooked at the Table 2-5 [Ti SA UG] [i pasted the table below] and i see that there are two points
AES CMAC ---> air cipher engine
CMAC ----> Authentication engine
is CMAC different from AES CMAC ??
can i perform AES CMAC using Auth engine ??
Thanks
RC Reddy
