11 Apr
2022
11 Apr
'22
12:20 a.m.
On 4/10/22 13:54, Felix.Vietmeyer@jila.colorado.edu wrote:
From your description it seems like the board I was working on must have
had an environment on NOR or eMMC which could be loaded but did not allow the board to come up. Then, the patch forces u-boot to use the default environment despite an existing env on NOR or eMMC.
I suspect the board must have some other problem with the environment. I just cannot tell what it is. This is using some downstream U-Boot fork, right ? Can you reproduce the problem in mainline too ? How ?