• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 247 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

SK-AM62: Boot partition 1 as primary boot mode and UDA as backup boot.

SK-AM62: Set value of redundant address to have a backup image

Hong Zhuang Shen
Prodigy 150 points
Part Number: SK-AM62

Hi TI Expert:

May I know how to set the value of redundant image?
I think my am62x_evm_a53_defconfig don't have redundant address:
CONFIG_ENV_SIZE=0x20000
CONFIG_ENV_OFFSET=0x680000

I found 2 statements in Kconfig:

1) CONFIG_ENV_ADDR_REDUND:
These settings describe a second storage area used to hold
a redundant copy of the environment data, so that there is
a valid backup copy in case there is a power failure during
a "saveenv" operation.

2) CONFIG_ENV_OFFSET_REDUND (optional):

Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
hold a redundant copy of the environment data. This provides a
valid backup copy in case the other copy is corrupted, e.g. due
to a power failure during a "saveenv" operation.

This value may also be positive or negative; this is handled in the
same way as CONFIG_ENV_OFFSET.

This value is also in units of bytes, but must also be aligned to
an MMC sector boundary.



  • 0
    TI__Guru**** 168481 points

    Hi,

    I am routing your query to our U-Boot expert for comments.

  • 0
    TI__Expert 8510 points

    Hi,

    These CONFIG options are to have a backup of U-boot environment, not of U-boot binaries. Is this what is needed?

    ~Judith

  • 0 in reply to Bin Liu
    Prodigy 150 points

    Hi, 
    Im using am62x eval kit, ti-processor-sdk-linux-am62xx-evm-08.04.01.03.
    I may explain what I did in my experiment:

    a) "mmc partconf" only will affect the U-boot environment, which mean that, If I need to switch between UDA and Boot 1, I need to set "mmc partconf".

    b) When I erase Boot Partition 1, R5 will switch to UDA automatically, but it stuck at "Starting ATF on ARM64 core...", do it mean it do not switch to backup U-boot automatically?
    Below shows my booting log:
    I had flash image into boot1 and UDA, 
    Boot 1 image: Jul 05 2023 - 16:01:37
    UDA image: Jul 05 2023 - 16:04:57

    1) At the first, I configure mmc partconf 0 1 1 1, it can boot normally, but if I switch to UDA, it stuck at R5 "Starting ATF on ARM64 core...". So, do it mean backup U-boot is not set, and can't be boot when boot 1 image is corrupt or has been erased?

    Correct me if im wrong....

    I need some guide so that it can switch to UDA as backup mode automatically when boot 1 is failed.  (Which mean that no need set "mmc partconf 0 1 7 1    ")

  • 0 in reply to Hong Zhuang Shen
    TI__Expert 8510 points

    Hi,

    a) "mmc partconf" only will affect the U-boot environment, which mean that, If I need to switch between UDA and Boot 1, I need to set "mmc partconf".

    partconf command is used to give ROM access to the correct boot partition:

    To give the ROM access to the boot partition, the following commands must be used for the first time:

    => mmc partconf 0 1 1 1
=> mmc bootbus 0 2 0 0


    Shown in the doc here: https://software-dl.ti.com/processor-sdk-linux-rt/esd/AM62X/08_06_00_42/exports/docs/linux/Foundational_Components/U-Boot/UG-Memory.html?highlight=partconf#booting-tiboot3-bin-tispl-bin-and-u-boot-img-from-emmc-boot-partition-for-k3-class-of-socs

    It modifies the PARTITION_CONFIG field.

    b) When I erase Boot Partition 1, R5 will switch to UDA automatically, but it stuck at "Starting ATF on ARM64 core...", do it mean it do not switch to backup U-boot automatically?

    1) At the first, I configure mmc partconf 0 1 1 1, it can boot normally, but if I switch to UDA, it stuck at R5 "Starting ATF on ARM64 core...".

    Can you please verify first if you can boot from UDA all the way to Linux Kernel? Erase boot0 partition, and boot with eMMC Boot using UDA.

    ~ Judith