Enabling saveenv command in u-boot for baltos ir2110
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I am using baltos ir2110. I am compiling u-boot-2017.01 with am335x_baltos_defconfig for u-boot. My problem is that saveenv command is not available with this configuration of u-boot. Is there any specific reason for this? Also how should turn it on ? Recompiling u-boot is not a problem for me but I am not finding the right configuration for enabling saveenv.
I have tried with adding CONFIG_CMD_SAVEENV=y in the configuration file.
Any help would be appreciated!
u-boot
add a comment |Â
up vote
0
down vote
favorite
I am using baltos ir2110. I am compiling u-boot-2017.01 with am335x_baltos_defconfig for u-boot. My problem is that saveenv command is not available with this configuration of u-boot. Is there any specific reason for this? Also how should turn it on ? Recompiling u-boot is not a problem for me but I am not finding the right configuration for enabling saveenv.
I have tried with adding CONFIG_CMD_SAVEENV=y in the configuration file.
Any help would be appreciated!
u-boot
I don't know the hardware. Do you know where the environment is saved? The u-boot needs to know how to write to this storage, which can be tricky for certain hardware.
â Philippos
Nov 6 '17 at 14:24
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using baltos ir2110. I am compiling u-boot-2017.01 with am335x_baltos_defconfig for u-boot. My problem is that saveenv command is not available with this configuration of u-boot. Is there any specific reason for this? Also how should turn it on ? Recompiling u-boot is not a problem for me but I am not finding the right configuration for enabling saveenv.
I have tried with adding CONFIG_CMD_SAVEENV=y in the configuration file.
Any help would be appreciated!
u-boot
I am using baltos ir2110. I am compiling u-boot-2017.01 with am335x_baltos_defconfig for u-boot. My problem is that saveenv command is not available with this configuration of u-boot. Is there any specific reason for this? Also how should turn it on ? Recompiling u-boot is not a problem for me but I am not finding the right configuration for enabling saveenv.
I have tried with adding CONFIG_CMD_SAVEENV=y in the configuration file.
Any help would be appreciated!
u-boot
asked Nov 6 '17 at 12:34
Aditya Purohit
111
111
I don't know the hardware. Do you know where the environment is saved? The u-boot needs to know how to write to this storage, which can be tricky for certain hardware.
â Philippos
Nov 6 '17 at 14:24
add a comment |Â
I don't know the hardware. Do you know where the environment is saved? The u-boot needs to know how to write to this storage, which can be tricky for certain hardware.
â Philippos
Nov 6 '17 at 14:24
I don't know the hardware. Do you know where the environment is saved? The u-boot needs to know how to write to this storage, which can be tricky for certain hardware.
â Philippos
Nov 6 '17 at 14:24
I don't know the hardware. Do you know where the environment is saved? The u-boot needs to know how to write to this storage, which can be tricky for certain hardware.
â Philippos
Nov 6 '17 at 14:24
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
The problem was with the version of u-boot. The u-boot-2017-01 version does not support environment macros configuration from the configuration file. This has to be done in the header file for the specific board, baltos.h in my case.
The following addition in baltos.h made it work:
#define CONFIG_ENV_SIZE (128 << 10)
#define CONFIG_ENV_IS_IN_FAT
#define FAT_ENV_INTERFACE "mmc"
#define FAT_ENV_DEVICE_AND_PART "0.0"
#define FAT_ENV_FILE "uboot.env"
/*#define CONFIG_ENV_IS_NOWHERE*/
The newer versions of u-boot support configuring the environment from a config file.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The problem was with the version of u-boot. The u-boot-2017-01 version does not support environment macros configuration from the configuration file. This has to be done in the header file for the specific board, baltos.h in my case.
The following addition in baltos.h made it work:
#define CONFIG_ENV_SIZE (128 << 10)
#define CONFIG_ENV_IS_IN_FAT
#define FAT_ENV_INTERFACE "mmc"
#define FAT_ENV_DEVICE_AND_PART "0.0"
#define FAT_ENV_FILE "uboot.env"
/*#define CONFIG_ENV_IS_NOWHERE*/
The newer versions of u-boot support configuring the environment from a config file.
add a comment |Â
up vote
1
down vote
The problem was with the version of u-boot. The u-boot-2017-01 version does not support environment macros configuration from the configuration file. This has to be done in the header file for the specific board, baltos.h in my case.
The following addition in baltos.h made it work:
#define CONFIG_ENV_SIZE (128 << 10)
#define CONFIG_ENV_IS_IN_FAT
#define FAT_ENV_INTERFACE "mmc"
#define FAT_ENV_DEVICE_AND_PART "0.0"
#define FAT_ENV_FILE "uboot.env"
/*#define CONFIG_ENV_IS_NOWHERE*/
The newer versions of u-boot support configuring the environment from a config file.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
The problem was with the version of u-boot. The u-boot-2017-01 version does not support environment macros configuration from the configuration file. This has to be done in the header file for the specific board, baltos.h in my case.
The following addition in baltos.h made it work:
#define CONFIG_ENV_SIZE (128 << 10)
#define CONFIG_ENV_IS_IN_FAT
#define FAT_ENV_INTERFACE "mmc"
#define FAT_ENV_DEVICE_AND_PART "0.0"
#define FAT_ENV_FILE "uboot.env"
/*#define CONFIG_ENV_IS_NOWHERE*/
The newer versions of u-boot support configuring the environment from a config file.
The problem was with the version of u-boot. The u-boot-2017-01 version does not support environment macros configuration from the configuration file. This has to be done in the header file for the specific board, baltos.h in my case.
The following addition in baltos.h made it work:
#define CONFIG_ENV_SIZE (128 << 10)
#define CONFIG_ENV_IS_IN_FAT
#define FAT_ENV_INTERFACE "mmc"
#define FAT_ENV_DEVICE_AND_PART "0.0"
#define FAT_ENV_FILE "uboot.env"
/*#define CONFIG_ENV_IS_NOWHERE*/
The newer versions of u-boot support configuring the environment from a config file.
edited Nov 12 '17 at 14:44
Jeff Schaller
32k849109
32k849109
answered Nov 8 '17 at 5:27
Aditya Purohit
111
111
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402823%2fenabling-saveenv-command-in-u-boot-for-baltos-ir2110%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I don't know the hardware. Do you know where the environment is saved? The u-boot needs to know how to write to this storage, which can be tricky for certain hardware.
â Philippos
Nov 6 '17 at 14:24