1: [[!meta title="NetBSD/evbarm on Raspberry Pi"]]
3: This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.
5: 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.)
9: [[!toc levels=2]]
11: <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
13: # What works (and what doesn't yet)
15: ## NetBSD 7 and NetBSD 8
17: - RaspberryPi 1, 2, 3 (except Pi 3 builtin WiFi and bluetooth)
18: - multiple processors on 2/3
19: - boots normally to multiuser, with FAT32 boot partition on uSD
20: - root filesystem can be uSD or USB-attached mass storage
21: - serial or graphics console (with EDID query / parsing)
22: - X11 via HDMI
23: - GPU (VCHIQ) - 3D and video decode. man page missing.
24: - USB host controller - dwctwo(4) and most devices work
25: - USB Ethernet - usmsc(4)
26: - DMA controller driver and sdhc(4) support
27: - RNG
28: - Audio: works. man page missing.
29: - GPIO
30: - I²C: works, could use enhancements, man page
31: - SPI: could use enhancements, man page
33: ## NetBSD current
35: - Raspberry Pi 3 builtin bluetooth
36: - Raspberry Pi 3 new SD host controller driver
38: ## What needs work
40: - USB (host); isochronous transfers.
41: - Raspberry Pi 3 builtin WiFi
43: # CPU types
45: - Raspberry Pi 1 uses "earmv6hf".
46: - Raspberry Pi 0 uses "\todo".
47: - Raspberry Pi 2 uses "earmv7hf".
48: - Raspberry Pi 3 uses "earmv7hf".
49: - Raspberry Pi 0W uses "\todo".
51: Note that one can run earmv6hf code on the 2 and 3. See also
52: [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
54: # Installation
56: ## SD card structure
58: The Raspberry Pi looks for firmware and kernel.img on the first FAT32 partition of the uSD card. A separate kernel (kernel7.img) is used on RPI2 and RPI3.
60: The NetBSD kernel will then use the FFS partition as the root filesystem.
62: A 2 GB card is the smallest workable size. The NetBSD filesystem will be expanded to fit.
64: ## Choosing a version
66: 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.
68: See also "ebijun's image", below, which is NetBSD-current and includes packages.
70: ## Getting bits to install
72: You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers.
74: 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.
76: ### Building yourself
78: 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 a MACHINE value, but denote both MACHINE and a MACHINE_ARCH. The third line is an example (equal to the second in effect).
80: - ./build.sh -m evbarm -a earmv6hf -u release
81: - ./build.sh -m evbarm -a earmv7hf -u release
82: - ./build.sh -m earmv7hf-el -u release
84: Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values on the same system; see build.sh.
86: ### NetBSD FTP servers
88: NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/). These are equivalent to building yourself.
90: - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
91: - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2/3.
92: - 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)
93: - 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/)
94: - 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/)
96: ## Preparing a uSD card
98: Once you have rpi.img.gz (or rpi_inst), put it on a uSD card using gunzip and dd, for example:
100: - gunzip rpi.img.gz
101: - dd if=rpi.img of=/dev/disk1
103: ### Serial Console
105: By default the rpi.img is set to use the HDMI output. If you wish to use a serial console, first mount the FAT32 partition and then
106: edit cmdline.txt and remove '"console=fb"'.
108: - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
110: In Kermit, the command is "set flow none".
112: In minicom, run "minicom -s" and set hardware flow control to "no"
114: ### Enabling ssh
116: If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf. Besides having to find the IP address, you will have to wait for the partition resizing and reboot.
118: ### Installation with sshramdisk image
120: build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console. Note that this image is much smaller and that you will need to fetch the sets over the network. To use this method, write that image to a uSD card as above, and then:
122: - Ensure that you have a lan with a DHCP server.
123: - Connect an Ethernet cable from the RPI to the LAN.
124: - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".
125: - Be careful to note the ip address given during DHCP so you don't lose your connection
126: - Also for after the sysinst is done and the system reboots
127: - sysinst started!
129: ## Installation via ebijun's image
131: As an alternative to the standard installation images, Jun Ebihara
132: provides an install image for Raspberry Pi that includes packages. It
133: is based on NetBSD-current and is built for earmv6hf, and thus will
134: work on Raspberry Pi 1, 2 and 3. This image is typically updated
135: every few weeks.
137: - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
139: # Maintaining a system
141: ## vcgencmd
143: The program vcgencmd, referenced in the boot section, can be found in pkgsrc/misc/raspberrypi-userland.
145: ## Updating the kernel
147: - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.
150: Kernels built from RPI2:
154: - 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.
155: - 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)
156: - reboot
158: ## Updating the firmware
160: 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.
162: 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.
164: ## Booting
166: 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.
168: 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.
170: 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 / (and thus within the fdisk partition), but the arrangement used permits growing / on first boot, for the typical case where a larger uSD is used, compared to the minimum image size.
172: 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 greater space, part of the point is to avoid writing to the uSD card.
174: 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.
175: \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.
177: \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.
179: # Wireless Networking
181: 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.
183: - A Realtek 802.11n USB adaptor configures as urtwn(4).
184: - Configure with wpa_supplicant in /etc/rc.conf -
188: dhcpcd_flags="-q -b"
190: wpa_supplicant_flags="-B -i urtwn0 -c /etc/wpa_supplicant.conf"
191: - A sample wpa_supplicant.conf can be found at /usr/share/examples/wpa_supplicant/wpa_supplicant.conf
193: # GPU
195: ## Video playback
196: 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.
198: ## OpenGL ES
199: Accelerated OpenGL ES is supported in NetBSD 7. The GL ES client libraries are included with the [misc/raspberrypi-userland](http://pkgsrc.se/misc/raspberrypi-userland) package.
201: ## Quake 3
202: A Raspberry Pi optimized build of *ioquake3* is available in the [games/ioquake3-raspberrypi](http://pkgsrc.se/games/ioquake3-raspberrypi) package. To use it, the following additional resources are required:
204: - pak0.pk3 from Quake 3 CD
205: - additional pak files from the [games/ioquake3-pk3](http://pkgsrc.se/games/ioquake3-pk3) package
206: - read/write permissions on /dev/vchiq and /dev/wsmouse
208: Place the pak0.pk3 file in the /usr/pkg/lib/ioquake3/baseq3 directory.
210: ## RetroArch / Libretro
211: Using [emulators/retroarch](http://pkgsrc.se/emulators/retroarch) it is possible to run many emulators at full speed the Raspberry Pi. Emulator cores for various gaming consoles are available in the [emulators/libretro-*](http://pkgsrc.se/search.php?so=libretro-) packages. To begin using retroarch:
213: - Install [emulators/retroarch](http://pkgsrc.se/emulators/retroarch)
214: - Install the libretro core for the system you would like to emulate (lets take [emulators/libretro-gambatte](http://pkgsrc.se/emulators/libretro-gambatte), a GameBoy Color emulator, as an example).
215: - Plug in a USB HID compatible Gamepad, such as the Logitech F710 in "DirectInput" mode (set "D/X" switch to "D").
216: - Create a config file for your gamepad using *retroarch-joyconfig*.
217: [[!template id=programlisting text="""
218: $ retroarch-joyconfig -o gamepad.cfg
220: - Launch the emulator from the command-line (no X required):
221: [[!template id=programlisting text="""
222: $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
225: # Developer notes
227: These notes are for people working on improvements to RPI support in NetBSD.
229: ## Updating the firmware version in the NetBSD sources
231: (Note that trying new firmware may result in a non-bootable system, so
232: be prepared to recover the bootable media with another system.)
234: Upstream firmware releases are
235: [on GitHub](https://github.com/raspberrypi/firmware/releases).
236: Copy all files except `kernel*.img` into `/boot` and reboot.
238: New firmware should pass all of the following tests before being committed to NetBSD.
240: - Audio
241: - OMXPlayer (and [[!template id=man name="vchiq"]])
242: - Serial/framebuffer console
243: - CPU frequency scaling
245: Tests shoudl be run on all of `rpi`.
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb