--- wikisrc/ports/evbarm/raspberry_pi.mdwn 2018/11/06 13:59:57 1.91 +++ wikisrc/ports/evbarm/raspberry_pi.mdwn 2018/11/06 18:16:43 1.100 @@ -12,6 +12,8 @@ Initial, limited, Raspberry Pi support w # What works (and what doesn't yet) +\todo Add information on Pi Zero and Pi Zero W. + ## NetBSD 7 and NetBSD 8 - RaspberryPi 1, 2, 3 (except Pi 3 builtin WiFi and bluetooth) @@ -43,13 +45,18 @@ Initial, limited, Raspberry Pi support w # CPU types - Raspberry Pi 1 uses "earmv6hf". - - Raspberry Pi 0 uses "\todo". + - Raspberry Pi Zero uses "\todo". - Raspberry Pi 2 uses "earmv7hf". - Raspberry Pi 3 uses "earmv7hf". - - Raspberry Pi 0W uses "\todo". + - Raspberry Pi Zero W uses "\todo". + +Note that one can run earmv6hf userland code on the 2 and 3. In theory the code compiled for earmv7hf will be faster. \todo Benchmark and explain. \todo Explain if one can run the earmv6hf RPI2 kernel on RPI1. \todo Explain if the earmv6hf rpi.img.gz will run on a RPI2/3. + +\todo Explain if one can run "eb" variants. (However, using eb is likely to find more bugs because almost everyone uses el. That can either be a reason to run it or not run it.) -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. +\todo Explain if systems built with earm or earmv5 will work on RPI or RPI2/3. + +See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode. # Installation @@ -64,34 +71,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 Raspberry Pi 2/3. -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 +149,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 +188,8 @@ 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. +\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. @@ -184,21 +205,11 @@ A third approach, workable on the Pi 3 o \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 +# X11 and GPU -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. +## Console font - - 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 +Some find the default font to be too small. \todo Give a link to the normal instructions on how to change it. ## 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 +261,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).