I have three MTD partitions, the mtd2 storage installed UBIFS volumes,
first is dtb volume, second is kernel volume, third is rootfs volume.
The saveenv was configured to save environment variables to NAND
There was no issue to run NAND boot, but if I called saveenv in
u-boot, then I run bootcmd again, it could not boot from NAND any
Bad Linux ARM zImage magic!
The saveenv does not take any parameters, how did it work to write to
the NAND 1m(ubootenv)?
Saving Environment to NAND... Erasing NAND...
Erasing at 0x5e0000 -- 100% complete.
Writing to NAND... OK
It looks like that saveenv overwritten to the storage, is 0x5e0000 RAM
or NAND address?
Where was that address defined?
How do I know it was the NAND 1m(ubootenv) address?