kas-kaz
commented
2 months ago I was able to set up the development environment in a Raspberry Pi Zero 2 W using Raspios Bullseye Lite arm64.
The image I used was 2022-01-28-raspios-bullseye-arm64-lite.zip.
These are the steps I followed, adapted from the guide Raspberry Pi OS Build Instructions:
Initial setup
The only change from the original guide is making swap space permanent as it was useful for my setup.
sudo apt update
# Interface -> Activate camera and SPI
# Locale -> en_US.UTF-8
sudo raspi-config
# add `spidev.bufsiz=131072`
sudo nano /boot/cmdline.txt
# Change to `CONF_SWAPSIZE=1024`
sudo nano /etc/dphys-swapfile
sudo rebootInstall python3.10
The only difference is I didn't install package python-pil, but I installed the dependencies of that package in the following step.
Also I used make -j 3 to take advantage of the Quad Core (with -j 4 the use of Swap is so intensive that it is even slower).
The link to lsb_release was needed because the custom installation of Python 3.10 broke the package and the tests require it.
sudo apt install -y build-essential zlib1g-dev libncurses5-dev \
libgdbm-dev libnss3-dev openssl libssl-dev libreadline-dev \
libffi-dev wget libsqlite3-dev
# Grab the python3.10 source
wget https://www.python.org/ftp/python/3.10.10/Python-3.10.10.tgz
tar -xzvf Python-3.10.10.tgz
cd Python-3.10.10
# Compile
./configure --enable-optimizations
sudo make -j 3 altinstall
# Make python3.10 the default version
sudo update-alternatives --install /usr/bin/python python /usr/local/bin/python3.10 1
sudo update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.10 1
# Manually re-install `python3-apt`
sudo apt remove --purge python3-apt -y
sudo apt autoremove -y
sudo apt install python3-apt -y
# Link to lsb_release module, needed for tests
sudo ln -s /usr/share/pyshared/lsb_release.py /usr/local/lib/python3.10/site-packages/lsb_release.py
cd ..Install dependencies
I had to download wiringpi-2.61-1-arm64 as the 64 bits version of the package is not available in apt. Version 2.61 (instead of 2.60 in the Buster setup) adds support for Zero 2 W.
The version of libzbar in apt in Bullseye is exactly the one required so no need to download the package.
# Install wiringpi with Zero 2 W support
wget https://github.com/WiringPi/WiringPi/releases/download/2.61-1/wiringpi-2.61-1-arm64.deb
sudo dpkg -i wiringpi-2.61-1-arm64.deb
sudo apt install -y python3-pip libjpeg-dev zlib1g-dev libopenjp2-7 git \
python3-opencv python3-picamera libatlas-base-dev qrencode
# Install python-pil dependencies
sudo apt install -y libc6 libfreetype6 libimagequant0 libjpeg62-turbo \
liblcms2-2 libtiff5 libwebp6 libwebpdemux2 libwebpmux3 zlib1g
sudo apt install -y libzbar0Compile MMAL 64 bits libraries
This was the trickiest part. MMAL libraries used by PiCamera are not available for arm64. And everywhere I read about it they mention it is discouraged as it causes crashes. I tried capturing QR codes several times and nothing failed. We need to download userland project and make these modifications as explained here.
git clone https://github.com/raspberrypi/userland
cd userland
git config --global user.email "xxxxxx"
git config --global user.name "xxxxxx"
git revert f97b1af1b3e653f9da2c1a3643479bfd469e3b74
git revert e31da99739927e87707b2e1bc978e75653706b9c
# Add 'SET(CMAKE_SHARED_LINKER_FLAGS "-Wl,--no-as-needed")' before
# line 'target_link_libraries(mmal mmal_core mmal_util mmal_vc_client vcos mmal_components)'
nano interface/mmal/CMakeLists.txt
sudo apt install -y cmake
./buildme --aarch64
sudo cp /opt/vc/lib/*.so /usr/lib/aarch64-linux-gnu/
cd ..Download the SeedSigner code:
git clone https://github.com/SeedSigner/seedsigner
cd seedsignerInstall Python pip dependencies:
I had to update RPi.GPIO to 0.7.1 as it added support for the newer version of GCC used in Bullseye.
python3 -m pip install -r requirements.txt
python3 -m pip install picamera==1.13 numpy==1.25.2 spidev==3.5 RPi.GPIO==0.7.1The rest is the same! I was able to run the rests as was shown in the guide, and also could execute main.py and run the app correctly. I didn't check every single option though, just scanned some QRs, created a seed, signed a transaction, and restored the seed using QR in another SeedSigner device. All worked correctly.
I never contributed to this project and I didn't know if it was appropriate to create a PR with a new guide. If the contributors consider it is desirable I could do it of course.
hax0rbana-adam
Build instructions fail on Debian 11 (there's a separate ticket about Debian 12 #430).
It'd be good if a core contributor could lay out what they'd like the roadmap to be in order to fix this (or how developer should set up an environment once Debian 10 is not longer supported).
This failure on Debian 11 was reported over a year ago in #149, but that was closed without being fixed nor being labeled as "won't fix", so it's not clear what the status is here. Buster (Debian 10) is supported under LTS for almost another year (June 30th, 2024), so it's getting security patches now, but its days are numbered. Even with the stripped down final images, developers still need to have a full environment to build everything, and that is going to get a lot harder when all the mirrors delete the packages for buster (like they did recently for stretch).
When following the manual installation instructions on the latest Raspberry Pi OS (based on Debian 11), the following error occurs when installing dependencies.