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.

[AM6442]how to boot from SD for HS mode

Other Parts Discussed in Thread: AM6442

LSDK:08_02_00_23

compile u-boot follow https://software-dl.ti.com/processor-sdk-linux-rt/esd/AM64X/08_02_00_23/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html

generate tiboot3.bin tispl.bin_HS u-boot.img_HS,and 

  • generate tiboot3.bin tispl.bin_HS u-boot.img_HS and replace the files of boot the board was powered on and nothing printed on console

  • generate tiboot3.bin tispl.bin_HS u-boot.img_HS and replace the files of boot.

    the board was powered on and nothing printed on console

  • Hi! The subject owner is currently out of the office. Please allow a couple of days for a response. Thanks.

  • Hello,
    Please let us know which board and SoC (GP or HS) you're testing with?
    The binary built for GP and HS are not exchangeable.
    software-dl.ti.com/.../UG-General-Info.html
    Best,
    -Hong

  • Board: AM6442

    I want to test with SOC ON HS .

    follow the steps 

    R5
    $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- am64x_hs_evm_r5_defconfig O=<output directory>/r5
    $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- O=<output directory>/r5
    $ cd ../k3-image-gen-<version>
    $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- SOC=am64x HS=1 SBL=<output directory>/r5/spl/u-boot-spl.bin SYSFW_HS_PATH=<path to tisdk>/board-support/prebuilt-images/ti-sci-firmware-am64x-hs-enc.bin SYSFW_HS_INNER_CERT_PATH=<path to tisdk>/board-support/prebuilt-images/ti-sci-firmware-am64x-hs-cert.bin
    
    Sign OPTEE and ATF binaries
    $ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl31.bin bl31.bin.signed
    $ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl32.bin bl32.bin.signed
    
    A53
    $ make ARCH=arm CROSS_COMPILE=aarch64-none-linux-gnu- am64x_hs_evm_a53_defconfig O=<output directory>/a53
    $ make ARCH=arm CROSS_COMPILE=aarch64-none-linux-gnu- ATF=<path to tisdk>/board-support/prebuilt-images/bl31.bin.signed TEE=<path to tisdk>/board-support/prebuilt-images/bl32.bin.signed  O=<output directory>/a53


  • Hello,
    One hypothesis is the SoC on your board is GP device instead of HS device:
    ==== How to know the device type (GP vs HS):
    Onchip ROM dump Soc_ID of the device for all device types (GP and HS) from peripheral boot modes like UART, USB-DFU...

    /* SOC ID definition */
    typedef struct __attribute__((packed, aligned(4)))
    {
        uint32_t            numBlocks;
        SOCID_PubInfo_t     pubInfo;
        SOCID_SecInfo_t     secInfo;
    }
    SOCID_Obj;

    - On GP:
    NumBlocks=1 (4 bytes)
    sizeof(pubInfo)=32 bytes
    Only the pubInfo is dumped by ROM code

    - On HS:
    NumBlocks=2 (4 bytes)
    sizeof(pubInfo)=32 bytes
    sizeof(secInfo)=168 bytes
    Both the pubInfo and secInfo are dumped by ROM code

    I'm attaching two sample log files captured from UART boot mode on GP and HS for your reference.

    Best,

    -Hong

    01000000011a0000616d36347800000000000000475020200000010000000100

    02000000011a0000616d3634780000000000000048535345000002000000020002a6000001000100b018658ad99dc903c8c9bfb27b12751099920a042ad1dfea7b7ba57369f15546de285edde6a7b39a8bdc40a27b237f8fb1e57f245e80b929c1e28b024aa2ecc61f6002b07cd9b0b7c47d9ca8d1aae57b8e8784a12f636b2b760d7d98a18f189760dfd0f23e2b0cb10ec7edc7c6edac3d9bdfefe0eddc3fff7fe9ad875195527db385c173177b2bb2de85f229f6c0d6618d3b91e52b3d77cbaa3ee92cc8533042