[U-Boot] Possible NAND environment issue which i see on DM355 and DM365

[Paulraj, Sandeep]

Hello,

I see an issue while trying to save the environment on both the DM355 and DM365.

Here is the dump

DM365 EVM # saveenv
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x3e000000040000 --   0% complete.
Writing to Nand... done
DM365 EVM #

If we look at the line, "Erasing at 0x3e000000040000 --   0% complete.",
The diagnostics are clearly wrong. It should be Erasing at 0x3e0000 --  100% complete.

I think this is an issue with the 64 bit support that is getting added to U-Boot. As usual I am willing to get corrected on what I just said.
The image is built of u-boot-ti and since I am in sync with arm , I don't believe I would have seen any NAND and environment related patches/updates over the last month or so.

Any commits/patches that is in u-boot that will result in me not seeing such issues?

I ask because I did not see this issues a couple months ago and the NAND driver is the same so I assume that the issue is with some other subsystem.

I must reiterate that both the DM355 and DM365 boot up a linux kernel just fine.

Thanks,
Sandeep