Setting bootable and unbootable AB rootFS slots for L4T r35.1

Hello,
regarding L4T 35.1.0 nvbootctrl mark as bootable - #12 by JerryChang

the issues of the linked post… (I need to mark my AB rootfs slots as bootable or unbootable on a L4T r35.1 for Nvidia Jetson AGX)

  • First of all, how is it looking the release of that functionality? I really need to use it asap, but if it is coming lets say this month, may be it does not worth the effort of implementing it manually.

  • If not, I am wondering from the following miniscript example:

# cd /sys/firmware/efi/efivars/
# printf "\x07\x00\x00\x00" > /tmp/var_tmp.bin
# printf "\x3c\xc0\x01\x00" >> /tmp/var_tmp.bin
# chattr -i RootfsInfo-781e084c-a330-417c-b678-38e696380cb9
# dd if=/tmp/var_tmp.bin of=RootfsInfo-781e084c-a330-417c-b678-38e696380cb9; sync
# chattr +i RootfsInfo-781e084c-a330-417c-b678-38e696380cb9
# reboot

1 - Is that working for slot A or for the current slot?
2 - Is there some other file to do the opposite? (set as unbootable)

These both questions would help me to manage it pretty quickly.

Thanks in advance,
Alvaro.

hello alvaro.gimenez.s,

I don’t have solid release date, but it’s around mid-Jan/2023 for next JetPack public release.
it’ll be able to create separated UEFI variables for rootfs A/B status, so user may rest them in UEFI menu.

Hi Jerry,
thanks for the answer. It looks promising, that should be this or next week.

  • Will it support also these variables for nvbootctrl script? I actually need them there. I am implementing the update system with rauc and i have everything else already configured (in fact, with cboot was working my workaround).
    So, more concrete: Are the functions is-slot-marked-successful, mark-boot-successful and set-slot-as-unbootable in the tool nvbootctrl implemented and working in the next JetPack public release?

  • May be I try anyway with your example script workaround anyway, if you could answer me the other 2 questions,
    1- Is that working for slot A or for the current slot?
    2 - Is there some other file to do the opposite? (set as unbootable)

Thank you in advance,
Alvaro.

hello alvaro.gimenez.s,

that’s register settings to update the slot-A status to normal.
as you can see, it writes the register values to var_tmp.bin and update RootfsInfo property directly.

may I know what’s your actual use-case, could you please wait for next Jetpack release?

Hi Jerry,
we are actually adapting an OS for Nvidia Jetson AGX using YOCTO OE4T and we need AB partitioning and update. Until now we were using a version with the previous Kernel and Jetpack versions, but we actually need functionality from the latest Jetpack.

The project cant be blocked on this for too long, but I guess is the better option.

Specifically, we need nvbootctrl full functionality for this. Will that be included in the upcoming release? From the release notes it looks so, but I would like to be sure.

Thanks in advance,
Alvaro.

hello alvaro.gimenez.s,

we should have next Jetpack release soon, why don’t you wait for it and give it a try.

Hello Jerry,
yes, I am in that status right now, waiting for the new Jetpack release. I just wanted to be sure that the fixes we need will be included.
If the UEFI implementation and the nv tools will support AB partitioning again, then it should be all fine as long as it does not get too delayed.
Regards,
Alvaro.

hello alvaro.gimenez.s,

okay, please wait for public release to confirm the use-case. you may reply this, or initial a new discussion thread to grant supports.

Hi Jerry,
any news about when the Jetpack will be released? January is coming to an end and we have somehow the development stopped.

Regards,
Alvaro.

hello alvaro.gimenez.s,

as you can see, JetPack 5.1 is available now.