PROCESSOR-SDK-J721E: u-boot instructions for programming eMMC using USB-DFU

Hi Diwakar,

My h/w only has USB, UART and eMMC ports attached (MMC0).  There is no SD card.  Therefore I need to use DFU-USB to program to the eMMC.

I followed instructions in section 5.3.1 of SPRACY5.  I got here:

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

TARGET => env default -f -a
TARGET => setenv mmcdev 0
TARGET => setenv bootpart 0
TARGET => saveenv
TARGET Saving Environment to FAT... Failed (1)

I believe the eMMC boot partition is RAW rather than FAT?

=> dfu 0 mmc 0 list
DFU alt settings list:
dev: eMMC alt: 0 name: rawemmc layout: RAW_ADDR
dev: eMMC alt: 1 name: rootfs layout: RAW_ADDR
dev: eMMC alt: 2 name: tiboot3.bin.raw layout: RAW_ADDR
dev: eMMC alt: 3 name: tispl.bin.raw layout: RAW_ADDR
dev: eMMC alt: 4 name: u-boot.img.raw layout: RAW_ADDR
dev: eMMC alt: 5 name: u-env.raw layout: RAW_ADDR
dev: eMMC alt: 6 name: sysfw.itb.raw layout: RAW_ADDR

thanks!

Hi Diwakar

I have been able to get all the way to writing the boot files to the eMMC using dfu-util.  However when the boot mode is changed to eMMC nothing happens.

I have tried the same procedure/files on my custom h/w and the EVM with no joy.

The procedure is the same as in section 5.3.1 of SPRACY5.

env default -f -a
setenv mmcdev 0
setenv bootpart 0
saveenv
setenv dfu_alt_info ${dfu_alt_info_emmc}
gpt write mmc 0 ${partitions}
mmc partconf 0 1 1 1
mmc bootbus 0 2 0 0
mmc dev 0 0
dfu 0 mmc 0

[HOST] dfu-util -a bootloader -D tiboot3.bin
[HOST] dfu-util -a tispl.bin -D tispl.bin
[HOST] dfu-util -a u-boot.img -D u-boot.img
[HOST] dfu-util -a sysfw.itb -D sysfw.itb

I have changed the config files in the bootloader like so:

k3_dfu.h

/* ASI modified to fit in a 4MB (0x2000 blocks) eMMC boot partition*/
#define DFU_ALT_INFO_EMMC \
	"dfu_alt_info_emmc=" \
	"rawemmc raw 0 0x400000 mmcpart 1;" \
	"rootfs part 0 1 mmcpart 0;" \
	"tiboot3.bin.raw raw 0x0 0x400 mmcpart 1;" \
	"tispl.bin.raw raw 0x400 0xB00 mmcpart 1;" \
	"u-boot.img.raw raw 0xF00 0xD00 mmcpart 1;" \
	"u-env.raw raw 0x1C00 0x100 mmcpart 1;" \
	"sysfw.itb.raw raw 0x1D00 0x300 mmcpart 1\0"

j721e_evm_a72_defconfig

CONFIG_ENV_IS_IN_MMC=y
CONFIG_SYS_REDUNDAND_ENVIRONMENT=y
CONFIG_SYS_RELOC_GD_ENV_ADDR=y
CONFIG_SYS_MMC_ENV_PART=1
# CONFIG_ENV_IS_IN_FAT is not set by AudioScience
# CONFIG_ENV_FAT_DEVICE_AND_PART="1:1" is not set by AudioScience
CONFIG_SPL_ENV_IS_NOWHERE=y
#!!!!!!!!!!!!!! not clear if this is needed !!!!!!!!!!!!!!
# set by AudioScience according to emmc values in DFU_ALT_INFO_EMMC
#CONFIG_ENV_SIZE=0x20000 is not set by AudioScience
CONFIG_ENV_OFFSET=0x380000
CONFIG_ENV_OFFSET_REDUND=0x380100

Any ideas?

Hi Diwakar,

I followed your instructions exactly and was able to generate files that would boot from the EVM eMMC.  

I then modified our custom h/w to use a 19.2MHz Oscillator thus allowing me to use the same tiboot3.bin as the EVM.

Our h/w uses a 4GB eMMC with a 4MB boot partition vs. the EVM's 16GB eMMC and what looks like a 32MB partition.

I had to modify k3_dfu.h to allow everything to fit inside 4MB:

/* ASI modified to fit in a 4MB (0x2000 blocks) eMMC boot partition*/
#define DFU_ALT_INFO_EMMC \
	"dfu_alt_info_emmc=" \
	"rawemmc raw 0 0x400000 mmcpart 1;" \
	"rootfs part 0 1 mmcpart 0;" \
	"tiboot3.bin.raw raw 0x0 0x400 mmcpart 1;" \
	"tispl.bin.raw raw 0x400 0xB00 mmcpart 1;" \
	"u-boot.img.raw raw 0xF00 0xD00 mmcpart 1;" \
	"u-env.raw raw 0x1C00 0x100 mmcpart 1;" \
	"sysfw.itb.raw raw 0x1D00 0x300 mmcpart 1\0"

I also had to remove this CONFIG in j721e_evm_a72_defconfig otherwise u-boot would crash when loading on my h/w during the DFU-USB phase

# CONFIG_DM_PCA953X is not set by AudioScience

This resulting set of boot files almost gets to a u-boot prompt on the EVM, but not quite....

U-Boot SPL 2021.01-dirty (Feb 24 2023 - 22:59:43 +0000)
Model: Texas Instruments K3 J721E SoC
Board:  rev
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.2--v08.05.02 (Chill Capybar')
Trying to boot from MMC1
init_env from device 17 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.7(release):v2.7.0-359-g1309c6c805-dirty
NOTICE:  BL31: Built : 07:46:16, Dec 18 2022
I/TC:
I/TC: OP-TEE version: 3.19.0 (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 Sun Dec 18 07:46:21 UTC 2022 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: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.2--v08.05.02 (Chill Capybar')
I/TC: HUK Initialized
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: Primary CPU switching to normal world boot

U-Boot SPL 2021.01-dirty (Feb 24 2023 - 22:59:39 +0000)
Model: Texas Instruments K3 J721E SoC
Board:  rev
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.2--v08.05.02 (Chill Capybar')
ti_i2c_eeprom_am6_get: Ignoring record id 255
Trying to boot from MMC1
<crash>

These same binaries do not seem to work on our h/w when booting from eMMC.  I see no output on the UART at all.

Any ideas?.

thanks

That works!.  Thanks for your help.

Would be nice to have all these change documented in a readme somewhere.