AM2634: Can the SBL choose from multiple appimages in flash?

I'm actually trying to do this on a AM2634- I neglected to change the part number when I posted.

Hi Tom,

I have changed the part number so that it does not cause any confusion.

Tom Tatakis said:

Is it possible to store multiple appimage files in flash and have the bootloader decide which one to launch based on a version number or some other key (maybe a special key in an external eeprom)?

Hi Tom, You will need to design this in your secondary bootloader. So you can read more about SBL here: Secondary Bootloader flow in AM26x devices

TI Provides example code for SBL in different boot modes here: https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/latest/exports/docs/api_guide_am263x/EXAMPLES_DRIVERS_SBL.html

I am assuming you will keep your images in flash, then  you can modify the SBL QSPI example: https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/latest/exports/docs/api_guide_am263x/EXAMPLES_DRIVERS_SBL_QSPI.html

We are setting the offset of image in syscfg :

So before calling bootloader APIs: 

Put a logic for the selection of the version number then override the offset.

Hope this helps.

Thanks- looking into this now.  On a related note, in UniFlash when I select the tiimage and appimage to load, it fills in a Load Address for each.  Where does UniFlash get the Load Address for the AppImage file?  Is that just an arbitrary address in flash with the only requirement that it match where the bootloader expects to find the image?

...

I tried building and running the qspi example, but I can not seem to debug it on my AM263x Control Card EVM.  The debugger connects, appears to load everything but then just becomes non-responsive, indicating it is running.  But the Pause and Stop buttons are disabled.

So tried to build my own debugger with a a known syscfg that I know works with the EVM.  I think have that project attached below but not sure??? I don't see an attach button, so I 'Inserted' a file.

I tried duplicating the relevant settings from the qspi example.  This project builds, loads, and I can step through with the debugger.  However, this one crashes on line 364 of hsmclient_loadhsmrt.c; the memcpy() call.

Should I be able to debug a SBL bootloader this way?  If my attachment is not there, is there another way to get you my project?

All of the settings I can see match up with the TI qspi sample.  Are there any obvious things to check for this to run on the EVM.

bootloader-ti.zip

Here's an updated project- I managed to get the memory regions matching what was in the qspi example.  I get the same results however- it crashes on line 364 of hsmclient_loadhsmrt.c; the memcpy() call.

0216.bootloader-ti.zip