--- wikisrc/ports/evbarm/raspberry_pi.mdwn 2017/10/31 11:32:36 1.66 +++ wikisrc/ports/evbarm/raspberry_pi.mdwn 2018/10/30 14:19:58 1.75 @@ -2,7 +2,7 @@ This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported. -Initial, limited, Raspberry Pi support was introduced in NetBSD 6.0. NetBSD 7.0 adds complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board. Raspberry Pi 3 support was added for NetBSD 8, and backported to NetBSD 7 in July of 2017. +Initial, limited, Raspberry Pi support was introduced in NetBSD 6.0. NetBSD 7.0 adds complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board. Raspberry Pi 3 support was added for NetBSD 8, and backported to NetBSD 7 in July of 2017. (This page assumes those using NetBSD 7 are using 7.2, or the netbsd-7 branch after mid 2018.) [[images/raspberrypi.jpg]] @@ -12,45 +12,43 @@ Initial, limited, Raspberry Pi support w # What works (and what doesn't yet) -## NetBSD 7 before July, 2017 +## NetBSD 7 and NetBSD 8 - - RaspberryPi 1, and 2 (including SMP) - - multi-user boot with root on SD card + - RaspberryPi 1, 2, 3 (except Pi 3 builtin WiFi and bluetooth) + - multiple processors on 2/3 + - boots normally to multiuser, with FAT32 boot partition on uSD + - root filesystem can be uSD or USB-attached mass storage - serial or graphics console (with EDID query / parsing) + - X11 via HDMI + - GPU (VCHIQ) - 3D and video decode. man page missing. + - USB host controller - dwctwo(4) and most devices work + - USB Ethernet - usmsc(4) - DMA controller driver and sdhc(4) support + - RNG - Audio: works. man page missing. - - I²C: works, could use enhancements, man page - GPIO - - RNG + - I²C: works, could use enhancements, man page - SPI: could use enhancements, man page - - GPU (VCHIQ) - 3D and video decode. man page missing. - - USB (host) - dwctwo(4) - - USB Ethernet - usmsc(4) - - X windows. - -## NetBSD 7 after July, 2017 and NetBSD 8 - - - Raspberry Pi 3 (excluding WiFi and bluetooth) ## NetBSD current - - Raspberry Pi 3 bluetooth + - Raspberry Pi 3 builtin bluetooth - Raspberry Pi 3 new SD host controller driver ## What needs work - USB (host); isochronous transfers. - - WiFi - - Raspberry Pi 3 in 64-bit mode. (Note that this will be provided by the evbarm64 port, rather than evbarm.) + - Raspberry Pi 3 builtin WiFi # CPU types -Note that one can also use code for earlier models on later models. - - Raspberry Pi 1 uses "earmv6hf". - Raspberry Pi 2 uses "earmv7hf". - Raspberry Pi 3 uses "earmv7hf". +Note that one can run earmv6hf code on the 2 and 3. See also +[[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode. + # Installation ## SD card structure @@ -63,7 +61,7 @@ A 2 GB card is the smallest workable siz ## Choosing a version -First, decide if you want to install a formal release (7.1), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current. Note that 7.1 predates Raspberry Pi 3 support. For people who don't know how to choose among those, netbsd-8 is probably best. +First, decide if you want to install a formal release (7.2 or 8.0), a stable branch build (netbsd-7, netbsd-8), or NetBSD-current. For people who don't know how to choose among those, 8.0 or netbsd-8 is probably best. See also "ebijun's image", below, which is NetBSD-current and includes packages. @@ -86,9 +84,9 @@ Getting sources and building a release w NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/). These are equivalent to building yourself. - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards. - - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2. - - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg) - - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/) + - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2/3. + - The old stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg) + - The stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/) - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/) ## Preparing a uSD card @@ -96,7 +94,7 @@ NetBSD provides nightly builds on [nyftp Once you have rpi.img.gz (or rpi_inst), put it on a uSD card using gunzip and dd, for example: - gunzip rpi.img.gz - - dd if=rpi.i7mg of=/dev/disk1 + - dd if=rpi.img of=/dev/disk1 ### Serial Console @@ -134,6 +132,8 @@ every few weeks. - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README) +# Maintaining a system + ## Updating the kernel - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g. @@ -143,13 +143,35 @@ every few weeks. /Users/feyrer/work/NetBSD/cvs/src-current/obj.evbarm-Darwin-XXX/sys/arch/evbarm/compile/RPI2/netbsd ... - - Besides the "netbsd" kernel in ELF format, there is also a "netbsd.bin" kernel that is in a format that the Raspberry can boot. + - Besides the "netbsd" kernel in ELF format, there is also a "netbsd.img" (for current) or "netbsd.bin" (for 7 and 8) kernel that is in a format that the Raspberry can boot. - Depending on your hardware version, copy this either to /boot/kernel.img (First generation Pi, Pi Zero hardware) or to /boot/kernel7.img (Pi 2, Pi 3 hardware) - reboot +## Updating the firmware + +A section below describes the process of updating NetBSD's copy of the firmware from upstream, with testing, by NetBSD developers. This section is about updating a system's firmware from the firmware in a version of NetBSD. + +TODO: Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec). Explain any particular cautions. + +## Booting + +The device boots by finding a file "bootcode.bin". The primary location is a FAT32 partition on the uSD card, and an additional location is on a USB drive. See the [[upstream documentation on booting|https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/]] and read all the subpages. + +The standard approach is to use a uSD card, with a fdisk partition table containing a FAT32 partition marked active, and a NetBSD partition. The NetBSD partition will then contain a disklabel, pointing to an FFS partition (a), a swap paritiion (b) and the FAT32 boot partition mounted as /boot (e). The file /boot/cmdline.txt has a line to set the root partition. + +One wrinkle in the standard approach is that the disk layout is "boot swap /", but the NetBSD fdisk partition starts at the location of /. The / partition can hold a disklabel, while swap cannot. It is normal to have swap after /, but this arrangement permits growing / on first boot, for the typical case where a larger uSD is used. + +An alternate approach is to have the boot FAT32 partition as above, but to have the entire system including root on an external disk. This is configured by changing root=ld0a to root=sd0a or root=dk0 (depending on disklabel/GPT). Besides greateer space, part of the point is to avoid writing to the uSD card. + +A third approach is to configure USB host booting (default off except on Pi 3+) see the upstream documentation) and have the boot partition also on the external device. In this case the external device must be configured via fdisk because the hardware's first-stage boot does not have GPT support. \todo Explain if this has been observed to work. + +\todo Explain USB enumeration and how to ensure that the correct boot and root devices are found if one has e.g. a small SSD for the system and a big disk. + +\todo Explain if the procedure to program USB host boot mode can function under NetBSD; the examples on the web use Raspbian. + # Wireless Networking - Note that the built-in WiFi in the RPI3 is not yet supported. +Note that the built-in WiFi in the RPI3 is not yet supported. USB WiFi interfaces (that work on NetBSD in general) should all work. - A Realtek 802.11n USB adaptor configures as urtwn(4). - Configure with wpa_supplicant in /etc/rc.conf - @@ -197,22 +219,21 @@ $ retroarch --appendconfig gamepad.cfg - These notes are for people working on improvements to RPI support in NetBSD. -## Updating the firmware +## Updating the firmware version in the NetBSD sources + +(Note that trying new firmware may result in a non-bootable system, so +be prepared to recover the bootable media with another system.) -You probably don't want to do this. Firmware updates can break things, -and the latest firmware that's been tested is already included in the -NetBSD build you installed. +Upstream firmware releases are +[on GitHub](https://github.com/raspberrypi/firmware/releases). +Copy all files except `kernel*.img` into `/boot` and reboot. -If you're feeling adventurous (or are the port maintainer), here's what -to test whenever you try new firmware: +New firmware should pass all of the following tests before being committed to NetBSD. - Audio - OMXPlayer (and [[!template id=man name="vchiq"]]) - Serial/framebuffer console - CPU frequency scaling -That goes for all of `rpi[0123]`. +Tests shoudl be run on all of `rpi[0123]`. -Upstream firmware releases are -[on GitHub](https://github.com/raspberrypi/firmware/releases). -Copy all files except `kernel*.img` into `/boot` and reboot.