MFG tool usage for NAND Flash

[kravik]

As per the MFG Tool Documentation, Initially board will boot with uImage_mfg and enumerate as UMS device, then copies all images for NAND to DDR. After copying to DDR it will write all images to NAND Flash.

How MFG Tool will know the NAND partition info? so that it will write all images(U-boot, Dtb, zImage and rootfs) to NAND flash. The .vbs file is mentioning only the partition numbers.

[Yuri]

Hello,

  The MFG loads and run minimal Linux system to memory of a target board.

This system is minimal, but it supports the same, including specific for the board,

features and parameters; in this sense it knows NAND partitioning.

Regards,

Yuri.

[kravik]

MFG tool package is having minimal Linux system images in it.
How this minimal Linux system knows the address and size of NAND in a custom board?
It seems for either NAND or NOR there won't be any partition table on the device, the flash partitions only exist in the MTD sub system.
How the minimal Linux system knows the flash partitions info, so that it can write each image within at specific address for the respective image?
Actual NAND partition info is available in the U-boot(environment variable)/dtb and these U-boot and dtb has to be flashed on the NAND. How MFG tool will get this info?