I thought about using 2 working installations, and a boot selector via autoboot.txt like it was discussed here instead:
Discussion:
viewtopic.php?p=2229940&hilit=rauc&sid= ... 1#p2229940
Documentation:
https://www.raspberrypi.com/documentati ... toboot-txt
When using it I would have 3 partitions:mmcblk0p3 would be mounted in /mnt/b when using mmcblk0p2 as '/'
mmcblk0p2 would be mounted in /mnt/a when using mmcblk0p3 as '/'
(I know the partition names might be different on an eMMC)
Programming the system for the 1st time could still be done via I/O board.
Updateing the unused system could be done via tar or dd to /mnt/b (or /mnt/a )
Switching between the system would be made by writing to /boot/autoexec.txt
I hope I have understood the dokumentation of autoboot.txt they are talking about boot_partitions and I don't know if they are talking about "/boot" or "/"
Maybe someone could give me some advice about the possibilities.
Discussion:
viewtopic.php?p=2229940&hilit=rauc&sid= ... 1#p2229940
Documentation:
https://www.raspberrypi.com/documentati ... toboot-txt
When using it I would have 3 partitions:
Code:
mmcblk0 179:0 0 29.7G 0 disk├─mmcblk0p1 179:1 0 256M 0 part /boot├─mmcblk0p2 179:2 0 29.5G 0 part /└─mmcblk0p3 179:2 0 29.5G 0 part /mmcblk0p2 would be mounted in /mnt/a when using mmcblk0p3 as '/'
(I know the partition names might be different on an eMMC)
Programming the system for the 1st time could still be done via I/O board.
Updateing the unused system could be done via tar or dd to /mnt/b (or /mnt/a )
Switching between the system would be made by writing to /boot/autoexec.txt
I hope I have understood the dokumentation of autoboot.txt they are talking about boot_partitions and I don't know if they are talking about "/boot" or "/"
Maybe someone could give me some advice about the possibilities.
Statistics: Posted by Noob_User — Mon Jul 08, 2024 8:33 am