AM6442: LINUX BOOT ERROR

Hi Tuna,

The frequency at which the core run can't be changed via Sysconfig. The frequency change you did probably is the timer frequency which serve different purpose.

Anyway, could you please tell what SBL you are using. Is it SBL_OSPI_LINUX? Also, have you made any changes to the SBL you are using? I ask this because the default SBL does not generate logs like "ERROR: Bootloader_socCpuResetReleaseSelf"

Regards,

Prashant

Hi Prashant,

You are right about the first part.
I changed the timer frequency (Instance TIMER8 - Input Clock Frequency: 26000000 - MCU_HFOCO). 
Then I set it back to the default value of 25000000.

I am using SBL_OSPI_LINUX and I didn't change anything.
In the screenshot below you can see the part where Bootloader_socCpuResetReleaseSelf() is located and called in sbl_ospi_linux.



Regards,

Hi Tuna,

I am not able to access the attached image on my internal network. Could you please drag & drop the image you want to share.

Thanks!

Hi Tuna,

Could you please let me know what all images you have flashed in OSPI & at what offsets.

Hi Prashant,
sbl_ospi_linux.Debug.hs.tiimage.fs --> 0x0
ipc_rpmsg_echo_linux_system.release.appimage.hs --> 0x80000
linux.appimage.hs --> 0x100000
uboot.img --> 0x300000

Don't be confused by u-boot.img and linux.appimage parts. 
Even when I don't flash them, the error persists.
Additionally, I debugged sbl and found that the main error is caused by "App_loadImages(bootHandle, &bootImageInfo);" and "App_runCpus(bootHandle, &bootImageInfo);" functions in sbl_ospi_linux.
Status variable returns -1 in these functions.
When I flash sbl_ospı_linux to the board by putting these functions in the comment line, the error I gave you at the beginning continues.
The reason why the status variable returns -1 in these functions is the line "status = Bootloader_verifyMulticoreImage(handle);" of the function "int32_t Bootloader_parseMultiCoreAppImage(Bootloader_Handle handle, Bootloader_BootImageInfo *bootImageInfo)" in bootloader.c.
This line generates an hs_fs validation error that I don't understand.

Thank you for your help.
Regards,

Hi Tuna,

Tuna Girisken said:

ipc_rpmsg_echo_linux_system.release.appimage.hs --> 0x80000

It looks like you have flashed HS-SE appimages identified by the extension .appimage.hs. If so, this would explain why the boot is failing in Bootloader_verifyMulticoreImage.

If you are using HS-FS device type, please use the images with extensions .hs_fs.tiimage & .appimage.hs_fs

Please have a look at the below FAQ for more info:

[FAQ] AM64X: How can I flash SOC initialization binaries on HS - FS HW versions .

Rerds,

Prashant

Hi Prashant,

Actually, I made a typo.

My current file structure:

sbl_ospi_linux.Debug.tiimage.hs_FS                  --> 0x0
ipc_rpmsg_echo_linux_system.release.appimage.hs_FS  --> 0x80000
linux.appimage.hs_FS                                --> 0x100000
uboot.img                                           --> 0x300000

Hello Tuna,

Tuna Girisken said:

I'm currently working with ti-processor-sdk-linux-am64xx-evm-08.05.00.21.

You said here you are working with PSDK v8.5. If so, I would like to know how are you generating the Linux Appimage because the PSDK v8.5 contains signed images of bl31.bin & bl32.bin. However, MCU+ SDK requires unsigned images of the same.

Additionally, could you also let me know the MCU+ SDK version you are using.

Regards,

Prashant

I am using the last version (v08.06)

Hi Tuna,

Your other thread https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1228266/am6442-spl-op-tee-insecure-configuration-error-during-boot-stage is resolved. Could you please clarify if the issue in this thread is different from the issue in other thread.

Regards,

Prashant