I'm planning to implement a "simple" A/B booting scenario with autoboot.txt
If I understand correctly, I need three FAT32 partitions:
- Partition 1 (FAT32) containing just one file autoboot.txt
- Partition 2 (FAT32) acting as bootfsA with Kernel, cmdline and so on on it
- Partition 3 (FAT32) acting as bootfsB with same logical content as bootfsA.
When changing from A to B or vice versa I need to enter tryboot and if that was working I can update autoboot.txt.
Is this correct?
Also, is the following command a good way to enter tryboot in case I can't control what is appended to my reboot command? Or is there a better way to handle this?
If I understand correctly, I need three FAT32 partitions:
- Partition 1 (FAT32) containing just one file autoboot.txt
- Partition 2 (FAT32) acting as bootfsA with Kernel, cmdline and so on on it
- Partition 3 (FAT32) acting as bootfsB with same logical content as bootfsA.
When changing from A to B or vice versa I need to enter tryboot and if that was working I can update autoboot.txt.
Is this correct?
Also, is the following command a good way to enter tryboot in case I can't control what is appended to my reboot command? Or is there a better way to handle this?
Code:
vcmailbox 0x00038064 4 0 1
Statistics: Posted by netbloom — Mon Dec 30, 2024 10:45 pm