1. Change in services/mbot_start_networking.py and the README.md instruction
The Pi 5 bookworm's bootfs partition is mounted to /boot/firmware, unlike Pi 4 mounted to /boot. We need to modify mbot_config.txt related code in mbot_sys_utils by adding things like
if is_ubuntu or is_pi5:
check(`/boot/firmware`)
elif is_pi4:
check(`/boot`)
If we do not make this change, and following the Pi 4's instruction, then to modify the mbot_config.txt on pi 5 before boot up, the student would have to: 1)find a linux machine, 2)go to the rootfs partition and go to /boot to find mbot_config.txt. Mac and windows can only see bootfs which mounted to /boot/firmware.
2. Change in install scripts
The new Pi OS bookworm don't like people do pip install in system-wise and force users to do apt install unless using python virtual env. As a workaround for now, we change the pip install to apt install.
Why:
1. Change in services/mbot_start_networking.py and the README.md instruction
The Pi 5 bookworm's
bootfspartition is mounted to/boot/firmware, unlike Pi 4 mounted to/boot. We need to modify mbot_config.txt related code inmbot_sys_utilsby adding things likeIf we do not make this change, and following the Pi 4's instruction, then to modify the
mbot_config.txton pi 5 before boot up, the student would have to: 1)find a linux machine, 2)go to therootfspartition and go to/bootto findmbot_config.txt. Mac and windows can only seebootfswhich mounted to/boot/firmware.2. Change in install scripts
The new Pi OS bookworm don't like people do pip install in system-wise and force users to do apt install unless using python virtual env. As a workaround for now, we change the pip install to apt install.