--- wikisrc/ports/evbarm/raspberry_pi.mdwn 2015/03/29 21:32:29 1.39 +++ wikisrc/ports/evbarm/raspberry_pi.mdwn 2017/03/30 15:53:47 1.47 @@ -2,7 +2,7 @@ This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported. -Initial 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. +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. [[images/raspberrypi.jpg]] @@ -11,14 +11,13 @@ Initial Raspberry Pi support was introdu ([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license) # Installation - - You may use the rpi.img file created by an evbarm build - evbarm-earmv6hf is recommended. This isn't optimized for Raspberry Pi 2, but allows a single image to be used for all boards. - - The Raspberry Pi and Pi 2 ports will be part of the NetBSD 7 release. - - The automatic nightly builds can be found in the 'evbarm-earmv6hf/binary/gzimg/' directory on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/). - - The stable build will be under netbsd-7/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/ - - The HEAD/current build will be under HEAD/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/ - - For example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201412161700Z/evbarm-earmv6hf/binary/gzimg/ - - 'releasedir/evbarm/binary/gzimg/' if you run (for example) './build.sh -m evbarm -a earmv6hf -u release' - - gunzip and dd this img to your sd card. + - The automatic nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/) 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 @@ -27,7 +26,13 @@ Initial Raspberry Pi support was introdu edit cmdline.txt and remove '"console=fb"' - - Growing the root file-system + - 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 @@ -81,8 +86,36 @@ Initial Raspberry Pi support was introdu - sysinst started! # Updating the firmware - - [rpi firmware files](https://github.com/raspberrypi/firmware/tree/master/boot) - - Copy all files except 'kernel*.img' into /boot and reboot + +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: + +- Audio +- OMXPlayer (and [[!template id=man name="vchiq"]]) +- Serial/framebuffer console +- CPU frequency scaling + +That goes for all of `rpi[0123]`. + +Upstream firmware releases are +[on GitHub](https://github.com/raspberrypi/firmware/releases). +Copy all files except `kernel*.img` into `/boot` and reboot. + +# Updating the kernel + - 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) + - reboot # Wireless Networking - A Realtek 802.11n USB adaptor configures as urtwn(4). @@ -140,7 +173,7 @@ $ retroarch --appendconfig gamepad.cfg - - USB (host) - dwctwo(4) - USB Ethernet - usmsc(4) - X windows. + - RaspberryPi 2 SMP # What needs work - USB (host); isochronous transfers. - - MULTIPROCESSOR support for Raspberry Pi 2