Diff for /wikisrc/ports/evbarm/raspberry_pi.mdwn between versions 1.27 and 1.77

version 1.27, 2015/01/29 21:28:16 version 1.77, 2018/10/30 14:35:31
Line 1 Line 1
 [[!meta title="NetBSD/evbarm on Raspberry Pi"]]  [[!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.
   
   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.)
   
 [[images/raspberrypi.jpg]]  [[images/raspberrypi.jpg]]
   
 [[!toc levels=2]]  [[!toc levels=2]]
   
 This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org).  
   
 <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>  <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
   
   # What works (and what doesn't yet)
   
   ## NetBSD 7 and NetBSD 8
   
    - RaspberryPi 1, 2, 3 (except Pi 3 builtin WiFi and bluetooth)
    - multiple processors on 2/3
    - 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)
    - X11 via HDMI
    - GPU (VCHIQ) - 3D and video decode. man page missing.
    - USB host controller - dwctwo(4) and most devices work
    - USB Ethernet - usmsc(4)
    - DMA controller driver and sdhc(4) support
    - RNG
    - Audio: works. man page missing.
    - GPIO
    - I²C: works, could use enhancements, man page
    - SPI: could use enhancements, man page
   
   ## NetBSD current
   
    - Raspberry Pi 3 builtin bluetooth
    - Raspberry Pi 3 new SD host controller driver
   
   ## What needs work
   
    - USB (host); isochronous transfers.
    - Raspberry Pi 3 builtin WiFi
   
   # CPU types
   
    - Raspberry Pi 1 uses "earmv6hf".
    - Raspberry Pi 2 uses "earmv7hf".
    - Raspberry Pi 3 uses "earmv7hf".
   
   Note that one can run earmv6hf code on the 2 and 3.  See also
   [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.
   
 # Installation  # Installation
  - You may use the rpi.img file created by an evbarm build - evbarm-earmv6hf is recommended.  
    - The Raspberry Pi port will be part of the NetBSD 7 stable release,  
      but you may want to use the HEAD branch for the latest development code.  
    - The automatic nightly builds can be found in the 'evbarm-earmv6hf/binary/gzimg/' directory under on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  
      - The HEAD/current build will be under HEAD/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/  
      - The stable build will be under netbsd-7/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'  
    - <i>gunzip and dd</i> this img to your sd card.  
   
            dd if=rpi.img of=/dev/disk1  ## SD card structure
   
   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.
   
   The NetBSD kernel will then use the FFS partition as the root filesystem.
   
   A 2 GB card is the smallest workable size.  The NetBSD filesystem will be expanded to fit.
   
   ## Choosing a version
   
   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.
   
  - Using a serial console  See also "ebijun's image", below, which is NetBSD-current and includes packages.
    - 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"'  ## Getting bits to install
   
  - Growing the root file-system  You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers.
    - 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.  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.
   
    - At the partition> prompt type "A" and press return.  ### Building yourself
   
            Adjust disklabel sector from 4194304 to 62333952 [n]?  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):
            Type "y" and press return.  
   
    - partition> prompt type "a" and press return.   - ./build.sh -m earmv6hf -u release
    - ./build.sh -m evbarm -a earmv6hf -u release
    - ./build.sh -m evbarm -a earmv7hf -u release
   
            Filesystem type prompt, press return to use the current value (4.2BSD).  ### NetBSD FTP servers
            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.  NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.
   
            Confirm this choice by typing "y" at the Label disk prompt.   - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
            Type "Q" and press return to quit disklabel.   - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2/3.
    - 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)    
    - 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/)
    - 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/)
   
    - At the # prompt (shell), type  ## Preparing a uSD card
   
            fsck -fy /dev/rld0a  Once you have rpi.img.gz (or rpi_inst), put it on a uSD card using gunzip and dd, for example:
            resize_ffs -y /dev/rld0a  
   
    - This may take a few minutes, be patient!   - gunzip rpi.img.gz
    - dd if=rpi.img of=/dev/disk1
   
            fsck -fy /dev/rld0a  ### Serial Console
            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  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
            fill the SD card.  edit cmdline.txt and remove '"console=fb"'.
   
 # Installation with sshramdisk image   - 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".
  - You may use the  rpi_inst.img.gz file created by an evbarm build.  
  - Connect Ethernet Cable to RPI.     In Kermit, the command is "set flow none".
   
      In minicom, run "minicom -s" and set hardware flow control to "no"
   
   ### Enabling ssh
   
   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.
   
   ### Installation with sshramdisk image
   
   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:
   
    - Ensure that you have a lan with a DHCP server.
    - Connect an Ethernet cable from the RPI to the LAN.
  - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".   - 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     - 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     - Also for after the sysinst is done and the system reboots
  - sysinst started!   - sysinst started!
   
 # Updating the firmware  ## Installation via ebijun's image
  - [rpi firmware files](https://github.com/raspberrypi/firmware/tree/master/boot)  
    - Copy all files except 'kernel*.img' into /boot and reboot  As an alternative to the standard installation images, Jun Ebihara
   provides an install image for Raspberry Pi that includes packages.  It
   is based on NetBSD-current and is built for earmv6hf, and thus will
   work on Raspberry Pi 1, 2 and 3.  This image is typically updated
   every few weeks.
   
    - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
   
   # Maintaining a system
   
   ## 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.img" (for current) or "netbsd.bin" (for 7 and 8) kernel that is in a format that the Raspberry can boot.
    - 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)
    - reboot
   
   ## Updating the firmware
   
   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.
   
   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.
   
   ## Booting
   
   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.
   
   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.
   
   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.
   
   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.
   
   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 be configured via fdisk because the hardware's first-stage boot does not have GPT support.   \todo Explain if this has been observed to work.
   \todo Explain if the [[procedure to program USB host boot mode|https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md]] can function under NetBSD; the examples on the web use Raspbian.
   \todo Explain if there is any way to run vcgencmd on NetBSD.
   
   \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.
   
 # Wireless Networking  # Wireless Networking
   
   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.
   
  - A Realtek 802.11n USB adaptor configures as urtwn(4).   - A Realtek 802.11n USB adaptor configures as urtwn(4).
    - Configure with wpa_supplicant in /etc/rc.conf -     - Configure with wpa_supplicant in /etc/rc.conf -
   
Line 97  This page attempts to document and coord Line 186  This page attempts to document and coord
 # GPU  # GPU
   
 ## Video playback  ## Video playback
 Accelerated video playback is supported in NetBSD 7 with the [OMXPlayer](http://pkgsrc.se/multimedia/omxplayer) application.  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.
   
 ## OpenGL ES  ## OpenGL ES
 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.  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.
   
 ### Quake 3  ## Quake 3
 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:  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:
   
  - pak0.pk3 from Quake 3 CD   - pak0.pk3 from Quake 3 CD
  - additional pak files from http://ioquake3.org/extras/patch-data/   - additional pak files from the [games/ioquake3-pk3](http://pkgsrc.se/games/ioquake3-pk3) package
  - read/write permissions on /dev/vchiq and /dev/wsmouse   - read/write permissions on /dev/vchiq and /dev/wsmouse
   
 Place the .pk3 files in ~/.q3a/baseq3 and ~/.q3a/missionpack directories.  Place the pak0.pk3 file in the /usr/pkg/lib/ioquake3/baseq3 directory.
   
 # Additional links  ## RetroArch / Libretro
  - [ARM userland utilities](https://github.com/jaredmcneill/userland)  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:
   
 # What works in -current   - Install [emulators/retroarch](http://pkgsrc.se/emulators/retroarch)
  - multi-user boot with root on SD card   - 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).
  - serial or graphics console (with EDID query / parsing)   - Plug in a USB HID compatible Gamepad, such as the Logitech F710 in "DirectInput" mode (set "D/X" switch to "D").
  - DMA controller driver and sdhc(4) support   - Create a config file for your gamepad using *retroarch-joyconfig*.
  - Audio: works. man page missing.  [[!template  id=programlisting text="""
  - I²C: works, could use enhancements, man page  $ retroarch-joyconfig -o gamepad.cfg
  - GPIO  """]]
  - RNG   - Launch the emulator from the command-line (no X required):
  - SPI: could use enhancements, man page  [[!template  id=programlisting text="""
  - VCHIQ: man page missing.  $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
  - USB (host) - dwctwo(4)  """]]
  - USB Ethernet - usmsc(4)  
  - X windows.  # Developer notes
   
   These notes are for people working on improvements to RPI support in NetBSD.
   
   ## Updating the firmware version in the NetBSD sources
   
   (Note that trying new firmware may result in a non-bootable system, so
   be prepared to recover the bootable media with another system.)
   
   Upstream firmware releases are
   [on GitHub](https://github.com/raspberrypi/firmware/releases).
   Copy all files except `kernel*.img` into `/boot` and reboot.
   
   New firmware should pass all of the following tests before being committed to NetBSD.
   
   - Audio
   - OMXPlayer (and [[!template id=man name="vchiq"]])
   - Serial/framebuffer console
   - CPU frequency scaling
   
   Tests shoudl be run on all of `rpi[0123]`.
   
 # What needs work  
  - USB (host); isochronous transfers.  

Removed from v.1.27  
changed lines
  Added in v.1.77


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb