• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 174 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

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

MCU-PLUS-SDK-AM243X: authentication of appimages fails on custom board fails in SBL_OSPI

Dominik Fischer
Intellectual 480 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi TI-Team,

I have the exact same problem as described in the linked issue (https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1349306/mcu-plus-sdk-am243x-cannot-sbl_ospi-boot-the-hs_fs-application-image-on-my-custom-board-am2431alv/5148133?tisearch=e2e-sitesearch&keymatch=%25252520user%2525253A572738#5148133)

I use SBL_OSPI, which is adjusted to my custom board (custom flash, custom DDR etc.) this works fine if the option "Disable Auth For Application Image" is unchecked. I can then load firmware files successfully. As soon as this Authentication option is checked the SBL_OSPI cannot start the flashed .appimage.hs_fs at 0x80000. If I debug I see that it fails at the same position as mentioned in the linked thread. The content of 0x60080000 is also equal

Yes, I also integrated the suggested workaround shown in various other threads, the following code fraction is inserted just before the Bootloader_parseMultiCoreAppImage(...).

            /* WORKAROUND: Enable the DAC mode */
            OSPI_Handle ospi_handle = OSPI_getHandle(CONFIG_OSPI0);
            OSPI_enableDacMode(ospi_handle);

I am currently using the MCU+ SDK delivered with the latest www.ti.com/.../09.02.00.08

I also tried to replicate on AM64x-EVM but there everything worked fine, I could start/authenticate any image given. Even my custom images using all R5-cores and now beeing bigger than 1,6 MB

Help would be highly appreciated. What is the problem? Is there a bigger bug in somewhere in MCU+ SDK and I currently need to disable authentication at all?

Kind regards,

Dominik

  • 0
    TI__Guru 56751 points

    Hello,

    Could you please go through the following thread & provide relevant inputs like SYSFW logs

    https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/908/t/1400448

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 480 points

    Sorry for the late response. The mentioned thread actually is a bit difficult to follow as multiple users respondended, but I got through and instructions for Sysfw logs were clear.

    One thing: I was not able to add dump_sysfw_logs() directly after Bootloader_socAuthImage() as this is not called from SBL_OSPI but in functions from bootloader.c. The dump function is now directly called after the Bootloader_parseMultiCoreAppImage().

    Here the printed SYSFWLOGS from Debug UART, I used the function as described. If you need other format let me know.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    <<SYSFW_LOGS
    180010C
    0x61C0009C
    0x61276CB7
    0x61276CB7
    0xC20101
    0xC20024
    0x61800101
    0x61C0008A
    0xC20104
    0xC20024
    0x61800104
    0x61C0008A
    0xC20100
    0xC20024
    0x61800100
    0x61C0008A
    0x62000000
    0xC2010D
    0xC20024
    0x6180010D
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • +1 in reply to Dominik Fischer
    Intellectual 480 points

    Hi Prashnat,

    I found a workaround, which currently helps me to load at least big hello world projects with signature checking activated. I modified the bootloader to take the appimage from a specified address in DDR RAM.

    1) switched the bootloader settings in Sysconfig

    2) Activated DDR (sysconfig, ddr-config header) on my custom board

    3) Added the following code in the SBL OSPI

    Fullscreen
    1
    2
    3
    4
    uint8_t* p_data_buffer = loadFromFlash(&bootParams.bufIoTempBufSize);
    bootParams.bufIoTempBuf = p_data_buffer;
    bootParams.bufIoDeviceIndex = ~0;
    bootParams.memArgsAppImageBaseAddr = (uintptr_t)p_data_buffer;
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

     

    Note: My loadFromFlash() function reads in blocks from the flash as soon as I tried to load the complete appimage at once I did not get the complete appimage in DDR, it was cut somewhere in the middle. Maybe a problem with Flash_read(…) and big read-sizes?

     

    This whole process seems to work fine for hello_world projects build in CCS. I even added a big array and bloated the hs_fs image to > 3 MB. Authentication and starting of the application/firmware still worked. Nevertheless, I am still not able to load my custom application, but I am now facing different errors, the Signature check does not fail anymore.

    ERROR: Bootloader_socCpuSetEntryPoint:908: CPU set config failed for r5f0-1Some tests have failed!!

  • 0 in reply to Dominik Fischer
    TI__Guru 56751 points

    Hi Dominik,

    Thank you for following up. Let me go through the results & get back to you!!

  • +1 in reply to Prashant Shivhare
    Intellectual 480 points

    I think we can close this issue for now. I switched to BOOTLOADER_MEDIA_MEM and with the correct configuration and some explicitely reserved space on DDR for bootloader the issue is solved. Prashant showed how to implement with 2 Bootloader instances in this issue:

    e2e.ti.com/.../5393976