• State
  • Locked Locked
  • Replies 15 replies
  • Subscribers 101 subscribers
  • Views 338 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.

On my custom device, the tiboot3.bin generated using Yocto with SDK version 10.01.00.04 encounters an error that prevents it from being flashed properly

? ??
Prodigy 10 points
Part Number: TDA4VM

Tool/software:

On my custom board, the tiboot3.bin generated using Yocto with SDK version 10.01.00.04 encounters an error that prevents normal flashing. The steps are as follows:

First, flash tiboot3.bin

After flashing tiboot3.bin, an error occurred when flashing sysfw.itb

At this point, it should have appeared, but the dfu device is no longer available.

I have confirmed that my custom device can be flashed with the ti-processor-sdk-linux-j7-evm-08_06_00_11 version of the SDK. However, now that I have upgraded to 10_01_00_04, it cannot be flashed properly. I have ensured that there have been no modifications to my hardware before and after the upgrade.

When tda4vm fails at 10_01_00_04, a prompt appears on the serial port terminal：

When tda4vm fails on 08_06-00_11, the serial port terminal displays a prompt::

My hardware did not change during this process, it was all flashed to EMMC through DFU.

Can I use the 08_06-00_11 version of Yocto to flash and write normally? Is there any change in the new version of tiboot3.bin.Can the official help me investigate? Thank you very much

  • 0
    Prodigy 10 points

    I made a mistake in saying something above:
    When tda4vm succeeds on 08_06-00_11, the serial port terminal displays a prompt:

  • 0 in reply to ? ??
    TI__Genius 17215 points

    Hi,

    I have assigned your question to the relevant expert.

    Best,
    Jared

  • 0 in reply to Jared McArthur
    TI__Genius 11050 points

    Hi,

    Can you provide the sizes of the boot files used(ie:tiboot3.bin,sysfw.itb,tispl.bin,u-boot.img).

    Regards

    Gokul

  • 0 in reply to ? ??
    TI__Genius 11050 points

    Hi ,

    I tested the same on SDK VERSION 10.01.00.04 and it is working fine on our TI EVM.

    Target board logs:

    Welcome to minicom 2.8

OPTIONS: I18n 
Port /dev/ttyUSB0, 16:11:12

Press CTRL-A Z for help on special keys


U-Boot SPL 2024.04-ti-ga970f6e51043 (Nov 13 2024 - 14:26:23 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
Trying to boot from DFU
######################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
init_env from device 18 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.11.0(release):v2.11.0-906-g58b25570c9-dirty
NOTICE:  BL31: Built : 04:20:32, Nov  1 2024
I/TC: 
I/TC: OP-TEE version: 4.4.0-dev (gcc version 13.3.0 (GCC)) #1 Fri Oct 18 17:45:27 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
I/TC: SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: HUK Initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2024.04-ti-ga970f6e51043 (Nov 13 2024 - 14:26:23 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
Detected: J7X-BASE-CPB rev A
Trying to boot from DFU
cdns-usb3-peripheral usb@6000000: DRD version v1 (ID: 0004024e, rev: 00000200)
cdns-usb3-peripheral usb@6000000: Initialized  ep0 support:  
cdns-usb3-peripheral usb@6000000: Initialized  ep1out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep2out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep3out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep4out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep5out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep6out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep7out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep8out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep9out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep10out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep11out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep12out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep13out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep14out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep15out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep1in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep2in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep3in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep4in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep5in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep6in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep7in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep8in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep9in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep10in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep11in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep12in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep13in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep14in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep15in support: BULK, INT ISO
##########DOWNLOAD ... OK
Ctrl+C to exit ...
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted


U-Boot 2024.04-ti-ga970f6e51043 (Nov 13 2024 - 14:26:23 +0000)

SoC:   J721E SR1.0 GP
Model: Texas Instruments J721e EVM
Board: J721EX-PM2-SOM rev E6
DRAM:  2 GiB (effective 4 GiB)
Core:  144 devices, 35 uclasses, devicetree: separate
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA00101 cpsw_ver: 0x6BA80100 ale_ver: 0x00293904 Ports:1
Detected: J7X-BASE-CPB rev A
cdns,sierra serdes@5000000: sierra probed
Net:   eth0: ethernet@46000000port@1
Hit any key to stop autoboot:  0 
=> 
=>

    Just a couple of questions to ask:

    • The prebuilt-images in the SDK has a the following sizes:
      • 1090079 bytes : tispl.bin
      • 1296715 bytes : u-boot.img 

    • However, the file sizes of the above 2 files seems to be different in your case.So have you modified those files ? 
      • If yes,it is most probable that those modifications could be causing the issue as we are not facing any issue on the TI EVM when booting using DFU.

    Regards

    Gokul

  • 0 in reply to Gokul Praveen
    Prodigy 10 points

    I have a question about the file boot-adas-j721e-evm.tar.gz in your download center. Has it been modified in any way?

  • 0 in reply to ? ??
    TI__Genius 11050 points

    HI,

    ? ?? said:
    Has it been modified in any way?

    Can you provide more clarity on this?

    Regards

    Gokul

  • 0 in reply to Gokul Praveen
    Prodigy 10 points

    hello
    1. What I mean is that I want to know if you can provide me with a successfully flash tiboot3.bin, sysfw.itb, tispl.bin, u-boot.img that you have used.
    2. Is boot-adas-j721e-evm.tar.gz what you use? Whether it is a pure default configuration.

  • 0 in reply to Gokul Praveen
    Prodigy 10 points

    hello
    There is another problem I found
    09.02.00.05
    09.01.00.06
    09.00.01.03
    09.00.00.08
    The above versions can be written sysfw.itb tiboot3.bin tispl.bin u-boot.img normally. It started to fail in the 10_01 version

  • 0 in reply to ? ??
    TI__Genius 11050 points

    HI,

    ? ?? said:
    2. Is boot-adas-j721e-evm.tar.gz what you use? Whether it is a pure default configuration.

    Yes this is what I have used. You have to use the the files with the following names after downloading and extracting that tar file:

    • tiboot3.bin
    • sysfw.itb
    • tispl.bin
    • u-boot.img
    ? ?? said:
    09.02.00.05

    Can you continue with this version then since it is the latest working version.

    Regards

    Gokul

  • 0 in reply to Gokul Praveen
    Prodigy 10 points

    hello

    At present, we need the 10.01 version. At present, I want to know what problems may be caused and solve them. Your help is very important to us


  • 0 in reply to ? ??
    TI__Genius 11050 points

    Hi,

    Are you trying with default boot files in the working SDK cases or have you made any software changes?

    Regards

    Gokul

  • 0 in reply to Gokul Praveen
    Prodigy 10 points

    I tried to generate sysfw.itb tiboot3.bin tispl.bin u-boot.img on 09.02.00.05-sdk. I found that compared with the 10.01 version, sysfw.itb tiboot3.bin tispl.bin u-boot.img can be flash through the dfu normally.

  • 0 in reply to Gokul Praveen
    Prodigy 10 points

    However, on 09.02.00.05-sdk, after I wrote rootfs, I could only start it once normally and could not start it normally later. I'm a little doubtful whether there is a problem of memory coverage

  • 0 in reply to ? ??
    TI__Genius 11050 points

    HI,

    ? ?? said:
    I tried to generate sysfw.itb tiboot3.bin tispl.bin u-boot.img on 09.02.00.05-sdk. I found that compared with the 10.01 version, sysfw.itb tiboot3.bin tispl.bin u-boot.img can be flash through the dfu normally

    Can you provide the code changes that you have made to the boot files on the 09.02.00.05 and 10.01 SDK, so that we can review and identify the issue as it is working on our end with the files in boot-adas-j721e-evm.tar.gz .

    Regards

    Gokul