Part Number: AM2634
Hi Team,
Is it possible to use the Bootloader API in non-SBL code?
Are there any considerations that have to be made when doing this?
Thanks!
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.
Part Number: AM2634
Hi Team,
Is it possible to use the Bootloader API in non-SBL code?
Are there any considerations that have to be made when doing this?
Thanks!
Is it possible to use the Bootloader API in non-SBL code?
Do you mean can you make calls to Bootloader functions (e.g. Bootloader_uniflashFlashFileSector()) from your application? If so, then yes. Please see my answer here: AM2634-Q1: Accessing the QSPI Flash - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums
Are there any considerations that have to be made when doing this?
The only thing I would highlight is that flashing operations can take in the order of seconds so you need to find a way of allowing the function to complete over this lengthy period. I am using FreeRTOS with Application Idle Hook enabled. I run these lengthy operations from this hook.
Hi Nishka,
My first question here would be what is the purpose behind calling the bootloader API in application code.
To mention broadly Bootloader apis do following:
1. Copy code to and from the flash -> Flash read write APIs can be used as alternative in application
2. Authenticate the application -> There are HSM APIs which can be used alternatively
3. Boot other CPU and self CPU -> I am not sure if this is what customer wants to do? If yes - then does customer want to build tertiary bootloader kind of application?
I would like to better understand why bootloader api calls are needed at application level?