Update to the 2019-02-06 image.
|Deletions are marked like this.||Additions are marked like this.|
|Line 10:||Line 10:|
|* The hardware still needs a non-free binary blob to boot (included in the raspi3-firmware package). A [[https://github.com/christinaa/rpi-open-firmware|free software replacement]] is being worked on.||* The hardware still needs a non-free binary blob to boot (included in the raspi3-firmware package). A [[https://github.com/christinaa/rpi-open-firmware|free software replacement]] is being worked on but development is [[https://github.com/christinaa/rpi-open-firmware/issues/37|stalled]].|
The Raspberry Pi 3 is a version of the RaspberryPi which was released in February 2016. It contains a 1.2 GHz ARM Cortex-A53 CPU and hence is the first version of the RaspberryPi to support the arm64 architecture. In 2018, two further models were added to the Raspberry Pi 3 family — The 3B+ and 3A+.
Debian buster runs on all of the Raspberry Pi 3 models, but there are a few issues preventing us from releasing an official image:
vmdb2, the successor of vmdebootstrap, included in Debian "buster".
- The Bluetooth module is untested.
Any help on these issues is very welcome!
To install the (unofficial, unsupported!) preview image on the SD card /dev/sdX, use (change /dev/sdX to your SD card device name):
$ wget https://people.debian.org/~gwolf/raspberrypi3/20190206/20190206-raspberry-pi-3-buster-PREVIEW.img.xz $ xzcat 20190206-raspberry-pi-3-buster-PREVIEW.img.xz | dd of=/dev/sdX bs=64k oflag=dsync status=progress
It is recommended to check the image was correctly downloaded by comparing its SHA256:
$ wget https://people.debian.org/~gwolf/raspberrypi3/20190206/20190206-raspberry-pi-3-buster-PREVIEW.img.xz.sha256 $ sha256sum -c 20190206-raspberry-pi-3-buster-PREVIEW.img.xz.sha256
If resolving client-supplied DHCP hostnames works in your network, you should be able to log into the Raspberry Pi 3 using SSH after booting it:
$ ssh root@rpi3 # Password is “raspberry”
For the sources of this image, please see https://github.com/Debian/raspi3-image-spec
If you have any questions/feedback, please direct them to https://lists.alioth.debian.org/mailman/listinfo/pkg-raspi-maintainers
You can use sysfs to configure and control the GPIO pins. The pin numbers are offset by 458 (see /sys/kernel/debug/gpio). Thus to enable pin 4 (as root):
# echo "462" > /sys/class/gpio/export
Unfortunately most Python GPIO libraries are unusable under arm64, as they try to detect the CPU revision from /proc/cpuinfo. The issue is tracked here: https://github.com/raspberrypi/linux/issues/2110
Shipping a system with a preset root password usable over the network is a recipe for disaster. We want to tackle this! 😉