Help me understand the detail of uuu protocol

[cnspring2002]

I want you to help me to understand the uuu script, thanks.

Q1:
SDP: boot -f flash.bin

This download flash.bin to OCRAM? Will it run the flash.bin in ocram? Or it only download SPL to ocram?

Q2:
SDPU: delay 1000
SDPU: write -f flash.bin -offset 0x57c00
SDPU: jump

What does this do? Write again the flash.bin to ram?

Q3:
SDP: dcd -f flash.bin
SDP: write -f flash.bin -ivt 0
SDP: jump -f flash.bin -ivt 0

I know this 3 commands is the detail steps of Q1, could you explain it to me?

[cnspring2002]

Thanks @AldoG 

But for imx8mp, I use next only:

SDPS: boot -f >/work/imx-boot-imx8mpevk-sd.bin-flash_evk

I find it will directly start SPL and then uboot, no need to to do "SDPV: write -f >/tftpboot/work/imx-boot-imx8mpevk-sd.bin-flash_evk -skipspl", the command if in uuu.auto, will be skipped as it directly go to FB state

So, looks

1) For imx8mp, SDPS: boot flash.bin will start SPL, and also uboot, "SPDV" skipped

2) For imx95, SDPS: boot flash.bin only start SPL, and then "SDPV: write -f flash.bin; SDPV: jump" will start uboot

What's the difference? I think both flash.bin for imx8mp and imx95 has SPL

Next is the log for imx8mp, if I only do "SDPS: boot -f >/work/imx-boot-imx8mpevk-sd.bin-flash_evk":

U-Boot SPL 2024.04-lf_v2024.04+g6dd466b4be5+p0 (Jan 20 2025 - 01:22:52 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0: RNG instantiated
Normal Boot
Trying to boot from BOOTROM
Boot Stage: USB boot
Find img info 0x48022fa0, size 1064
Need continue download 1024
NOTICE: Do not release JR0 to NS as it can be used by HAB
NOTICE: BL31: v2.10.0 (release):android-15.0.0_1.0.0-rc3-6-g5ee49dd5e
NOTICE: BL31: Built : 05:48:54, Dec 25 2024

U-Boot 2024.04-lf_v2024.04+g6dd466b4be5+p0 (Jan 20 2025 - 01:22:52 +0000)

CPU: i.MX8MP[8] rev1.1 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 29C
Reset cause: POR
Model: NXP i.MX8MPlus LPDDR4 EVK board
DRAM: 6 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C2 0x50]
SNK.Power3.0 on CC2
tcpc_pd_receive_message: Polling ALERT register, TCPC_ALERT_RX_STATUS bit failed, ret = -62
Power supply on USB2
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
Core: 288 devices, 37 uclasses, devicetree: separate
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from nowhere... OK
[*]-Video Link 0adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19

[0] lcd-controller@32e80000, video
[1] mipi_dsi@32e60000, video_bridge
[2] adv7535@3d, panel
adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19
In: serial
Out: serial
Err: serial
SEC0: RNG instantiated
switch to partitions #0, OK
mmc1 is current device
Detect USB boot. Will enter fastboot mode!
Net:
Warning: ethernet@30bf0000 (eth1) using random MAC address - 12:2b:43:8d:fd:cc

Warning: ethernet@30be0000 (eth0) using random MAC address - d2:09:b9:7e:b5:39
eth0: ethernet@30be0000, eth1: ethernet@30bf0000 [PRIME]
Fastboot: Normal
Boot from USB for mfgtools
*** Warning - Use default environment for mfgtools
, using default environment

Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; fi;
Hit any key to stop autoboot: 0

## Checking Image at 43800000 ...
Unknown image format!
Run fastboot ...

[AldoG]

Hello,

Are you using prebuilt images or you have built your own images?

Best regards/Saludos,
Aldo.

[AldoG]

Hello, 

A1> It does all 3, please note that flash.bin does include spl in some cases.

A2> This one is in case there is spl, so it will load uboot to its load address

A3> Run DCD from image with ivt header:
dcd -f <file name>

write image to address.:
write -f <file name> [-addr 0x000000] [-ivt 0]
ivt 0 means write to the address, which ivt pointer

jump to image with ivt header:
jump -f <file name> [-ivt 0]

Best regards/Saludos,
Aldo.