Yocto build of u-boot-xlnx 2018.3 does not support 'saveenv' command

[jasonhannon]

I have a custom board based on the Zynq 7000 that worked fine under u-boot-xlnx 2016.4 (Krogoth). I'm in the process of porting over to 2018.3 (Thud). I have added the line

"CONFIG_CMD_SAVEENV=y"

to my custom_defcofig file and the line

"#define CONFIG_CMD_SAVEENV"

to my custom.h file.

When I try to execute saveenv at the uboot promt I get "Unrecognized command 'saveenv'.

[stephenm]

The saveenv requires a default storage. Can you pass your defconfig?

[aravindb]

HI @jasonhannon 

Have you corss checked this config enabled or not in .config file after configuring th u-boot .

By default this CMD_SAVEENV support already enabled in xilinx u-boot. No need explicitly enable.

Thanks & regards

Aravind

[jasonhannon]

Yes. 

In checking the .config file I see the following:

CONFIG_CMD_SAVEENV=y

CONFIG_ENV_IS_IN_UBI=y

[stephenm]

Can you enable the debug in the u-boot (add #define debug in <u-boot_HOME>/include/common.h)

recompile, and try again.

[jasonhannon]

It seems that when I have CONFIG_ENV_IS_IN_UBI=y  in my custom_deconfig file U-boot fails on boot giving the following error: No environment driver for location 13.

My current boot architecture uses an SD card with BOOT.bin, uEnv.txt, bootfiles.ubifs, and rootfs.ubifs installed. The sdboot definition in my custom.h file programs NAND with the contents of the SD. This approach worked fine back with the 2016.4 Krogoth u-boot-xlnx. Seems a lot has changed since then and I can't seem to locate any documentation that tells me what particular #define CONFIG_xxxx and/or CONFIG_xxxx=y options I need to have set in either my custom_defconfig and/or custom.h files.

[jasonhannon]

A couple of more points:

1) When I have #define CONFIG_ENV_IS_IN_UBI in my custom.h file only it results in my .config file showing CONFIG_ENV_IS_IN_NOWHERE=y and the saveenv command being not enabled in my uboot build.

2) When I add  CONFIG_ENV_IS_IN_UBI=y in my custom_defconfig file the resulting .config file shows CONFIG_ENV_IS_IN_UBI=y but U-boot fails to boot giving the No environment driver for location 13 error.

What is the difference between having CONFIG_ENV_IS_IN_UBI=y in my custom_defconfig file and #define CONFIG_ENV_IS_IN_UBI in my custom.h file?

[stephenm]

Try CONFIG_ENV_IS_IN_FAT

[jasonhannon · Accepted solution]

I fixed the issue by putting the following after the #include zynq-common.h line in my custom.h file

#undef CONFIG_ENV_IS_NOWHERE