Jetson TX2/TX2i bootloader redundancy

Hi,
I’ve been reading about enabling bootloader redundancy on TX2/TX2i and it is very confusing with not much info available. I basically want to make sure if my device for some reason (say data corruption) couldn’t boot from the main bootloader, it jumps to the redundant set and continue to boot from there.
Some questions I have -

  1. Is bootloader redundancy by default enabled for Jetson TX2/TX2i ? If so, how many redundant copies of BFS are by default flashed (Jetpack 3.2.1)? How many maximum number of BFS can I have ? Is nvbootctrl the correct command to check or enable/disable redundancy configuration ?

  2. I found a document Runtime_Bootloader_Update_Process_for_Jetson_TX1 which does explain some. Tried looking for the equivalent doc for Jetson TX2 but couldn’t find. Please send me a pointer to it.
    Thanks!

hello FM2461,

  1. bootloader redundancy is disabled by default.
  2. please download the [L4T Documentation] and check the [NVIDIA Tegra Linux Driver Package]
    you should refer to [Release 28.2 Development Guide]-> [Boot Loader]-> [TX2 Bootloader Update and Redundancy] for details.

Thank You JerryChang. Found all the info around Bootloader Redundancy in the L4T Documentation as suggested by you.

Have a quick followup question -
Why is the bootloader redundancy disabled by default ? The default partition configuration in flash_l4t_t186.xml when I flashed using flash.sh (from Jetpack 28.2.1) without enabling redundancy shows both the slots enabled anyway.

Number  Start (sector)    End (sector)  Size       Code  Name
   1            4097        58724352   28.0 GiB    0700  APP
   2        58724353        58732544   4.0 MiB     0700  mts-bootpack
   3        58732545        58740736   4.0 MiB     0700  mts-bootpack_b
   4        58740737        58741760   512.0 KiB   0700  cpu-bootloader
   5        58741761        58742784   512.0 KiB   0700  cpu-bootloader_b
   6        58742785        58743808   512.0 KiB   0700  bootloader-dtb
   7        58743809        58744832   512.0 KiB   0700  bootloader-dtb_b
   8        58744833        58750976   3.0 MiB     0700  secure-os
   9        58750977        58757120   3.0 MiB     0700  secure-os_b
  10        58757121        58761216   2.0 MiB     0700  eks
  11        58761217        58762424   604.0 KiB   0700  bpmp-fw
  12        58762425        58763632   604.0 KiB   0700  bpmp-fw_b
  13        58763633        58764632   500.0 KiB   0700  bpmp-fw-dtb
  14        58764633        58765632   500.0 KiB   0700  bpmp-fw-dtb_b
  15        58765633        58769728   2.0 MiB     0700  sce-fw
  16        58769729        58773824   2.0 MiB     0700  sce-fw_b
  17        58773825        58786112   6.0 MiB     0700  sc7
  18        58786113        58798400   6.0 MiB     0700  sc7_b
  19        58798401        58802496   2.0 MiB     0700  FBNAME
  20        58802497        59064640   128.0 MiB   0700  BMP
  21        59064641        59326784   128.0 MiB   0700  BMP_b
  22        59326785        59392320   32.0 MiB    0700  SOS
  23        59392321        59457856   32.0 MiB    0700  SOS_b
  24        59457857        59588928   64.0 MiB    0700  kernel
  25        59588929        59720000   64.0 MiB    0700  kernel_b
  26        59720001        59721024   512.0 KiB   0700  kernel-dtb
  27        59721025        59722048   512.0 KiB   0700  kernel-dtb_b
  28        59722049        60246336   256.0 MiB   0700  CAC
  29        60246337        61071326   402.8 MiB   0700  UDA

hello FM2461,

there’s flash.xml to specify the partition names and its files flashing into a board.
however, you still need to configure from the software side to enable A/B redundancy.
thanks