LP-AM243: Specifications of SBL OSPI Multi-Partition

Hello, Prashant

Thank you for your answer. Even if BANK did not continue as for me, I hoped that I worked normally.
I must revise SBL OSPI MULTI-PARTITION application.
Please tell me a little more.

A1)
/* load and run all CPUs, if a application is not found, the core is run with a while(1); loop */
In this comment sentence, I am listed with loop.
I was not able to find it where you carried out while(1).

I confirmed Bootloader_socGetCoreVariant().
coreVariant = (CSL_REG32_RD(BOOTLOADER_DEVICE_JTAG_USERID_REG) & BOOTLOADER_DEVICE_JTAG_USERID_CORENUM_MASK);

#define CSL_REG32_RD(p) (CSL_REG32_RD_RAW((volatile uint32_t *) (p)))
In this way, a loop does not make it.

Where are you doing loop?

A1-2, A2)
Please advise specific R5F application about a method to carry out.

If there is not appimage in flash memory in Bootloader_parseMultiCoreAppImage(), I think that it is terminated abnormally.
Is this way of thinking right?
Please tell me the function name if right you file it, and where you open.
I want to know an access method to appimage.

My ideas are as follows:
retcode = Bootloader_parseMultiCoreAppImage();
if (retcode < 0) {
  exist = open();
  if (exist == ok) {
    //　Normal processing
  }
  else {
    // I do nothing
  }
}

Do you have the idea other than the existence confirmation of the file?
Please tell me if you have an idea.

Regards.

Hi Yoshiki,

A1) I checked the full code of SBL_OSPI_MULTI_PARTITION and realize that comment is misleading. The default SBL_OSPI_MULTI_PARTITION will always try to find & parse an appimage for each core via the Bootloader_parseMultiCoreAppImage function.

If this function returns FAILURE (status = SystemP_FAILURE), the SBL considers this as a boot failure & so will not execute any further steps guarded by the if condition "status == SystemP_SUCCESS".

A1-2, A2) In order to exclude running an application on a core, you can comment the corresponding code like shown for the M4F core

diff --git a/examples/drivers/boot/sbl_ospi_multi_partition/am243x-lp/r5fss0-0_nortos/main.c b/examples/drivers/boot/sbl_ospi_multi_partition/am243x-lp/r5fss0-0_nortos/main.c
index b663b288..cd8e6c89 100644
--- a/examples/drivers/boot/sbl_ospi_multi_partition/am243x-lp/r5fss0-0_nortos/main.c
+++ b/examples/drivers/boot/sbl_ospi_multi_partition/am243x-lp/r5fss0-0_nortos/main.c
@@ -182,10 +182,10 @@ int main(void)
         }
         if (!Bootloader_socIsMCUResetIsoEnabled())
         {
-            if(SystemP_SUCCESS == status)
-            {
-                status = App_bootCpu( CONFIG_BOOTLOADER_FLASH_M4FSS0_0, CSL_CORE_ID_M4FSS0_0 );
-            }
+            /*if(SystemP_SUCCESS == status)*/
+            /*{*/
+            /*    status = App_bootCpu( CONFIG_BOOTLOADER_FLASH_M4FSS0_0, CSL_CORE_ID_M4FSS0_0 );*/
+            /*}*/
         }
         if(SystemP_SUCCESS == status)
         {

Otherwise, the idea you mention also works. You may do nothing if Bootloader_parseMultiCoreAppImage returns FAILURE & proceed forward with booting appimages for the other cores.

Regards,

Prashant