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.

AM2634: Optimize the boot time in HS-SE mode lead to jump from SBL to app failure

Part Number: AM2634

I refer to this URL link to optimize the boot time of RBL/SBL.

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1222158/faq-am2634-mcu-plus-sdk-am263x-how-to-understand-optimize-the-boot-time-of-rbl-sbl

I use the tifs8..5+SDK8.6  to try.

1.I use  the AM2634 in HS-SE mode(write some keys), so I shall complie tifs8.5 to generate new HSM(hsmRtImg.h).

2.Second, I modfiy SDK8.6 as shown in figure, and complie it (command:gmake libs-clean -s || gmake libs -s)

3.modify the flash chip ID in SBL_QSPI example, complie SBL_QSPI and sign it:

  gmake -s -C ./examples/drivers/boot/sbl_qspi/am263x-cc/r5fss0-0_nortos/ti-arm-clang/ syscfg-gui

  python mcu_rom_image_gen.py --image-bin sbl_qspi_am263x-cc_r5fss0-0_nortos_ti-arm-clang.bin --core R5 --swrv 1 --loadaddr 0x70002000 --sign-key mcu_custMpk.pem --out-image sbl_qspi_am263x-cc_r5fss0-0_nortos_ti-arm-clang.release.hs.tiimage --debug DBG_PUBLIC_ENABLE

  gmake -C examples/drivers/boot/sbl_qspi/am263x-cc/r5fss0-0_nortos/ti-arm-clang/ all -s

4.complie the example of hello word(App). And burn SBL and helloword by uart.

5.power on the device again and start from the qspi, the reasult is that it successfully jumped from SBL to App.

Nextly, I want to separate SBL and HSM firmware(SBL without incorporated HSMRt firmware):

1.Use a patch file from TI E2E platform to change the SDK in order to optimize the boot time of RBL/SBL

   git apply boot_5F00_time_5F00_1.diff

2.complie SDK8.6(command:gmake libs-clean -s||gmake libs -s)

3.complie SBL_QSPI and sign it:

   python mcu_rom_image_gen.py --image-bin sbl_qspi_am263x-cc_r5fss0-0_nortos_ti-arm-clang.bin --core R5 --swrv 1 --loadaddr 0x70002000 --sign-key mcu_custMpk.pem --out-image sbl_qspi_am263x-cc_r5fss0-0_nortos_ti-arm-clang.release.hs.tiimage --debug DBG_PUBLIC_ENABLE

   gmake -C examples/drivers/boot/sbl_qspi/am263x-cc/r5fss0-0_nortos/ti-arm-clang/ all -s

11.use array2bin.c, Convert the hsmRtImg.h file to hsmRtImg.bin

12.burn them by uart (SBL+HSM+helloword),HSM is in 0xA0000

13.power on the device again and start from the qspi, the reasult is that it failurely jumped from SBL to App.

In addition, the same attempt was made in tifs8.6+sdk9.0.0.13 and the same results were obtained. (Every attempt is in HS-SE mode, not do same attempt in HS-FS mode, maybe it is a useful information)

  • Hi ,

    Can you try using this file ?

    main_hsse.c
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    /*
    * Copyright (C) 2018-2021 Texas Instruments Incorporated
    *
    * Redistribution and use in source and binary forms, with or without
    * modification, are permitted provided that the following conditions
    * are met:
    *
    * Redistributions of source code must retain the above copyright
    * notice, this list of conditions and the following disclaimer.
    *
    * Redistributions in binary form must reproduce the above copyright
    * notice, this list of conditions and the following disclaimer in the
    * documentation and/or other materials provided with the
    * distribution.
    *
    * Neither the name of Texas Instruments Incorporated nor the names of
    * its contributors may be used to endorse or promote products derived
    * from this software without specific prior written permission.
    *
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    This file optimizes has been tested on HSSE device for 09.02 release. Do let me know if this helps.

    Best Regards,
    Aakash

  • Can you provide the diff file corresponding to SDK9.2? The diff files linked below are applicable to SDK8.5, but are slightly different in other versions and cannot be used directly.

      https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1222158/faq-am2634-mcu-plus-sdk-am263x-how-to-understand-optimize-the-boot-time-of-rbl-sbl

  • Hope to get your reply

  • Hi,

    We cannot provide any interim fixes and as the secondary bootloaders are customer owned, it should be in customers responsibility to keep up with the modifications.

    Anyways, the FAQ is planned to be integrate as part of 10.00 release (upcoming in Aug 2024).

    I hope this helps.

    Best Regards,
    Aakash