Greetings!
Assume I have a multi-boot arrangement where I have a SSD configured with a "master" boot partition, (FAT - partition 1), and several additional boot and root partitions as extended partitions.
I use an autoboot.txt file in the "master" boot partition, and the state of certain GPIO pins, to select which of several other boot partitions will be used.
Viz.:I want this to boot on any "reasonable" Raspberry Pi, that is a Pi-3 or greater, including the Pi-5. Since it has to boot on a Pi-5, I will need the boot files from Bookworm as the files in the master boot partition, (though not all of the selections are valid for a Pi-5).
Question 1:
If I use the boot files from the 64-bit Bookworm in the master boot partition, and I jump via autoboot.txt to a new boot partition that contains older 32 bit boot files, is that OK? In other words, once the autoboot.txt redirects the device to a new boot partition, does it "start from scratch" as if it had never booted anything else, or are there any residual effects that carry over from the original boot partition?
Corollary question 2:
I have a tenth boot partition and the autoboot.txt documentation is not clear how they are numbered.
Is the tenth partition in the autoboot,.txt file "10" (decimal) or "0A" (hexadecimal)?
Assume I have a multi-boot arrangement where I have a SSD configured with a "master" boot partition, (FAT - partition 1), and several additional boot and root partitions as extended partitions.
I use an autoboot.txt file in the "master" boot partition, and the state of certain GPIO pins, to select which of several other boot partitions will be used.
Viz.:
Code:
# Pin/dip-switch mapping for GPIO O/S selection:# Dip-switch Broadcomm pin Physical pin Used to select:# None (default) -- -- Buster (Legacy) - Set up as dev environment# 1 21 40 Waveshare e-Paper Display with buttons# 2 26 37 Adafruit 16x2 LCD Display with buttons# 3 20 38 Adafruit 128x32 OLED display# 4 19 35 Bullseye 32 bit# 5 16 36 Bookworm 64 bit# common ground 39 Common ground for all switches# Setup GPIO pins, set as inputs, (ip), pulled high, (pu).gpio=21=ip,pugpio=26=ip,pugpio=20=ip,pugpio=19=ip,pugpio=16=ip,pu[default]# Default if no switches are selected# Buster Legacyboot_partition=5[all][gpio21=0]# Waveshare e-Paper Display with buttonsboot_partition=6[all][gpio26=0]# Adafruit 16x2 LCD Display with buttonsboot_partition=7[all][gpio20=0]# Adafruit 128x32 OLED display (no buttons)boot_partition=8[all][gpio19=0]# Bullseye 32 bitboot_partition=9[all][gpio16=0]# Bookworm 64 bitboot_partition=10[all]Question 1:
If I use the boot files from the 64-bit Bookworm in the master boot partition, and I jump via autoboot.txt to a new boot partition that contains older 32 bit boot files, is that OK? In other words, once the autoboot.txt redirects the device to a new boot partition, does it "start from scratch" as if it had never booted anything else, or are there any residual effects that carry over from the original boot partition?
Corollary question 2:
I have a tenth boot partition and the autoboot.txt documentation is not clear how they are numbered.
Is the tenth partition in the autoboot,.txt file "10" (decimal) or "0A" (hexadecimal)?
Statistics: Posted by jharris1993 — Wed Aug 21, 2024 4:54 pm — Replies 0 — Views 24