Jump to content

U-Boot saveenv issue


BreadLee

Recommended Posts

Hi,

 

I built a fresh Armbian Image from scratch (using Armbian build system). After that I used Etcher to burn .img file to SD card. Everything works great, but U-Boot shows, that there is no environment. I used saveenv and fixed a problem. Then I installed Armbian into internal memory (eMMC), same message about environment, I tried fix it same way, using saveenv, but I get only  an error message and infinite loop. Screenshot attached. How I can fix that?

 

13.png

 

UPD: My board - Orange Pi Zero Plus 2

 

Kind regards

Link to comment
Share on other sites

41 minutes ago, BreadLee said:

I built a fresh Armbian Image from scratch

 

... which uses new u-boot 2018.06 where boot environment is/must be saved to a file system. I think the location of env file is hard encoded ... well, you find a bug.

 

If you have time, check if https://github.com/armbian/build/blob/master/lib/compilation.sh#L157 changing to 

CONFIG_ENV_EXT4_DEVICE_AND_PART="auto:auto"

helps.

Link to comment
Share on other sites

1 hour ago, Igor said:

 

... which uses new u-boot 2018.06 where boot environment is/must be saved to a file system. I think the location of env file is hard encoded ... well, you find a bug.

 

If you have time, check if https://github.com/armbian/build/blob/master/lib/compilation.sh#L157 changing to 


CONFIG_ENV_EXT4_DEVICE_AND_PART="auto:auto"

helps.

Igor, thank you for your reply. 

I will check it right now.

Link to comment
Share on other sites

2 hours ago, Igor said:

If you have time, check if https://github.com/armbian/build/blob/master/lib/compilation.sh#L157 changing to 


CONFIG_ENV_EXT4_DEVICE_AND_PART="auto:auto"

helps.

Igor, I tried to do that, but currently it shows me an error with SD card also. 

13.png

I will try to move it on to eMMC, but it will not work, in my opinion.

 

Update:

Same with eMMC

13.png.1ad899bc616a45e4e6c7e0285fb1dc27.png

Link to comment
Share on other sites

4 hours ago, Igor said:

CONFIG_ENV_EXT4_DEVICE_AND_PART="auto:auto"

 

"auto" is not implemented for the device identifier, only for the partition number.

Though in theory it is possible to use (sunxi specific) boot device ID from the SPL header, but unless someone writes and tests this we are stuck with fixed device IDs.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines