Tx2 l4t 32.5.1 bup fail!

I tested the bup upgrade of the current system and found that it failed

  • After the system is powered on, run the following command to check the system
    nvbootctrl dump-slots-info

    I place the BUP file in the target system under this directory before the Update Engine is run: /opt/ota_package/
  • I use the following command to execute
    nv_update_engine --install
  • After the system restarted, I found that the bup failed
  • Run this command to check:nvbootctrl dump-slots-info
    log:Current bootloader slot: A
    Active bootloader slot: A
    magic:0x43424e00, version: 4 features: 3 num_slots: 2
    slot: 0, priority: 15, suffix: _a, retry_count: 7, boot_successful: 1
    slot: 1, priority: 0, suffix: _b, retry_count: 0, boot_successful: 0
  • Run this command to check:nv_update_engine --verify
    log:Nvidia A/B-Redundancy Update tool Version 2.0
    verifying update
    Verify bootloader update begins.
    The current slot 0 is marked as boot successful
    SM: S22
    Previous update on slot 1 failed
    The retry count of current slot 0 has been restored.
    The priority of current slot 0 has been restored.
    Set non-current slot 1 as unbootable.

hello easyzoom,

may I know what’s the actual use-case,

[edit] below is specific to r35.1 release.
you may see-also this forum topic for reference, Mark bootloader bootable
thanks

I want to upgrade bootloader, kernel,dtb and so on

  • After the upgrade, error logs are displayed when the system is powered on
    [0000.140] C> ERROR: Highest Layer Module = 0x40, Lowest Layer Module = 0x40,
    Aux Info = 0x0, Reason = 0xd
    [▒[0000.059] C> ERROR: Highest Layer Module = 0x40, Lowest Layer Module = 0x40,
    Aux Info = 0x0, Reason = 0xd
    [0▒[0000.054] C> ERROR: Highest Layer Module = 0x40, Lowest Layer Module = 0x40,
    Aux Info = 0x0, Reason = 0xd
    [0▒[0000.054] C> ERROR: Highest Layer Module = 0x40, Lowest Layer Module = 0x40,
    Aux Info = 0x0, Reason = 0xd
    [0[0000.054] C> ERROR: Highest Layer Module = 0x40, Lowest Layer Module = 0x40,
    Aux Info = 0x0, Reason = 0xd
    [0▒[0000.054] C> ERROR: Highest Layer Module = 0x40, Lowest Layer Module = 0x40,
    Aux Info = 0x0, Reason = 0xd
    [0[0000.054] C> ERROR: Highest Layer Module = 0x40, Lowest Layer Module = 0x40,
    Aux Info = 0x0, Reason = 0xd

sorry, I was misread your release version, that you’re actually using TX2 on r32.5.1.
previous comment revised.

hello easyzoom,

please refer to developer guide, Preparing for an Image-Based OTA Update.
may I know which TARGET_BSP you’re used?
please also review the steps performed on the Host Machine and also on the Jetson Device.

  • I use the following command to generate the image
    BOARDID=3636 BOARDSKU=0001 FAB=300 ROOTFS_AB=1 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh -x 0x18 mmcblk0p1
  • I use the following command to generate the bup package
    ./l4t_generate_soc_bup.sh t18x
  • The platform I use is TX2 NX

TARGET_BSP is Tegra186_Linux_R32.5.1_aarch64

hello easyzoom,

there should be fixes check-in to remove partition size change.
could you please share the tegraparser_v2/tegraparser_gpt.c for reference?

BTW,
may I know what’s the actual use-case,
is it possible for moving to the latest release image version?

  • I did change the partition , I changed flash_l4t_t186_rootfs_ab.xml
  • What’s wrong with l4t 32.5.1 version of bup?
    tegraparser_v2 is a binary file, What information does it contain?

tegraparser_v2 (913.8 KB)

  • I removed the APP_b partition from the xml file , * But I generated the bup package using the ROOTFS AB=1 environment variable Whether it’s because of this operation?

it is file system to create partitions with APP and APP_b for setting-up rootfs redundancy.
that should be expected failure if there’s no other APP partition to enable ROOTFS AB,

Then can I do bup upgrade for other AB partitions except APP partitions? If so, how can I modify smd_info.cfg correctly in this case ?

hello easyzoom,

what’s the partitions you’re going to update? i.e. bootloader, kernel and dtb?
please refer to this session, Updating an Individual Partition.

hello JerryChang
May I understand that the R32.5.1 version is not perfect, so the bup update cannot be completed ?

hello easyzoom,

had you try running the script nv_part_update with your customize update_list.conf to perform an individual partition update?

hello JerryChang,

This update_list.conf file does not exist in L4T R32.5.1

because you have to create update_list.conf by yourself, and please edit it to add the names and slots of the partition(s) to be updated.

hello JerryChang,

The update_list.conf you mentioned was only explained in version R32.7.1. Now I am using version R32.5.1

  • So version R32.5.1 is not supported, right?