LP-AM261: Boot from OSPI is not as expected

Mallikarjuanreddy Gadagi

Part Number: LP-AM261
Other Parts Discussed in Thread: UNIFLASH

I was able flash the .out file to R5_0 core through the UART mode to using the sbl_null cfg with modification to add the binary .out file

I have also attahed the cfg file for reference. and added the logs.

After the flashing complete changed to OSPI mode. I can only see the default SBL logs , but expected .out is not executing.

Please do suggest the missing cfg/procedure

UART logs after boot:

INFO: Bootloader_socLoadHsmRtFw:82: Device Type : HSFS
INFO: Bootloader_socLoadHsmRtFw:84: HSMRT Size in Bytes : 27603
INFO: Bootloader_socLoadHsmRtFw:97: hsm runtime firmware load complete ...
Starting NULL Bootloader ...
INFO: Bootloader_runCpu:205: CPU r5f0-1 is initialized to 500000000 Hz !!!
KPI_DATA: [BOOTLOADER_PROFILE] CPU Clock : 500.000 MHz
KPI_DATA: [BOOTLOADER_PROFILE] Boot Media : undefined
KPI_DATA: [BOOTLOADER_PROFILE] Boot Image Size : 0 KB
KPI_DATA: [BOOTLOADER_PROFILE] Cores present :
KPI_DATA: [BOOTLOADER PROFILE] System_init : 79us
KPI_DATA: [BOOTLOADER PROFILE] Drivers_open : 22us
KPI_DATA: [BOOTLOADER PROFILE] LoadHsmRtFw : 24774us
KPI_DATA: [BOOTLOADER PROFILE] SBL End : 9629us
KPI_DATA: [BOOTLOADER_PROFILE] SBL Total Time Taken : 34504us

NULL Bootloader Execution Complete...
INFO: Bootloader_loadSelfCpu:257: CPU r5f0-0 is initialized to 500000000 Hz !!!
INFO: Bootloader_runSelfCpu:267: All done, reseting self ...

default_sbl_null_eth.cfg

C:\ti\mcu_plus_sdk_am261x_11_01_00_19\tools\boot>python uart_uniflash.py -p COM16 --cfg="C:\ti\mcu_plus_sdk_am261x_11_01_00_19\tools\boot\sbl_prebuilt\am261x-lp\default_sbl_null_eth.cfg"

Parsing config file ...
Parsing config file ... SUCCESS. Found 3 command(s) !!!

Executing command 1 of 3 ...
Found flash writer ... sending sbl_prebuilt/am261x-lp/sbl_uart_uniflash.release.tiimage

Sent flashwriter sbl_prebuilt/am261x-lp/sbl_uart_uniflash.release.tiimage of size 51601 bytes in 6.37s.

Executing command 2 of 3 ...
Command arguments : --file=sbl_prebuilt/am261x-lp/sbl_null.release.tiimage --operation=flash --flash-offset=0x0
Sent sbl_prebuilt/am261x-lp/sbl_null.release.tiimage of size 182940 bytes in 20.05s.
[STATUS] SUCCESS !!!

Executing command 3 of 3 ...
Command arguments : --file=sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin --operation=flash-sector-write --flash-offset=0x81000
Sending sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin: 242844bytes [00:23, 11142.78bySending sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin: 243873bytes [00:23, 11126.27bySending sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin: 243873bytes [00:23, 11126.27bySending sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin: 243874bytes [00:23, 11126.27bySending sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin: 243875bytes [00:24, 11126.27bySending sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin: 243876bytes [00:26, 11126.27bySending sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin: 243877bytes [00:26, 11126.27by Sent sbl_prebuilt/am261x-lp/enet_cpsw_tcpserver_am261x-lp_r5fss0-0_freertos_ti-arm-clang.bin of size 242392 bytes in 24.91s.
[STATUS] SUCCESS !!!

All commands from config file are executed !!!

1 month ago

0 Rijohn Pius 1 month ago

TI__Expert 4120 points

Hi Mallikarjuanreddy,

Thank you for the query!!

As I see from the quary your are trying to program the flash using uart_uniflash python script .

There are couple of points to be noted here:

1. SBL null does the power On and clock setup for the R5F CPUs, reset and run all the CPUs in a "WFI" loop

2. SBL NULL does NOT boot any application binary.

3. Inorder to boot any application binary you shall use/modify the mcelf_sbl_ospi.cfg file present in the same sbl_prebuilt folder as default_sbl_null.cfg.

4. Update the application image path in lines 24/25 . Ensure that type of binary is release.mcelf

5. Comment out the XIP file path in line 27/28 is not used.

6. Follow the same steps for UART flashing [ensure booth mode is set to UART while flashing] with only change in the mcelf_sbl_ospi.cfg

python uart_uniflash.py -p COM16 --cfg="C:\ti\mcu_plus_sdk_am261x_11_01_00_19\tools\boot\sbl_prebuilt\am261x-lp\mcelf_sbl_ospi.cfg"

Thanks & Regards,
Rijohn

0 Mallikarjuanreddy Gadagi 1 month ago in reply to Rijohn Pius

Intellectual 270 points

Hi Rijohn,

Thanks for clarification.

Do we need the mcelf file needed for the flashing is it ok to use the .out or .bin file is fine

0 Rijohn Pius 1 month ago in reply to Mallikarjuanreddy Gadagi

TI__Expert 4120 points

Hi Mallikarjuanreddy,

Yes application image should be in .mcelf from 11.0 SDK version.

https://software-dl.ti.com/mcu-plus-sdk/esd/AM261X/11_01_00_19/exports/docs/api_guide_am261x/TOOLS_FLASH.html#TOOLS_FLASH_UART_UNIFLASH

Thanks & Regards,
Rijohn

0 Mallikarjuanreddy Gadagi 1 month ago in reply to Rijohn Pius

Intellectual 270 points

Hi Rijohn,

Ok, from the SDK documentation, i found we need to convert the .out to mcelf format using the genimage.py (C:\ti\mcu_plus_sdk_am261x_11_01_00_19\tools\boot\multicore-elf)

So, during this procedure i finding the few errors

Logs:

C:\ti\mcu_plus_sdk_am261x_11_01_00_19\tools\boot\multicore-elf>python genimage.py --core-img="0":"r0.out" --output="app.mcelf"
Traceback (most recent call last):
File "C:\ti\mcu_plus_sdk_am261x_11_01_00_19\tools\boot\multicore-elf\genimage.py", line 40, in <module>
from modules.otfaecc_structs import *
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\ti\mcu_plus_sdk_am261x_11_01_00_19\tools\boot\multicore-elf\modules\otfaecc_structs.py", line 35, in <module>
from construct import Struct, Int16ul, Int16ub, \
ModuleNotFoundError: No module named 'construct'

+1 Rijohn Pius 1 month ago in reply to Mallikarjuanreddy Gadagi

TI__Expert 4120 points

Hi Mallikarjuanreddy,

From the error logs, I think this error is due to the missing python packages mentioned in C:\ti\mcu_plus_sdk_am261x_11_01_00_19\requirements.txt

Can you please ensure the below steps are done:

Open a terminal in this path and do: pip install -r requirements.txt
For more information please check: https://software-dl.ti.com/mcu-plus-sdk/esd/AM261X/11_01_00_19/exports/docs/api_guide_am261x/SDK_DOWNLOAD_PAGE.html
Once all the packages are installed, rebuild the project once again from ccs and the .mcelf format image should be present in Release/Debug folder(same location as .out files) as per your active build configuration.

Thanks & Regards,

Rijohn

0 Mallikarjuanreddy Gadagi 1 month ago in reply to Rijohn Pius

Intellectual 270 points

Hi Rijohn,

Thanks for the update and link

Which is solved the issue

Arm-based microcontrollers

Arm-based microcontrollers forum

LP-AM261: Boot from OSPI is not as expected