This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM6442: After adding the Bootloader_socSecHandover() function in SBL, the kernel can not jump over properly

Part Number: AM6442

Hi Team,

When all core cores are loaded and all application-specific firewall calls are set, the security switch is ready, as indicated by the CMD file as shown below: 

AM6442B SEFHAALV is being used.

The project is modified based on C:\ti\MCU_plus_SDK_AM64x_09_00_00_31\examples\drivers\boot\SBL_osPI_multi_partition. After all cores are loaded, add the Bootloader_socSecHandover() function before starting r500, and find the jump failed. While if do not add this function, it  jump and run properly. 

Instead, in the C:\ti\MCU_plus_SDK_am64x_08_04_00_17\examples\drivers\boot\SBL_osPI_multi_partition project, increase the Bootloader_socSecHandover() function in the same manner without a jump failure issue.

The customer would like to know if there a problem with this function? Or is the SDK lib being used wrong? Could you help check this case? Thanks.

Best Regards,

Cherry

  • Hi Cherry,

    After all cores are loaded, add the Bootloader_socSecHandover() function before starting r500, and find the jump failed. While if do not add this function, it  jump and run properly.

    May I know the exact point at which this function call is added. Also, it would be helpful if the failure logs could be shared.

    increase the Bootloader_socSecHandover() function in the same manner without a jump failure issue.

    I am not sure if I understand this statement. What is meant by "increase the Bootloader_socSecHandover() function in the same manner"?

    Regards,

    Prashant