Hi tom
The warning message possible cause by the environment not set.
This warning is displayed when you try to access an uninitialized on-disk u-boot environment.
If you have serial access you may just interrupt the boot process by typing CR and then:
saveenv
reset
https://github.com/umiddelb/armhf/issues/22
When the system is flashed, the region of eMMC that could/does hold the U-Boot environment is not written. This is why U-Boot prints “Warning: Bad CRC, using default environment”. Because of this, U-Boot uses a default environment that’s built into the U-Boot binary. This will also cause fw_printenv to fail to read the environment from eMMC, since there is none stored there.
If you want to write the environment to eMMC, you can:
a) Power on/reboot the system
b) Wait for U-Boot to run
c) Interrupt the U-Boot boot process
d) In U-Boot, run “env default -f -a; saveenv”
After that, the environment will be saved in eMMC, so (a) U-Boot will read the environment from eMMC when booting instead of using its built-in default copy (b) fw_printenv should be able to read the environment from eMMC.
First of all, thanks for you replies. Here is what I found out based on your responses:
“env default -f -a; saveenv” did not change or do anything on my TX2, but “saveenv;reset” gets rid of Bad-CRC error message when printing env variables. If I want to set a variable to something else like so:
“sudo fw_printenv bootdelay 0”, it comes back with “bootdelay=2 ## Error: “0” not defined”.
That command is incorrect, Do you want to change the value you need? Than you need use fw_setenv instead of fw_printenv. Also you need to below link to enable the write permission.
I think you solved my problem. After renaming fw_printenv to fw_setenv, everything seems to work. I did not even have to go into UBoot shell to run those 2 commands you gave me after reflashing. I did not think renaming or copying fw_printenv to fw_setenv would make a difference but it does.