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.

MCU-PLUS-SDK-AM243X: Cannot SBL_OSPI boot the hs_fs application image on my custom board.

Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: LP-AM243, UNIFLASH

Hello, 

I'm experiencing the same symptoms in url below.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1202676/processor-sdk-am64x-cannot-ospi-boot-the-hs_fs-application-image-on-am6442-a53-core

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1214401/am6442-sbl_ospi---------bootloader_parsemulticoreappimage-returns--1

I am developing a custom board with the AM2431ALX (HS-FS).

The built-in SPI flash memory is the S25HL512T, which is exactly the same as the evaluation board LP-AM243.

The initialization was confirmed to have been carried out normally, and the sample images of sbl_ospi_am243x and hello_world_am243x were flashed to flash memory through UART Uniflash, confirming that they were operating normally.

(I'm sure there's no problem here.)

So, I soldered W25Q128JVSIQ(winbond) SPI Flash memory considering pinmap after desolding this SPI flash memory(S25HL512T).
After the re-initialization operation, I was able to download and run ospi_flash_diag_am243x sample image in CCS
to obtain the following spi flash parameters.
(The file is not loaded, so I'm uploading some of the images.)

I saved this file as a json file.

Also, I pressed 'automatically configure flash' - Load from JSON button in syscfg tool of sbl_ospi_am243x sample project.

I compared the parameters and confirmed that they were input normally.

Also, syscfg in the sbl_uart_uniflash_am243x sample project also loaded the JSON file in the same way as above.

I built these project without modifying anything. I completed the flash successfully through UART Uniflash, including hello_world_am243x sample image. ([STATUS] SUCCESS !!!)

The contents of the .cfg file used in UART Uniflash are as follows.


--flash-writer=custom_built/sbl_uart_uniflash.Release.hs_fs.tiimage
# '--operation=flash-phy-tuning-data' Even if I tried adding it, the result was the same.
--file=custom_built/sbl_ospi.Debug.hs_fs.tiimage --operation=flash --flash-offset=0x0      # Even if I tried "Release", the result was the same.
--file=custom_built/hello_world_am243x-evm_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0x80000      # Even if I tried "Release", the result was the same.

However, it showed the same symptoms as the URL that I had above linked.
To be more specific, (Debugged using loop_forever.)
sbl_ospi_am243x example code
ㄴ(main.c : 132) status = Bootloader_parsemultiCoreAppImage
    ㄴ(bootloader.c : 661) status = Bootloader_verifyMulticoreImage
        ㄴ(bootloader.c : 581) authStatus = Bootloader_socAuthImage
            ㄴ(bootloader_soc.c : 1244) status = Sciclient_procBootAuthAndStart
                 ㄴ(sciclient_procboot.c : 267) respParam.flags < This value is 2 when it is operating normally, and this value is 0 after SPI flash memory changes.
I thought it was an authentication problem, so I unchecked the BOOTLOADER-Disable Auth For Application Image from syscfg of the sbl_ospi_am243x project and rebuilt and flahs, and I was able to confirm that it booted normally and Hello world was also output normally.
Is there a way to boot normally without unchecking this?
And when you uncheck this check, what are the problems?
Please help me
Thank you.
  • Hello Seong,

    Is there a way to boot normally without unchecking this?

    I believe you mean without checking this because when you check that option, the SBL skips the authentication of the appimage and boots it directly. So, if you keep this unchecked, the SBL will request authentication of the appimage and only if it successful it boots the appimage.

    And when you uncheck this check, what are the problems?

    When you do so, the SBL skips the authentication checks. While this may be convenient in development stage to get past any authentication failure issues, this is not recommended in production at all. In production, you would want to authenticate any appimage before booting it to make sure the appimage is not corrupted accidentally or maliciously.

    -------------

    Coming to the issue, do you see the authentication failures on every POR or randomly?

    Regards,

    Prashant

  • Closing this thread as the issue is further discussed here: e2e.ti.com/.../5143260