nxp-imx / imx-kobs

Tool to create and write Freescale/NXP I.MX NAND boot related boot data structure to nand flash
GNU General Public License v2.0
29 stars 26 forks source link

imx8dxp with Nand Flash kobs-ng writing two boot streams #22

Open vmuthusu opened 5 years ago

vmuthusu commented 5 years ago

Hi We are using a custom board based on imx8dxp with Nand Flash. we have created a binary using the mkimage_imx8 with (SECO,SCFW,U-Boot and M4 binary). When we flash this binary using the uuu tool and the command FBK: ucmd kobs-ng init -v --chip_0_device_path=/dev/mtd0 /tmp/flash.bin the mtd0 partition size is 0x00500000 (5MB) the kobs-ng is writing the same binary into two locations. Output of kobs-ng for your reference. Firmware: image #0 @ 0x80000 size 0xe5000 - available 0x240000 Firmware: image #1 @ 0x2c0000 size 0xe5000 - available 0x240000. can you please let us know why kobs-ng is writing it twice?

For iMX8 we have the Primary and Seconday Image container sets to boot. The above flash.bin corresponds to one Image container set which comes immediately after the FCB and DBBT. For this single image container set itself kobs-ng duplicates the binary. So if we flash the other image container set using kobs-ng it will also duplicate the binary. Do we really need to have the kobs-ng flashing the binary in 2 different locations for iMX8 based processors? Is it possible to configure this some way?

Thanks V.Muthusubramanian