--- wikisrc/ports/evbarm/raspberry_pi.mdwn 2018/11/06 18:16:43 1.100 +++ wikisrc/ports/evbarm/raspberry_pi.mdwn 2018/11/07 14:47:51 1.111 @@ -1,8 +1,8 @@ [[!meta title="NetBSD/evbarm on Raspberry Pi"]] -This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported. +This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are supported. We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page. -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.) +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 later, but note that everyone uses 8 or -current.) [[images/raspberrypi.jpg]] @@ -12,12 +12,11 @@ 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) - - multiple processors on 2/3 + - RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth) + - RPI0 and RPI0W are expected to work (without WiFi, and one needs fdt files \todo where from?) + - multiple processors on RPI2/RPI3 - boots normally to multiuser, with FAT32 boot partition on uSD - root filesystem can be uSD or USB-attached mass storage - serial or graphics console (with EDID query / parsing) @@ -34,29 +33,37 @@ Initial, limited, Raspberry Pi support w ## NetBSD current - - Raspberry Pi 3 builtin bluetooth - - Raspberry Pi 3 new SD host controller driver + - RPI3+ + - RPI3 builtin bluetooth + - RPI3 new SD host controller driver + +## What needs documenting if it works + + - CM1 + - CM3 + - CM3lite ## What needs work - USB (host); isochronous transfers. - - Raspberry Pi 3 builtin WiFi + - RPI3, RPI0W builtin WiFi + - RPI0W Bluetooth Low Energy (probably) # CPU types - - Raspberry Pi 1 uses "earmv6hf". - - Raspberry Pi Zero uses "\todo". - - Raspberry Pi 2 uses "earmv7hf". - - Raspberry Pi 3 uses "earmv7hf". - - Raspberry Pi Zero W uses "\todo". + - RPI1 uses "earmv6hf". + - RPI0 uses "earmv6hf". + - RPI0W uses "earmv6hf". + - RPI2 uses "earmv7hf". + - RPI3 uses "earmv7hf". -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. +Note that one can run a build of earmv6hf on the 2 and 3. There will still be a kernel7, built to use the 2/3 hardware, but with the armv6 instruction set. -\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.) +In theory the code compiled for earmv7hf will be faster, but anecdotal experience is that it doesn't matter that much. -\todo Explain if systems built with earm or earmv5 will work on RPI or RPI2/3. +While the evbarm port has "eb" variants (for big-endian mode), the RPI systems do not support eb and these variants will not work. Systems built with older CPU architectures (earm, earmv4, earmv5) are not expected to work on RPI. -See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode. +See also [[NetBSD/aarch64|aarch64]] for running the RPI2-1.2 and RPI3/RPI3+ in 64-bit mode. # Installation @@ -100,13 +107,13 @@ An example URL, arguably the standard ap 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. + - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that uses the armv7 instruction set, and thus can run only on the RPI2 and RPI3 (and perhaps the CM3). It also supports systems other than the RPI family. \todo Explain why there is no armv7_inst.gz. ## Preparing a uSD card -Once you have rpi.img.gz (or rpi_inst), put it on a uSD card using gunzip and dd, for example: +Once you have rpi.img.gz (or rpi_inst for earmv6 boards), put it on a uSD card using gunzip and dd, for example: - gunzip rpi.img.gz - dd if=rpi.img of=/dev/disk1 @@ -119,7 +126,7 @@ The standard approach is to use a USB ke By default the rpi.img is set to use the HDMI output. If you wish to use a serial console, mount the FAT32 partition on another system and edit cmdline.txt and remove '"console=fb"'. - - Most (all?) USB-to-TTL serial adapters have wires for Tx, Rx and ground, and not RTS/CTS or other flow control lines. Thus, your terminal program (or terminal) must be configured to not require flow control; a symptom of misconfiguration is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none". + - Most (all?) USB-to-TTL serial adapters have wires for TX, RX and ground, and not RTS/CTS or other flow control lines. Thus, your terminal program (or terminal) must be configured to not require flow control; a symptom of misconfiguration 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". @@ -137,7 +144,7 @@ build.sh (and hence the FTP site) also c - Use ssh to login to the address you found with user "sysinst", and password "netbsd". - When installing, ensure that you enable DHCP and ssh, so that you can log in again after the system is installed. -\todo Verify that the above is accurate and sufficient. +The rpi_inst.img.gz image will only work for systems that use earmv6hf kernels (so not RPI2/3). See [this port-arm message](https://mail-index.netbsd.org/port-arm/2017/08/18/msg004374.html) for details. ## Installation via ebijun's image @@ -188,6 +195,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. +Probably, for the RPI3+, one needs to use -current, or use -8 with firmware from -current. \todo Defuzz. + \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 @@ -203,14 +212,10 @@ An alternate approach is to have the boo 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. \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. -\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. +There is no well-defined USB enumeration order, so the preferred approach if one has multiple USB mass storage devices is to use named wedges in both fstab and cmdline.txt. # X11 and GPU -## Console font - -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. @@ -265,8 +270,6 @@ 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. +See the anita section in the evbarm page. -\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). +It is not currently known how to emulate a RPI in qemu, and therefore anita does not yet have support for this. \todo Add a command-line example to run qemu emulating some RPI model.