Diff for /wikisrc/ports/evbarm/raspberry_pi.mdwn between versions 1.18 and 1.54

version 1.18, 2013/07/30 05:25:37 version 1.54, 2017/10/14 14:54:58
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.
   
 [[images/raspberrypi.jpg]]  [[images/raspberrypi.jpg]]
   
 This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org).  [[!toc levels=2]]
   
 <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 before July, 2017
   
    - RaspberryPi 1, and 2 (including SMP)
    - 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
    - GPIO
    - RNG
    - 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.
   
   ## NetBSD 7 after July, 2017 and NetBSD 8
   
    - Raspberry Pi 3 (excluding WiFi and bluetooth)
   
   ## NetBSD current
   
    - Raspberry Pi 3 bluetooth
    - Raspberry Pi 3 new SD host controller driver
   
   ## What needs work
   
    - USB (host); isochronous transfers.
    - WiFi
   
 # Installation  # Installation
  - Use the latest HEAD/-current which builds for install  
    - As the raspberry pi port is still not part the stable release, you will want to use the   - 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 are part of the NetBSD 7 release.
      HEAD branch to download installation sets.      - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
    - You may use the rpi.img file created by an arm build.      - The 'evbarm-earmv7hf/binary/gzimg/' directory, as of August 6th 2015, contains an armv7.img file that is optimized for Raspberry Pi 2.
    - An example can be found in the '/evbarm/binary/gzimg/' directory under releng.netbsd.org      - 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/)
      - On nyftp.netbsd.org/pub/NetBSD-daily/HEAD/YYYYMMDDHHMMZ (it will look like pub/NetBSD-daily/HEAD/201305220150Z)      - 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/)
    - 'obj/releasedir/evbarm/binary/gzimg/' if you run (for example) './build.sh -m evbarm -u release'    - 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'
      - <i>gunzip and dd</i> this img to your sd card.     - <i>gunzip and dd</i> this img to your sd card. For example,
   
            dd if=rpi.img of=/dev/disk1             dd if=rpi.img of=/dev/disk1
   
  - Using a serial console   - Using a serial console
    - By default the rpi.img is set to use the HDMI output; to change mount rpi.img (it's a FAT filesystem)     - 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"'             edit cmdline.txt and remove '"console=fb"'
    - proceed with the 'dd'  
   
  - 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".
    - During the partitioning process, do not delete or format the  
      first MSDOS (FAT) partition, as the Raspberry pi firmware is        In Kermit, the command is "set flow none".
      hard coded to boot on the SDCAD / 1st MSDOS partition / Firmware  
      updates and boot loader.        In minicom, run "minicom -s" and set hardware flow control to "no"
    - 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.  ## Installation with sshramdisk image
    - Reboot, and at the prompt to enter the passname 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.  
   
 # Installation with sshramdisk image  
  - You may use the  rpi_inst.img.gz file created by an evbarm build.   - You may use the  rpi_inst.img.gz file created by an evbarm build.
  - Connect Ethernet Cable to RPI.   - Connect Ethernet Cable to RPI.
  - After starting DHCP client,SSH login to RPI with user "sysinst",passwd "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  ## Updating the kernel
  - [rpi firmware files](https://github.com/raspberrypi/firmware/tree/master/boot)  
    - Copy all files except 'kernel*img' into /boot and reboot  
   
 # Additional links   - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.
  - [ARM userland utilities](https://github.com/jaredmcneill/userland)  
   
 # What works           ...
  - multi-user boot with root on SD card           Kernels built from RPI2:
  - serial or graphics console (with EDID query / parsing)            /Users/feyrer/work/NetBSD/cvs/src-current/obj.evbarm-Darwin-XXX/sys/arch/evbarm/compile/RPI2/netbsd
  - X windows.           ...
  - USB (host); control, interrupt and bulk transfers. Has some stability issues that are being worked on. man page missing.  
  - USB Ethernet   - Besides the "netbsd" kernel in ELF format, there is also a "netbsd.bin" kernel that is in a format that the Raspberry can boot.
  - RNG: works   - 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)
  - I²C: works, could use enhancements, man page   - reboot
  - SPI: works, could use enhancements, man page  
  - VCHIQ: work in progress. man page missing. (-current)  # Wireless Networking
  - Audio: works. man page missing. (-current)  
     Note that the built-in WiFi in the RPI3 is not yet supported.
 # What needs work  
  - USB (host); isochronous transfers. DMA support.   - A Realtek 802.11n USB adaptor configures as urtwn(4).
  - DMA controller driver / dmover(9) backend     - Configure with wpa_supplicant in /etc/rc.conf -
  - Teach sdhc(4) about dmover; not Raspberry Pi specific  
  - hardfloat; not Raspberry Pi specific             ifconfig_urtwn0=dhcp
  - earm ABI; not Raspberry Pi specific             dhcpcd=YES
  - GPIO             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
   
   # GPU
   
   ## 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.
   
   ## 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.
   
   ## 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:
   
    - pak0.pk3 from Quake 3 CD
    - additional pak files from the [games/ioquake3-pk3](http://pkgsrc.se/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.
   
   ## RetroArch / Libretro
   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:
   
    - Install [emulators/retroarch](http://pkgsrc.se/emulators/retroarch)
    - 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).
    - 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*.
   [[!template  id=programlisting text="""
   $ retroarch-joyconfig -o gamepad.cfg
   """]]
    - Launch the emulator from the command-line (no X required):
   [[!template  id=programlisting text="""
   $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
   """]]
   
   # Developer notes
   
   These notes are for people working on improvements to RPI support in NetBSD.
   
   ## Updating the firmware
   
   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.

Removed from v.1.18  
changed lines
  Added in v.1.54


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