Writing uuu zip file with uuu.auto to burn multiple images to i.MX6 NAND

[JohnKlug]

I have four images that I wish to write to a NAND via uuu.

I should think there would be an example somewhere for the MCIMX6ULL-EVK board, since NAND is supported.

Here is the U-Boot string for the NAND:

include/configs/mx6ullevk.h:
#define MFG_NAND_PARTITION "mtdparts=gpmi-nand:64m(nandboot),16m(nandkernel),16m(nanddtb),16m(nandtee),-(nandrootfs)"

The Yocto build created the U-boot, zImage, Device Tree (DTB), and Root UBI or UBIFS images.

So how do I create the zip file and put commands in uuu.auto to write the images automatically?

[igorpadykov]

Hi JohnKlug

such example is provided on

https://wiki.somlabs.com/index.php/How_to_write_image_to_VisionSOM-6ULL_NAND_memory_using_UUU_tool_o...

Also one can look at sample uuu scripts included in Demo Images:

https://www.nxp.com/design/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applicat...

Best regards
igor

[JohnKlug]

The example from visionSOM uses a custom UUU written for their board.  I don't know if source is available:

 -b vsom_6ull_nand_flasher 

So I do not see how visionSOM helps me.

The NXP examples in the download (I downloadedL5.4.47-2.2.0_images_MX6UL7D.zip) do not have any that match the gpmi-weim example that I made.

The only example that seems to be NAND relatated is example_kernel_nand.uuu.  This one uses a initramfs which is not part of the gpmi-weim example that I made.  Do I need to create an initramfs somehow?  So is the initramfs required for this to work?  This example seems to be giving kernel commands that might be intended for the initramfs.

There are duplicate sections in the example.  My understanding would be that the i.MX8 (sdps) could be deleted for i.MX6. But what about SDPU/SDPV?  Do these correspond to U-Boot configuration items?  Where is there detailed documentation on how these are enabled?

What is SPL?  Where does "SPDV: jump" go?

More questions:

FB: acmd ${kboot} ${loadaddr} ${initrd_addr} ${fdt_addr}

What is acmd versus ucmd?  ucmd looks like what follows is a U-Boot command.  It appears that acmd would boot the kernel, since what follows are Linux shell commands.  Does this depend on the initramfs?

Do you really need the kernel to write to the NAND?  I have used the nand command to write to NAND in U-Boot in the past.

[JohnKlug]

I missed maybe another image.  nandtee mentioned in the U-Boot MFG_NAND_PARTITION.

I see two possible candidates:

333212 Dec 23 10:04 tee.mx6ullevk.bin
333276 Dec 23 10:04 uTee-6ullevk

file tee.mx6ullevk.bin
tee.mx6ullevk.bin: data
file uTee-6ullevk
uTee-6ullevk: u-boot legacy uImage, , Linux/ARM, OS Kernel Image (Not compressed), 333212 bytes, Wed Dec 23 16:04:52 2020, Load Address: 0x84000000, Entry Point: 0x84000000, Header CRC: 0xA1F3A823, Data CRC: 0xFA2BC071

So maybe five partitions need to be written?