• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 98 subscribers
  • Views 558 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM625: Linux SDK support for SK-AM62B-P1 and SK-AM62-LP

Koichiro Tashiro
Mastermind 22915 points
Part Number: AM625
Other Parts Discussed in Thread: SK-AM62B-P1, SK-AM62-LP, SK-AM62, SK-AM62B

Hi,

My customer has below two boards and wants to use Linux SDK08.06.00.42.
https://www.ti.com/tool/SK-AM62B-P1
https://www.ti.com/tool/SK-AM62-LP

They tried to use below prebuilt SD card image, but it does not work.
https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-BDCgfEXHLk/08.06.00.42/tisdk-default-image-am62xx-evm.wic.xz

Below SDK09.01.00.08 images worked.
https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-BDCgfEXHLk/09.01.00.08/tisdk-default-image-am62xx-evm.wic.xz
https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-BDCgfEXHLk/09.01.00.08/tisdk-default-image-am62xx-lp-evm.wic.xz

Questions:
Q1) Does SDK08.06.00.42 support SK-AM62B-P1 and SK-AM62-LP?
Q2) If not, could you tell me how to modify SD card image for SK-AM62B-P1 and SK-AM62-LP with SDK08.06.00.42?

Thanks and regards,
Koichiro Tashiro

  • 0
    TI__Guru 68290 points

    Hello Koichiro,
    1/. what are the board revison for the two boards? for example, PROC142xx
    2/. "it does not work" means not booting at all?
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    TI__Mastermind 22915 points

    Hi Hong,

    Hong Guan64 said:
    1/. what are the board revison for the two boards? for example, PROC142xx

    SK-AM62B-P1
    PCB revision : PROC142A
    Assembly variant : 002

    SK-AM62-LP
    PCB revision : PROC124E2
    Assembly variant : PROC124E2A

    Hong Guan64 said:
    2/. "it does not work" means not booting at all?

    Let me check it with the customer.

    Thanks and regards,
    Koichiro Tashiro

  • 0 in reply to Koichiro Tashiro
    TI__Guru 68290 points

    Hello Koichiro,
    In SDK 8.6, the WIC image is for SK-AM62 board.
    It is possible to build u-boot for SK-AM62 and SK-AM62-LP
    software-dl.ti.com/.../UG-General-Info.html
    Compiling R5 and ARM64 images
    - SK-AM62 am62x_evm_r5_defconfig am62x_evm_a53_defconfig
    - SK-AM62-LP am62x_lpsk_r5_defconfig am62x_lpsk_a53_defconfig
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    TI__Mastermind 22915 points

    Hi Hong,

    Hong Guan64 said:
    It is possible to build u-boot for SK-AM62 and SK-AM62-LP

    Do you mean "it is possible to build u-boot for SK-AM62B-P1 and SK-AM62-LP"?

    Hong Guan64 said:
    - SK-AM62 am62x_evm_r5_defconfig am62x_evm_a53_defconfig

    This is also for SK-AM62B-P1?

    Thanks and regards,
    Koichiro Tashiro

  • 0 in reply to Koichiro Tashiro
    TI__Guru 68290 points
    Koichiro Tashiro said:
    Do you mean "it is possible to build u-boot for SK-AM62B-P1 and SK-AM62-LP"?

    yes.

    Koichiro Tashiro said:
    This is also for SK-AM62B-P1?

    yes.

    SK-AM62 family boards: PROC114x (SK-AM62, SK-AM62B) & PROC142x (SK-AM62-P1, SK-AM62B-P1)

    Best,
    -Hong

  • 0 in reply to Hong Guan64
    TI__Mastermind 22915 points

    Hi Hong,

    Based on your replies, the customer tried to rebuild u-boot for SK-AM62-LP with SDK8.6.
    But the code stops at below log.

    U-Boot SPL 2021.01-00001-g45cb7e44ae (Jan 23 2024 - 14:44:39 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
spl_load_fit_image: Skip load 'atf': image size is 0!
spl_load_fit_image: Skip load 'tee': image size is 0!
spl_load_fit_image: Skip load 'dm': image size is 0!
Authentication passed
Authentication passed
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...


    The build sequence he used was below. Do you see any mistakes here?
    username@debian:~/data/bcp/240123/sdk0806$ mkdir tibin
username@debian:~/data/bcp/240123/sdk0806$ cp /home/username/ti-processor-sdk-linux-am62xx-evm-08.06.00.42/board-support/prebuilt-images/bl3* tibin/.
username@debian:~/data/bcp/240123/sdk0806$ mkdir ti-sysfw
username@debian:~/data/bcp/240123/sdk0806$ cp /home/username/ti-processor-sdk-linux-am62xx-evm-08.06.00.42/board-support/prebuilt-images/ti-fs-firmware-am62x* ti-sysfw/.
username@debian:~/data/bcp/240123/sdk0806$ mkdir ti-dm
username@debian:~/data/bcp/240123/sdk0806$ mkdir ti-dm/am62xx
username@debian:~/data/bcp/240123/sdk0806$ cp /home/username/ti-processor-sdk-linux-am62xx-evm-08.06.00.42/board-support/prebuilt-images/ipc_echo_testb_mcu1_0_release_strip.xer5f ti-dm/am62xx/.

username@debian:~/data/bcp/240123/sdk0806$ export TI_SECURE_DEV_PKG=/home/username/data/bcp/240123/sdk0806/core-secdev-k3
username@debian:~/data/bcp/240123/sdk0806$ export UBOOT_DIR=/home/username/data/bcp/240123/sdk0806/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654/
username@debian:~/data/bcp/240123/sdk0806$ export K3IG_DIR=/home/username/data/bcp/240123/sdk0806/k3-image-gen-2022.01/
username@debian:~/data/bcp/240123/sdk0806$ export DMFW_DIR=/home/username/data/bcp/240123/sdk0806/ti-dm/am62xx
username@debian:~/data/bcp/240123/sdk0806$ export SYSFW_DIR=/home/username/data/bcp/240123/sdk0806/ti-sysfw
username@debian:~/data/bcp/240123/sdk0806$ cd $UBOOT_DIR
username@debian:~/data/bcp/240123/sdk0806/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- am62x_lpsk_r5_defconfig O=$UBOOT_DIR/out/r5
username@debian:~/data/bcp/240123/sdk0806/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- O=$UBOOT_DIR/out/r5
username@debian:~/data/bcp/240123/sdk0806/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654$ cd $K3IG_DIR
username@debian:~/data/bcp/240123/sdk0806/k3-image-gen-2022.01$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- SOC=am62x SOC_TYPE=hs-fs SBL=$UBOOT_DIR/out/r5/spl/u-boot-spl.bin SYSFW_DIR=$SYSFW_DIR
username@debian:~/data/bcp/240123/sdk0806/k3-image-gen-2022.01$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- SOC=am62x SOC_TYPE=gp SBL=$UBOOT_DIR/out/r5/spl/u-boot-spl.bin SYSFW_DIR=$SYSFW_DIR
username@debian:~/data/bcp/240123/sdk0806/k3-image-gen-2022.01$ cd ../tibin
username@debian:~/data/bcp/240123/sdk0806/tibin$ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl31.bin bl31.bin.signed
username@debian:~/data/bcp/240123/sdk0806/tibin$ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl32.bin bl32.bin.signed
username@debian:~/data/bcp/240123/sdk0806/tibin$ cd ../ti-dm/am62xx
username@debian:~/data/bcp/240123/sdk0806/ti-dm/am62xx$ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh ipc_echo_testb_mcu1_0_release_strip.xer5f ipc_echo_testb_mcu1_0_release_strip.xer5f.signed
username@debian:~/data/bcp/240123/sdk0806/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654$ cd u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654/
username@debian:~/data/bcp/240123/sdk0806/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654$ make ARCH=arm CROSS_COMPILE=aarch64-none-linux-gnu- am62x_lpsk_a53_defconfig O=$UBOOT_DIR/out/a53
username@debian:~/data/bcp/240123/sdk0806/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654$ make ARCH=arm CROSS_COMPILE=aarch64-none-linux-gnu- ATF=../tibin/bl31.bin.signed TEE=../tibin/bl32.bin.signed DM=$DMFW_DIR/ipc_echo_testb_mcu1_0_release_strip.xer5f.signed O=$UBOOT_DIR/out/a53


    Could you try to build u-boot for SK-AM62-LP with SDK8.6 and confirm it work on your side?

    Thanks and regards,
    Koichiro Tashiro

  • +1 in reply to Koichiro Tashiro
    TI__Guru 68290 points

    Hello Koichiro,
    I built SDK 8.6 u-boot, and tested u-boot booting on SK-AM62-LP (HS-FS)
    1/. reconfigure "Rules.make" file under SDK installation folder

    - UBOOT_MACHINE=am62x_evm_a53_defconfig
+ UBOOT_MACHINE=am62x_lpsk_a53_defconfig

- UBOOT_MACHINE_R5=am62x_evm_r5_config
+ UBOOT_MACHINE_R5=am62x_lpsk_r5_config

    2/. build u-boot from SDK installation folder
    make u-boot
    make sysfw-image

    I'm attaching the u-boot log for your reference.
    Best,
    -Hong

    Fullscreen am62-lpsk_8.6_boot.log Download 
    U-Boot SPL 2021.01-00001-g45cb7e44ae (Jan 25 2024 - 23:05:31 -0600)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 05:06:58, Feb 24 2023

U-Boot SPL 2021.01-00001-g45cb7e44ae (Jan 25 2024 - 23:05:08 -0600)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2021.01-00001-g45cb7e44ae (Jan 25 2024 - 23:05:08 -0600)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM62x LP SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62-LP-SKEVM rev E2
DRAM:  2 GiB
NAND:  0 MiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0
=>

  • 0 in reply to Hong Guan64
    TI__Mastermind 22915 points

    Hi Bin,

    Thanks for your reply. The customer tried the same, but still it did not work. There was no output on the console. They are checking their build steps now.

    They have a few questions.
    Q1) At below step, "bl31.bin", "bl32bin" and "ipc_echo_testb_mcu1_0_release_strip.xer5f" are used as-is in "ti-processor-sdk-linux-am62xx-evm-08.06.00.42/board-support/prebuilt-images", correct?

    Hong Guan64 said:
    2/. build u-boot from SDK installation folder
    make u-boot
    make sysfw-image

    Q2) If the answer to Q1 is yes, below steps in the customers' build steps are not necessary, correct?

    username@debian:~/data/bcp/240123/sdk0806/tibin$ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl31.bin bl31.bin.signed
username@debian:~/data/bcp/240123/sdk0806/tibin$ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh bl32.bin bl32.bin.signed

username@debian:~/data/bcp/240123/sdk0806/ti-dm/am62xx$ $TI_SECURE_DEV_PKG/scripts/secure-binary-image.sh ipc_echo_testb_mcu1_0_release_strip.xer5f ipc_echo_testb_mcu1_0_release_strip.xer5f.signed



    Thanks and regards,
    Koichiro Tashiro

  • 0 in reply to Koichiro Tashiro
    TI__Guru 68290 points
    Hong Guan64 said:
    2/. build u-boot from SDK installation folder
    make u-boot
    make sysfw-image

    After modifying "Rules.make" as noted in my last reply, only the above two cmds are needed for building u-boot for SK-AM62-LP (HS-FS).
    1/. was the u-boot build process completed successfully by customer?
    2/. what was the SoC type on customer board?
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    TI__Mastermind 22915 points

    Hi Hong,

    Hong Guan64 said:
    1/. was the u-boot build process completed successfully by customer?

    Yes.

    Hong Guan64 said:
    2/. what was the SoC type on customer board?

    HS-FS

    Thanks and regards,
    Koichiro Tashiro

  • +1 in reply to Koichiro Tashiro
    TI__Guru 68290 points

    Hello Koichiro,
    It is good to know SDK8.6 u-boot build completed without error.
    The u-boot binary are under folders once build is complete:
    - tiboot3.bin: under /board-support/k3-image-gen-2022.01/
    - tispl.bin/u-boot.img: /board-support/u-boot_build/a53/
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    TI__Mastermind 22915 points

    Hi Hong,

    Thanks for your help, now the customer is able to build working u-boot.
    This item is now closed.

    Thanks and regards,
    Koichiro Tashiro