Differences between revisions 1 and 59 (spanning 58 versions)
Revision 1 as of 2016-11-24 09:54:03
Size: 1735
Editor: ?MichaelStapelberg
Comment:
Revision 59 as of 2019-03-25 08:17:44
Size: 2725
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
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. 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+.
Line 3: Line 3:
Debian stretch runs on the Raspberry Pi 3 as soon as the following blockers are out of the way: Debian buster runs on all of the Raspberry Pi 3 models, but there are a few issues preventing us from releasing an official image:
Line 5: Line 5:
 * https://bugs.debian.org/845422 (src:linux: BCM2835 MMC driver)
 * https://bugs.debian.org/845488 (ITP: linux-firmware-raspi3 package)
 * https://bugs.debian.org/845439 (vmdebootstrap: don’t enforce (U)EFI on arm64)
 * https://bugs.debian.org/845526 (vmdebootstrap: allow users to create the boot directory path)
 * DebianPkg:vmdb2, the successor of vmdebootstrap, included in Debian "buster".
 * The Bluetooth module is untested.
Line 10: Line 8:
Once the above blockers are fixed, there are still a couple of known issues: Longer-term improvements:
Line 12: Line 10:
 * The smsc95xx USB ethernet driver does not use the smsc95xx.macaddr= kernel parameter which the Raspberry Pi bootloader specifies. Hence, on every boot you will have a different MAC address, resulting in new IP addresses if you use DHCP/SLAAC.
 * The Wifi and Bluetooth modules are not currently supported.
 * On boot, the initrd tries to do a file system check but fails because it cannot find fsck.ext4. Later on, systemd actually starts a working file system check, so this is more of a cosmetic issue.
 * Images built with vmdebootstrap don’t automatically expand to use all of the available SD card space.
 * 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]].
Line 21: Line 16:
To install the (unofficial, unsupported!) preview image on the SD card {{{/dev/sdb}}}, use: To install the (unofficial, unsupported!) preview image on the SD card {{{/dev/sdX}}}, use (change ''/dev/sdX'' to your SD card device name):
Line 23: Line 18:
$ wget https://people.debian.org/~stapelberg/raspberrypi3/2016-11-24-raspberry-pi-3-stretch-PREVIEW.img
$ sudo dd if=2016-11-24-raspberry-pi-3-stretch-PREVIEW.img of=/dev/sdb bs=5M
$ 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
Line 27: Line 22:
The root password is “raspberry”. 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

== GPIO ==

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
}}}

GPIO libraries work, but require some extra effort as of 2019-03-25.
 * For RPi.GPIO, see https://alioth-lists.debian.net/pipermail/pkg-raspi-maintainers/Week-of-Mon-20190318/000333.html
 * For gpiozero, see https://alioth-lists.debian.net/pipermail/pkg-raspi-maintainers/Week-of-Mon-20190318/000334.html

== Known issues ==
Shipping a system with a preset root password usable over the network is a recipe for disaster. We want to tackle this! 😉

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.

Longer-term improvements:

  • The hardware still needs a non-free binary blob to boot (included in the raspi3-firmware package). A free software replacement is being worked on but development is stalled.

Any help on these issues is very welcome!

Preview image

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

GPIO

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

GPIO libraries work, but require some extra effort as of 2019-03-25.

Known issues

Shipping a system with a preset root password usable over the network is a recipe for disaster. We want to tackle this! 😉