Hi TI
There's an issue from eMMC booting after dfu-util download.
After updating firmware binaries including rootfs, the eMMC booting can not be succedded with following logs.
When we check mmc part, user partition has been deleted.
Could you please check the procudure introduced in spracy5.pdf is correct?
We followed the the following steps to update firmware usinf dfu-util.
# This will download the images to the board but not flash them to eMMC
# These first set of steps are optional if you have u-boot running on the board already
HOST $ sudo dfu-util -l
HOST $ sudo dfu-util -R -a bootloader -D <PATH_TO_BIN>/tiboot3.bin
HOST $ sudo dfu-util -R -a sysfw.itb -D <PATH_TO_BIN>/sysfw.itb
HOST $ sudo dfu-util -R -a tispl.bin -D <PATH_TO_BIN>/tispl.bin
HOST $ sudo dfu-util -R -a u-boot.img -D <PATH_TO_BIN>/u-boot.img
# At this point, the u-boot will start executing. Halt at the u-boot prompt (u-boot logs will
appear on the MAIN UART 1st instance)
TARGET => env default -f -a
TARGET => setenv mmcdev 0
TARGET => setenv bootpart 0
TARGET => saveenv
TARGET => setenv dfu_alt_info ${dfu_alt_info_emmc}
# one time only per board
TARGET => gpt write mmc 0 ${partitions}
TARGET => dfu 0 mmc 0
# This does the actual flashing to the eMMC boot0 partition
HOST $ sudo dfu-util -l
HOST $ sudo dfu-util -a tiboot3.bin.raw -D <PATH_TO_BIN>/tiboot3.bin
HOST $ sudo dfu-util -a tispl.bin.raw -D <PATH_TO_BIN>/tispl.bin
HOST $ sudo dfu-util -a u-boot.img.raw -D <PATH_TO_BIN>/u-boot.img
HOST $ sudo dfu-util -a sysfw.itb.raw -D <PATH_TO_BIN>/sysfw.itb
# Flashing a tiny file system to eMMC User partition
HOST $ sudo dfu-util -a rootfs -D <PATH_TO_CREATED_TINYFS>/tinyrootfs.img
#one time only per board, to give ROM access to the boot partition, the following commands must
be used for the first time
TARGET => mmc partconf 0 1 1 1
U-Boot SPL 2020.01-dirty (Jul 27 2021 - 01:45:40 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
33333 do_board_detect
4444 do_board_detect()Trying to boot from MMC1
Loading Environment from MMC... *** Warning - bad CRC, using default environment
init_env from device 17 not supported!
Starting ATF on ARM64 core...
NOTICE: BL31: v2.4(release):07.03.00.005-dirty
NOTICE: BL31: Built : 13:45:56, Apr 10 2021
U-Boot SPL 2020.01-dirty (Jul 27 2021 - 01:44:44 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
33333 do_board_detect
4444 do_board_detect()Trying to boot from MMC1
U-Boot 2020.01-dirty (Jul 27 2021 - 22:55:07 -0700)
SoC: J7200 SR1.0
Model: Texas Instruments K3 J7200 SoC
ti_i2c_eeprom_am6_parse_record: Ignoring record id 17
Board: J7200X-PM2-SOM rev E6
DRAM: 4 GiB
not found for dev hbmc-mux
Flash: 64 MiB
MMC: sdhci@4f80000: 0, sdhci@4fb0000: 1
Loading Environment from MMC... OK
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Detected: J7X-BASE-CPB rev E3
Detected: J7X-GESI-EXP rev E3
Detected: J7X-VSC8514-ETH rev E2
Net: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Warning: ethernet@46000000 using MAC address from ROM
eth0: ethernet@46000000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0(part 0) is current device
SD/MMC found on device 0
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid GPT ***
find_valid_gpt: *** Using Backup GPT ***
** Unrecognized filesystem type **
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid GPT ***
find_valid_gpt: *** Using Backup GPT ***
** Unrecognized filesystem type **
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid GPT ***
find_valid_gpt: *** Using Backup GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_val
Thanks.
Regards,
Jack Cha
