This page attempts to document and coordinate efforts towards NetBSD/evbarm on Raspberry Pi. 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 image by Christopher Lee used under CC-By-2.0 license)
- The automatic nightly builds on nyftp.netbsd.org provide image files that can be used for installation. The Raspberry Pi and Pi 2 ports will be part of the NetBSD 7 release.
- 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, as of August 6th 2015, 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/201412161700Z/evbarm-earmv6hf/binary/gzimg/)
- The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201508062150Z/evbarm-earmv7hf/binary/gzimg/)
- You can build your own version of these images using (for example) './build.sh -m evbarm -a earmv6hf -u release', or './build.sh -m evbarm -a earmv7hf -u release'
gunzip and dd this img to your sd card. For example,
dd if=rpi.img of=/dev/disk1
Using a serial console
By default the rpi.img is set to use the HDMI output; to change to using a serial console first mount rpi.img (it's a FAT filesystem)
edit cmdline.txt and remove '"console=fb"'
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".
In Kermit, the command is "set flow none".
In minicom, run "minicom -s" and set hardware flow control to "no"
Growing the root file-system (not required with NetBSD -current after 2015-04-07, or by NetBSD 7 after 2015-08-06)
- During the partitioning process, do not delete or format the first MSDOS (FAT) partition, as the Raspberry pi firmware is hard coded to boot on the SDCAD / 1st MSDOS partition / Firmware updates and boot loader.
- Copy /boot/cmdline.txt to /boot/cmdline.txt.orig
- Edit /boot/cmdline.txt and add the '-s' flag to the end of the first line of text to boot into single-user mode.
- For the next steps, the root filesystem mustn't be mounted rw. So reboot, and at the prompt to enter the pathname of shell, press return for the default (/bin/sh).
At the # prompt, type
"disklabel -i ld0" and press return.
At the partition> prompt type "A" and press return.
Adjust disklabel sector from 4194304 to 62333952 [n]? Type "y" and press return.
partition> prompt type "a" and press return.
Filesystem type prompt, press return to use the current value (4.2BSD). Start offset prompt, press return to use the current value. Partition size prompt, type "$" and press return to grow the partition to use all available free space.
partition> prompt type "W" to save the changes to the disklabel.
Confirm this choice by typing "y" at the Label disk prompt. Type "Q" and press return to quit disklabel.
At the # prompt (shell), type
fsck -fy /dev/rld0a resize_ffs -y /dev/rld0a
This may take a few minutes, be patient!
fsck -fy /dev/rld0a mount_msdos /dev/ld0e /boot mv /boot/cmdline.txt.orig /boot/cmdline.txt reboot
When the system comes back up, the root file-system will have been expanded to fill the SD card.
- You may use the rpi_inst.img.gz file created by an evbarm build.
- Connect Ethernet Cable to RPI.
- After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".
- Be careful to note the ip address given during DHCP so you don't lose your connection
- Also for after the sysinst is done and the system reboots
- sysinst started!
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.
If you're feeling adventurous (or are the port maintainer), here's what to test whenever you try new firmware:
- OMXPlayer (and vchiq)
- Serial/framebuffer console
- CPU frequency scaling
That goes for all of
Upstream firmware releases are
Copy all files except
/boot and reboot.
Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.
... Kernels built from RPI2: /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.
- Depending on your hardware version, copy this either to /boot/kernel.img (old/V1 hardware) or to /boot/kernel7.img (new/V2 hardware)
- 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
Accelerated OpenGL ES is supported in NetBSD 7. The GL ES client libraries are included with the misc/raspberrypi-userland package.
A Raspberry Pi optimized build of ioquake3 is available in the games/ioquake3-raspberrypi package. To use it, the following additional resources are required:
- pak0.pk3 from Quake 3 CD
- additional pak files from the games/ioquake3-pk3 package
- read/write permissions on /dev/vchiq and /dev/wsmouse
Place the pak0.pk3 file in the /usr/pkg/lib/ioquake3/baseq3 directory.
Using 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-* packages. To begin using retroarch:
- Install emulators/retroarch
- Install the libretro core for the system you would like to emulate (lets take emulators/libretro-gambatte, a GameBoy Color emulator, as an example).
- Plug in a USB HID compatible Gamepad, such as the Logitech F710 in "DirectInput" mode (set "D/X" switch to "D").
- Create a config file for your gamepad using retroarch-joyconfig.
$ retroarch-joyconfig -o gamepad.cfg
- Launch the emulator from the command-line (no X required):
$ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
- multi-user boot with root on SD card
- serial or graphics console (with EDID query / parsing)
- DMA controller driver and sdhc(4) support
- Audio: works. man page missing.
- 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.
- RaspberryPi 2 SMP
- USB (host); isochronous transfers.