--- wikisrc/ports/evbarm/raspberry_pi.mdwn 2018/11/06 13:59:57 1.91 +++ wikisrc/ports/evbarm/raspberry_pi.mdwn 2018/11/06 22:29:26 1.103 @@ -1,6 +1,6 @@ [[!meta title="NetBSD/evbarm on Raspberry Pi"]] -This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported. +This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are supported. We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page. 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.) @@ -14,8 +14,9 @@ Initial, limited, Raspberry Pi support w ## NetBSD 7 and NetBSD 8 - - RaspberryPi 1, 2, 3 (except Pi 3 builtin WiFi and bluetooth) - - multiple processors on 2/3 + - RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth) + - RPI0 and RPI0W are expected to work (without WiFi, and one needs fdt files \todo where from?) + - multiple processors on RPI2/RPI3 - 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) @@ -32,24 +33,36 @@ Initial, limited, Raspberry Pi support w ## NetBSD current - - Raspberry Pi 3 builtin bluetooth - - Raspberry Pi 3 new SD host controller driver + - RPI3B+ + - RPI3 builtin bluetooth + - RPI3 new SD host controller driver + +## What needs documenting if it works + + - CM1 + - CM3 + - CM3lite ## What needs work - USB (host); isochronous transfers. - - Raspberry Pi 3 builtin WiFi + - RPI3 builtin WiFi # CPU types - - Raspberry Pi 1 uses "earmv6hf". - - Raspberry Pi 0 uses "\todo". - - Raspberry Pi 2 uses "earmv7hf". - - Raspberry Pi 3 uses "earmv7hf". - - Raspberry Pi 0W uses "\todo". + - RPI1 uses "earmv6hf". + - RPI0 uses "\todo". + - RPI2 uses "earmv7hf". + - RPI3 uses "earmv7hf". + - RPI0W uses "\todo". -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. +Note that one can run a build of earmv6hf on the 2 and 3. There will still be a kernel7, built to use the 2/3 hardware, but with the armv6 instruction set. + +In theory the code compiled for earmv7hf will be faster, but anecdotal experience is that it doesn't matter that much. + +While the evbarm port has "eb" variants (for big-endian mode), the RPI systems do not support eb and these variants will not work. Systems built with older CPU architectures (earm, earmv4, earmv5) are not expected to work on RPI. + +See also [[NetBSD/aarch64|aarch64]] for running the RPI2-1.2 and RPI3/RPI3+ in 64-bit mode. # Installation @@ -64,34 +77,38 @@ Note that SD cards generally have limite ## Choosing a version -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. +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, a recent build of netbsd-8 is probably best, with 8.0 the choice for those who value being at exactly a formal release. See also "ebijun's image", below, which is NetBSD-current and includes packages. ## Getting bits to install -You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers. - -Both will provide rpi.img.gz and rpi_inst.img.gz. Each is an image to be written to a uSD card, and has a FAT32 partition for booting. In rpi.img.gz, there is also an FFS partition for NetBSD. +You can either build a release yourself with build.sh, or get a release from the NetBSD HTTPS/FTP servers. The bits from both sources should match, except for things like timestamps, or because the sources are from slightly different points along branches. ### Building yourself -Getting sources and building a release with build.sh is not special for evbarm. However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one. The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH. build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH. The third line uses an alias and is equal to the second in effect, for RPI2/3. +Getting sources and building a release with build.sh is not special for evbarm. However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one each. The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH. build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH. The third line uses an alias and is equal to the second, for RPI2/3. Note that the aliases start with "evb" while the MACHINE_ARCH values do not, and that aliases have "-el" or "-eb", while the MACHINE_ARCH values have no suffix or "eb". - ./build.sh -m evbarm -a earmv6hf -u release - ./build.sh -m evbarm -a earmv7hf -u release - - ./build.sh -m earmv7hf-el -u release + - ./build.sh -m evbearmv7hf-el -u release -Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values on the same system; see build.sh. +Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values for a MACHINE; see build.sh. Use something like "evbarm-earmv7hf", so that 1) earvm6 and earmv7 don't collide and 2) anita will recognize it as a type of evbarm. ### NetBSD autobuild HTTPS/FTP servers -NetBSD provides nightly builds on [nyftp.netbsd.org](https://nyftp.netbsd.org/pub/NetBSD-daily/). These are equivalent to building yourself. The next directory level is the branch being built (netbsd-7, netbsd-8, HEAD, and more), plus optionally things like compiler type. It is followed by date/time, e.g. "HEAD/201811051650Z"; once a build is complete the symlink "latest" is adjusted to point to it. The next level is "${MACHINE}-${MACHINE_ARCH}", e.g. "evbarm-earmv7hf", and multiple combinations are provided. +NetBSD provides nightly builds on [nyftp.netbsd.org](https://nyftp.netbsd.org/pub/NetBSD-daily/). The next directory level is the branch being built (netbsd-7, netbsd-8, HEAD, and more), plus optionally things like compiler type. It is followed by date/time, e.g. "HEAD/201811051650Z"; once a build is complete the symlink "latest" is adjusted to point to it. The next level is "${MACHINE}-${MACHINE_ARCH}", e.g. "evbarm-earmv7hf", and multiple combinations are provided. + +An example URL, arguably the standard approach for first-time NetBSD/RPI users, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/ + +### release layout + +Once you get to the releasedir, self-built and autobuild releases have the same structure. - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that will run on any of the RPI boards. - - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that uses the armv7 instruction set, and thus can run only on the Raspberry Pi 2/3, but is also faster than rpi.img. + - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that uses the armv7 instruction set, and thus can run only on the RPI2 and RPI3 (and perhaps the CM3). It also supports systems other than the RPI family. -An example URL, arguably the standard approach for beginners, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/ +\todo Explain why there is no armv7_inst.gz. ## Preparing a uSD card @@ -138,6 +155,14 @@ 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) +## Configuring 802.11 + +After installation, the Ethernet will function as on any other NetBSD system; simply enable dhcpcd or configure a static address. USB WiFi devices will also function as on any other NetBSD system; in addition to dhcpcd or static, configure and enable wpa_supplicant. + +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. In particular, the following are known to work: + + - urtwn0: Realtek (0xbda) 802.11n WLAN Adapter (0x8176), rev 2.00/2.00, addr 5, MAC/BB RTL8188CUS, RF 6052 1T1R + ## Links The following pages have been published by NetBSD community members. (Note that some of them are old.) @@ -169,6 +194,10 @@ A section below describes the process of \todo Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec). Explain how to update a system (presumably /boot) from either an installed system's new firmware files, or the source tree. Explain any particular cautions. +Probably, for the RPI3B+, one needs to use -current, or use -8 with firmware from -current. \todo Defuzz. + +\todo Explain if using updated firmware from one branch (e.g. netbsd-current) on a system using a different branch (e.g. netbsd-8) is safe. Explain if pullups are done to release branches with new firmware. + ## 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. @@ -182,23 +211,9 @@ An alternate approach is to have the boo A third approach, workable on the Pi 3 only, is to configure USB host booting (already enableed on the 3+; see the upstream documentation) and have the boot partition also on the external device. In this case the external device must have an MBR because the hardware's first-stage boot does not have GPT support. In theory the [procedure to program USB host boot mode](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md) will function on a NetBSD system because the programming is done by bootcode.bin. \todo Confirm that putting program_usb_boot_mode=1 in config.txt and booting works to program the OTP bit. Confirm that one can then boot NetBSD from external USB. -\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. - -# Wireless Networking - -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. +There is no well-defined USB enumeration order, so the preferred approach if one has multiple USB mass storage devices is to use named wedges in both fstab and cmdline.txt. - - A Realtek 802.11n USB adaptor configures as urtwn(4). - - Configure with wpa_supplicant in /etc/rc.conf - - - ifconfig_urtwn0=dhcp - dhcpcd=YES - dhcpcd_flags="-q -b" - wpa_supplicant=YES - wpa_supplicant_flags="-B -i urtwn0 -c /etc/wpa_supplicant.conf" - - A sample wpa_supplicant.conf can be found at /usr/share/examples/wpa_supplicant/wpa_supplicant.conf - -# GPU +# X11 and GPU ## Video playback Accelerated video playback is supported in NetBSD 7 with the [OMXPlayer](http://pkgsrc.se/multimedia/omxplayer) application and through GStreamer with the [omx](http://pkgsrc.se/multimedia/gst-plugins1-omx) plugin. @@ -250,5 +265,12 @@ New firmware should pass all of the foll - Serial/framebuffer console - CPU frequency scaling -Tests shoudl be run on all of `rpi[0123]`. +Tests should be run on all of `rpi[0123]`. + +## Testing with anita and qemu + +anita has support for evbarm. Install qemu and dtb-arm-vexpress from pkgsrc. Note that the release subdirectory should be evbarm-earmv6hf or evbarm-earmv7hf. +\todo Explain how to select various RPI models to emulate. +\todo Explain about how DTB works. +\todo Give a command line example to run qemu (without anita).