• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 429 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.

TDA4VM: TDA4VL: ATF boot failed

li quan
Intellectual 955 points
Part Number: TDA4VM
Other Parts Discussed in Thread: TDA4VL

Hi expers,

At present, the j721s2 board we are using can be started normally using the TI prebuilt ATF image (ti-processor-sdk-linux-j721s2-evm-08_00_03_59/board-support/prebuilt-images/bl31.bin),

However, the ATF compiled from the ATF source code in the SDK cannot be started.

cd ~/ti-processor-sdk-linux-j721s2-evm-08_00_03_59/board-support/trusted-firmware-a-2.5

make ARCH=aarch64 CROSS_COMPILE=aarch64-none-linux-gnu- PLAT=k3 TARGET_BOARD=generic SPD=opteed

It is found that the system is stuck when uboot R5 starts the ATF，

The log information is as follows：

1. TI prebuilt-images:(boot success)

U-Boot SPL 2021.01-dirty (Jun 08 2022 - 20:19:48 +0800)

SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.0--w2021.33-j721s2 (Terrif')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC2
-----------------ATF Image begin (0x70000000)-------------------
f4 03 00 aa f5 03 01 aa f6 03 02 aa f7 03 03 aa
00 06 81 d2 a0 18 a6 f2 00 10 1e d5 df 3f 03 d5
------------------end-------------------
NOTICE:  BL31: v2.5(release):08.00.00.004-dirty
NOTICE:  BL31: Built : 16:15:40, Dec  9 2021
U-Boot SPL 2021.01-dirty (Jun 08 2022 - 16:51:20 +0800)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.0--w2021.33-j721s2 (Terrif')

Trying to boot from MMC2

 2. trusted-firmware-a-2.5 built ATF：(boot failed)

U-Boot SPL 2021.01-dirty (Jun 08 2022 - 20:19:48 +0800)

SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.0--w2021.33-j721s2 (Terrif')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC2
-----------------ATF Image begin (0x70000000)------------------
f4 03 00 aa f5 03 01 aa f6 03 02 aa f7 03 03 aa
00 06 81 d2 a0 18 a6 f2 00 10 1e d5 df 3f 03 d5
------------------end-------------------

The rproc_start (1) function is executed successfully, but the ATF does not print, and the system is stuck.

Is there any difference between the prebuilt ATF firmware and the ATF source code provided?

Regards,

Li quan

  • 0
    TI__Guru**** 164020 points

    Hi Li quan,

    I will try to replicate this at my end and get back to you in couple of days.

    - Keerthy

  • +1 in reply to Keerthy J
    TI__Guru**** 164020 points

    Hi Li quan,

    I could reproduce the issue at my end. You can build a working ATF Image for TDA4VL By using the documentation in the U-Boot folder of SDK.
    File: board/ti/j721s2/README

    Sources:
    --------
    1. ATF:
    Tree: github.com/.../arm-trusted-firmware.git
    Branch: master

    So clone the above repository.

    Checkout master branch.

    Use the build command that you have used:

    make ARCH=aarch64 CROSS_COMPILE=aarch64-none-linux-gnu- PLAT=k3 TARGET_BOARD=generic SPD=opteed
    I am able to boot to U-boot prompt.

    U-Boot SPL 2021.01 (Jun 13 2022 - 19:37:38 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0016 '22.1.1--v2022.01 (Terrific Llam')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC2
Starting ATF on ARM64 core...


U-Boot SPL 2021.01 (Jun 13 2022 - 20:52:35 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0016 '22.1.1--v2022.01 (Terrific Llam')
Trying to boot from MMC2


U-Boot 2021.01 (Jun 13 2022 - 20:52:35 +0530)

SoC:   J721S2 SR1.0
Model: Texas Instruments J721S2 EVM
ti_i2c_eeprom_am6_parse_record: Ignoring record id 17
ti_i2c_eeprom_am6_parse_record: Ignoring record id 17
Board: J721S2X-PM1-SOM rev E1
DRAM:  16 GiB
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from MMC... OK
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Net:   eth0: ethernet@46000000port@1
Hit any key to stop autoboot:  0
    I believe this unblocks your development.

    Let me know if this helps you.

    Best Regards,
    Keerthy
  • 0 in reply to Keerthy J
    Intellectual 955 points

    Hi Keerthy,

    Thanks, it is ok.

    Best Regards

    Li quan

  • 0 in reply to Keerthy J
    Intellectual 955 points

    Hi Keerthy,

    Now I can boot to U-boot by github.com/.../arm-trusted-firmware.git, but after make clean and recompile or make some changes and recompile the system is stuck again. 

    Best Regards

    Li quan

  • 0 in reply to li quan
    TI__Guru**** 164020 points

    Hi Li quan,

    That depends on the changes you did. Unchanged firmware recompiled failing is something I do not expect.
    Please give details of the steps and what you changed & the logs of failure.

    - Keerthy