uuu with custom script quits after "SDPV: jump" if "bootcmd_mfg" is in boards environment

[flobro]

iMX8QM processor

I am running uuu with the following:

uuu_version 1.2.39

# @_flash.bin | bootloader
# @_kernel
# @_devtree
SDPS[-t 10000]: boot -f _flash.bin
SDPV: delay 1000
SDPV: write -f _flash.bin -skipspl
SDPV: jump
FB: ucmd setenv fdt_addr_r 0x84000000
FB: ucmd setenv fdt_addr 0x84000000
FB: ucmd setenv fastboot_buffer ${fdt_addr}
FB: download -f _devtree
FB: ucmd setenv loadaddr 0x80280000
FB: ucmd setenv fastboot_buffer ${loadaddr}
FB: download -f _kernel
FB: ucmd setenv bootargs console=ttyLP0,115200 earlycon mode=dev2 seth2 rdinit=/linuxrc-dev init_fatal_sh
FB: acmd booti ${loadaddr} - ${fdt_addr}
FB: done

If the board has a previous install and the UBOOT environment has "bootcmd_mfg" defined, the script quits after the "SDPV: jump", and the board starts booting from the saved environment on the board.

If I delete the "bootcmd_mfg" from the env stored on the eMMC, the uuu script works fine.

I have not seen that behavior on my imx8MP setup, and I cannot find any reference to bootcmd_mfg in the uuu source anywhere.

I realize I can make sure I do not use that particular env variable, but I am looking for the reason why this happens.

[flobro]

Thank you for the response - but... The fact that it "does" work without the bootcmd_mfg environment variable set shows that it does work correctly. It is the newest version (1.5.182) and it supports the iMX8QM perfectly fine, but with the one weirdness.

Any one know why a "bootcmd_mfg" env variable would be causing any behavior to stop following the script? 

[JosephAtNXP]

Hi @flobro,

Could you share the output of your script ran with the -v option, please?

Regards,

[flobro]

What I have realized is that a SOM already loaded and functioning that I try to use SDP on, after the first four commands:

DPS[-t 10000]: boot -f _flash.bin
SDPV: delay 1000
SDPV: write -f _flash.bin -skipspl
SDPV: jump

The bootloader takes off using what is stored in the already programmed environment (bootcmd). I cannot send any other commands from the serial loader...

I must go in and wipe the existing environment out before I can use SDP on the board, rendering SDP useless otherwise.

This only appears to happen on the imx8QM, and NOT on my imx8MP boards.

[flobro]

Run built-in script:
uuu_version 1.2.39

# @_flash.bin | bootloader
# @_kernel
# @_devtree
SDPS[-t 10000]: boot -f ./mount/flash.bin
SDPV: delay 1000
SDPV: write -f ./mount/flash.bin -skipspl
SDPV: jump
FB: ucmd setenv fdt_addr_r 0x84000000
FB: ucmd setenv fdt_addr 0x84000000
FB: ucmd setenv fastboot_buffer ${fdt_addr}
FB: download -f ./mount/seth.dtb
FB: ucmd setenv loadaddr 0x80280000
FB: ucmd setenv fastboot_buffer ${loadaddr}
FB: download -f ./mount/Image
FB: ucmd setenv bootargs console=ttyLP0,115200 earlycon mode=dev2 seth2 rdinit=/linuxrc-dev init_fatal_sh
FB: acmd booti ${loadaddr} - ${fdt_addr}
FB: done

Wait for Known USB Device Appear...
New USB Device Attached at 1:612-0F0651AAC6536973
1:612-0F0651AAC6536973>Start Cmd:SDPS[-t 10000]: boot -f ./mount/flash.bin
100%1:612-0F0651AAC6536973>Okay (0.947s)
New USB Device Attached at 1:612-
1:612->Start Cmd:SDPV: delay 1000
1:612->Okay (1s)
1:612->Start Cmd:SDPV: write -f ./mount/flash.bin -skipspl
100%1:612->Okay (0.876s)
1:612->Start Cmd:SDPV: jump
100%1:612->Okay (0.5s)

Stops after "SDPV:Jump" ONLY if the onboard environment variable "bootcmd_mfg" is present. Otherwise it works perfectly.

[JosephAtNXP]

Hi,

Thank you for your interest in NXP Semiconductor products,

You would need to check that you are using latest uuu release, with the correctly ported u-boot. The cause of FB commands not being issued is that the fastboot device is not found, probably because of using a different USB IF or missing the SW configuration in U-Boot source.

Regards