We are trying to enable the A/B redundancy in TX2. We referred the below linkes and are able to enable it.
We updated the smd_info.cfg file and executed the “
sudo nv_smd_generator smd_info.cfg slot_metadata.bin” command and then flashed out device. Here is a copy of our smd_info.cfg.
# Copyright (c) 2017-2018, NVIDIA CORPORATION. All rights reserved. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING # FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER # DEALINGS IN THE SOFTWARE. # SMD metadata information < VERSION 3 > # # Config 1: Disable A/B support (Default) # # slot info order is important! # <priority> <suffix> <retry_count> <boot_successful> #15 _a 7 1 # # Config 2: Enable redundancy support (by removing comments ##) # < REDUNDANCY_USER 1 > # slot info order is important! # <priority> <suffix> <retry_count> <boot_successful> 15 _a 7 1 14 _b 7 1
We checked this with the below commands.
nvidia@tegra-ubuntu:~$ sudo nvbootctrl dump-slots-info magic:0x43424e00, version: 3 features: 3 num_slots: 2 slot: 0, priority: 15, suffix: _a, retry_count: 7, boot_successful: 1 slot: 1, priority: 14, suffix: _b, retry_count: 7, boot_successful: 1 nvidia@tegra-ubuntu:~$ sudo nvbootctrl get-current-slot 0
The debug log for this case is attached as “normal_working.log”.
In order to test the change in the active slot, we used the dd command to corrupt the _a partition and rebooted the system. We observed two behaviours.
1.We corrupted the mts-bootpack partition using “
sudo dd if=examples.desktop of=/dev/mmcblk0p2” command and rebooted the system. The system got booted successfully and the output for nvbootctrl command below.
nvidia@tegra-ubuntu:~$ sudo nvbootctrl dump-slots-info [sudo] password for nvidia: magic:0x43424e00, version: 3 features: 3 num_slots: 2 slot: 0, priority: 15, suffix: _a, retry_count: 0, boot_successful: 1 slot: 1, priority: 14, suffix: _b, retry_count: 7, boot_successful: 1 nvidia@tegra-ubuntu:~$ sudo nvbootctrl get-current-slot 1
The device has booted in slot 1.The debug log is attached as “mts-bootpack_corrupted.log”
2.We tried the same by corrupting the kernel partition using “
sudo dd if=examples.desktop of=/dev/mmcblk0p26”. This now the device failed to boot. The debug log is attached as “kernel_corrupted.log”
Are these steps enough to enable this device recovery feature? and is there an alternate way to test this?