Add the information for the save_uenv command and refactor the documentation to remove the eMMC information that was wrong.
Signed-off-by: Manorit Chawdhry m-chawdhry@ti.com --- doc/board/ti/k3.rst | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/doc/board/ti/k3.rst b/doc/board/ti/k3.rst index 7dfe39c5fa57..e95779e32566 100644 --- a/doc/board/ti/k3.rst +++ b/doc/board/ti/k3.rst @@ -594,20 +594,21 @@ Refer (:ref:`U-boot ARMV8 build <k3_rst_include_start_build_steps_uboot>`) Saving environment ------------------
-SAVEENV is disabled by default and for the new flow uses Uenv.txt as the default -way for saving the environments. This has been done as Uenv.txt is more granular -then the saveenv command and can be used across various bootmodes too. +CONFIG_CMD_SAVEENV is disabled by default and for the new flow uses +uEnv.txt as the default way for saving the environments. This has been done +as uEnv.txt is more granular then the saveenv command and can be used +across various bootmodes too.
-**Writing to MMC/EMMC** +**Writing to MMC**
.. prompt:: bash =>
- env export -t $loadaddr <list of variables> - fatwrite mmc ${mmcdev} ${loadaddr} ${bootenvfile} ${filesize} + setenv save_to_env <variables to be saved in uEnv.txt> + run save_uenv
-**Reading from MMC/EMMC** +**Reading from MMC**
-By default run envboot will read it from the MMC/EMMC partition ( based on +By default run envboot will read it from the MMC partition ( based on mmcdev) and set the environments.
If manually needs to be done then the environment can be read from the @@ -615,8 +616,11 @@ filesystem and then imported
.. prompt:: bash =>
- fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile} - env import -t ${loadaddr} ${filesize} + run envboot + +To read from eMMC, the save_uenv and envboot commands would need to be +changed to pickup the bootenvfile from eMMC. Mainly the write and read +commands would change to eMMC.
.. _k3_rst_refer_openocd: