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, and 2 (including SMP)
18: - Raspberry Pi 3 (excluding WiFi and bluetooth)
19: - multi-user boot with root on SD card
20: - serial or graphics console (with EDID query / parsing)
21: - DMA controller driver and sdhc(4) support
22: - Audio: works. man page missing.
23: - I²C: works, could use enhancements, man page
24: - GPIO
25: - RNG
26: - SPI: could use enhancements, man page
27: - GPU (VCHIQ) - 3D and video decode. man page missing.
28: - USB (host) - dwctwo(4)
29: - USB Ethernet - usmsc(4)
30: - X windows.
32: ## NetBSD current
34: - Raspberry Pi 3 bluetooth
35: - Raspberry Pi 3 new SD host controller driver
37: ## What needs work
39: - USB (host); isochronous transfers.
40: - WiFi
42: # CPU types
44: Note that one can also use code for earlier models on later models.
46: - Raspberry Pi 1 uses "earmv6hf".
47: - Raspberry Pi 2 uses "earmv7hf".
48: - Raspberry Pi 3 uses "earmv7hf".
50: See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
52: # Installation
54: ## SD card structure
56: 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.
58: The NetBSD kernel will then use the FFS partition as the root filesystem.
60: A 2 GB card is the smallest workable size. The NetBSD filesystem will be expanded to fit.
62: ## Choosing a version
64: 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.
66: See also "ebijun's image", below, which is NetBSD-current and includes packages.
68: ## Getting bits to install
70: You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers.
72: 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.
74: ### Building yourself
76: Getting sources and building a release with build.sh is not special for evbarm. Pick a CPU type alias and pass it to build.sh with -m. Examples (the first two are equivalent):
78: - ./build.sh -m earmv6hf -u release
79: - ./build.sh -m evbarm -a earmv6hf -u release
80: - ./build.sh -m evbarm -a earmv7hf -u release
82: ### NetBSD FTP servers
84: NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/). These are equivalent to building yourself.
86: - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
87: - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2/3.
88: - 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)
89: - 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/)
90: - 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/)
92: ## Preparing a uSD card
94: Once you have rpi.img.gz (or rpi_inst), put it on a uSD card using gunzip and dd, for example:
96: - gunzip rpi.img.gz
97: - dd if=rpi.img of=/dev/disk1
99: ### Serial Console
101: 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
102: edit cmdline.txt and remove '"console=fb"'.
104: - 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".
106: In Kermit, the command is "set flow none".
108: In minicom, run "minicom -s" and set hardware flow control to "no"
110: ### Enabling ssh
112: 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.
114: ### Installation with sshramdisk image
116: 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:
118: - Ensure that you have a lan with a DHCP server.
119: - Connect an Ethernet cable from the RPI to the LAN.
120: - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".
121: - Be careful to note the ip address given during DHCP so you don't lose your connection
122: - Also for after the sysinst is done and the system reboots
123: - sysinst started!
125: ## Installation via ebijun's image
127: As an alternative to the standard installation images, Jun Ebihara
128: provides an install image for Raspberry Pi that includes packages. It
129: is based on NetBSD-current and is built for earmv6hf, and thus will
130: work on Raspberry Pi 1, 2 and 3. This image is typically updated
131: every few weeks.
133: - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
135: ## Updating the kernel
137: - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.
140: Kernels built from RPI2:
144: - 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.
145: - 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)
146: - reboot
148: ## Updating the firmware
150: 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.
152: 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.
154: # Wireless Networking
156: Note that the built-in WiFi in the RPI3 is not yet supported.
158: - A Realtek 802.11n USB adaptor configures as urtwn(4).
159: - Configure with wpa_supplicant in /etc/rc.conf -
163: dhcpcd_flags="-q -b"
165: wpa_supplicant_flags="-B -i urtwn0 -c /etc/wpa_supplicant.conf"
166: - A sample wpa_supplicant.conf can be found at /usr/share/examples/wpa_supplicant/wpa_supplicant.conf
168: # GPU
170: ## Video playback
171: 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.
173: ## OpenGL ES
174: 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.
176: ## Quake 3
177: 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:
179: - pak0.pk3 from Quake 3 CD
180: - additional pak files from the [games/ioquake3-pk3](http://pkgsrc.se/games/ioquake3-pk3) package
181: - read/write permissions on /dev/vchiq and /dev/wsmouse
183: Place the pak0.pk3 file in the /usr/pkg/lib/ioquake3/baseq3 directory.
185: ## RetroArch / Libretro
186: 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:
188: - Install [emulators/retroarch](http://pkgsrc.se/emulators/retroarch)
189: - 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).
190: - Plug in a USB HID compatible Gamepad, such as the Logitech F710 in "DirectInput" mode (set "D/X" switch to "D").
191: - Create a config file for your gamepad using *retroarch-joyconfig*.
192: [[!template id=programlisting text="""
193: $ retroarch-joyconfig -o gamepad.cfg
195: - Launch the emulator from the command-line (no X required):
196: [[!template id=programlisting text="""
197: $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
200: # Developer notes
202: These notes are for people working on improvements to RPI support in NetBSD.
204: ## Updating the firmware version in the NetBSD sources
206: (Note that trying new firmware may result in a non-bootable system, so
207: be prepared to recover the bootable media with another system.)
209: Upstream firmware releases are
210: [on GitHub](https://github.com/raspberrypi/firmware/releases).
211: Copy all files except `kernel*.img` into `/boot` and reboot.
213: New firmware should pass all of the following tests before being committed to NetBSD.
215: - Audio
216: - OMXPlayer (and [[!template id=man name="vchiq"]])
217: - Serial/framebuffer console
218: - CPU frequency scaling
220: Tests shoudl be run on all of `rpi`.
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb