File:  [NetBSD Developer Wiki] / wikisrc / ports / evbarm / raspberry_pi.mdwn
Revision 1.53: download - view: text, annotated - select for diffs
Sat Oct 14 14:53:46 2017 UTC (3 years, 6 months ago) by gdt
Branches: MAIN
CVS tags: HEAD
reorganize to focus more on users

    1: [[!meta title="NetBSD/evbarm on Raspberry Pi"]]
    2: 
    3: This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.
    4: 
    5: 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.
    6: 
    7: [[images/raspberrypi.jpg]]
    8: 
    9: [[!toc levels=2]]
   10: 
   11: <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
   12: 
   13: # What works
   14: 
   15: ## NetBSD 7 before July, 2017
   16: 
   17:  - RaspberryPi 1, and 2 (including SMP)
   18:  - multi-user boot with root on SD card
   19:  - serial or graphics console (with EDID query / parsing)
   20:  - DMA controller driver and sdhc(4) support
   21:  - Audio: works. man page missing.
   22:  - I²C: works, could use enhancements, man page
   23:  - GPIO
   24:  - RNG
   25:  - SPI: could use enhancements, man page
   26:  - GPU (VCHIQ) - 3D and video decode. man page missing.
   27:  - USB (host) - dwctwo(4)
   28:  - USB Ethernet - usmsc(4)
   29:  - X windows.
   30: 
   31: ## NetBSD 7 after July, 2017 and NetBSD 8
   32: 
   33:  - Raspberry Pi 3 (excluding WiFi and bluetooth)
   34: 
   35: ## NetBSD current
   36: 
   37:  - Raspberry Pi 3 bluetooth
   38:  - Raspberry Pi 3 new SD host controller driver
   39: 
   40: # What needs work
   41: 
   42:  - USB (host); isochronous transfers.
   43:  - WiFi
   44: 
   45: # Installation
   46: 
   47:  - 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.
   48:     - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
   49:     - The 'evbarm-earmv7hf/binary/gzimg/' directory, as of August 6th 2015, contains an armv7.img file that is optimized for Raspberry Pi 2.
   50:     - 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/)
   51:     - 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/)
   52:   - 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'
   53:    - <i>gunzip and dd</i> this img to your sd card. For example,
   54: 
   55: 	   dd if=rpi.img of=/dev/disk1
   56: 
   57:  - Using a serial console
   58:    - 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)
   59: 
   60: 	   edit cmdline.txt and remove '"console=fb"'
   61: 
   62:    - 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".
   63: 
   64:       In Kermit, the command is "set flow none".
   65: 
   66:       In minicom, run "minicom -s" and set hardware flow control to "no"
   67: 
   68: ## Installation with sshramdisk image
   69: 
   70:  - You may use the  rpi_inst.img.gz file created by an evbarm build.
   71:  - Connect Ethernet Cable to RPI.
   72:  - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".
   73:    - Be careful to note the ip address given during DHCP so you don't lose your connection
   74:    - Also for after the sysinst is done and the system reboots
   75:  - sysinst started!
   76: 
   77: ## Updating the kernel
   78: 
   79:  - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.
   80: 
   81:          ...
   82:          Kernels built from RPI2:
   83:           /Users/feyrer/work/NetBSD/cvs/src-current/obj.evbarm-Darwin-XXX/sys/arch/evbarm/compile/RPI2/netbsd
   84:          ...
   85: 
   86:  - Besides the "netbsd" kernel in ELF format, there is also a "netbsd.bin" kernel that is in a format that the Raspberry can boot.
   87:  - 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)
   88:  - reboot
   89: 
   90: # Wireless Networking
   91: 
   92:   Note that the built-in WiFi in the RPI3 is not yet supported.
   93: 
   94:  - A Realtek 802.11n USB adaptor configures as urtwn(4).
   95:    - Configure with wpa_supplicant in /etc/rc.conf -
   96: 
   97:            ifconfig_urtwn0=dhcp
   98:            dhcpcd=YES
   99:            dhcpcd_flags="-q -b"
  100:            wpa_supplicant=YES
  101:            wpa_supplicant_flags="-B -i urtwn0 -c /etc/wpa_supplicant.conf"
  102:    - A sample wpa_supplicant.conf can be found at /usr/share/examples/wpa_supplicant/wpa_supplicant.conf
  103: 
  104: # GPU
  105: 
  106: ## Video playback
  107: 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.
  108: 
  109: ## OpenGL ES
  110: 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.
  111: 
  112: ## Quake 3
  113: 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:
  114: 
  115:  - pak0.pk3 from Quake 3 CD
  116:  - additional pak files from the [games/ioquake3-pk3](http://pkgsrc.se/games/ioquake3-pk3) package
  117:  - read/write permissions on /dev/vchiq and /dev/wsmouse
  118: 
  119: Place the pak0.pk3 file in the /usr/pkg/lib/ioquake3/baseq3 directory.
  120: 
  121: ## RetroArch / Libretro
  122: 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:
  123: 
  124:  - Install [emulators/retroarch](http://pkgsrc.se/emulators/retroarch)
  125:  - 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).
  126:  - Plug in a USB HID compatible Gamepad, such as the Logitech F710 in "DirectInput" mode (set "D/X" switch to "D").
  127:  - Create a config file for your gamepad using *retroarch-joyconfig*.
  128: [[!template  id=programlisting text="""
  129: $ retroarch-joyconfig -o gamepad.cfg
  130: """]]
  131:  - Launch the emulator from the command-line (no X required):
  132: [[!template  id=programlisting text="""
  133: $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
  134: """]]
  135: 
  136: # Developer notes
  137: 
  138: These notes are for people working on improvements to RPI support in NetBSD.
  139: 
  140: ## Updating the firmware
  141: 
  142: You probably don't want to do this. Firmware updates can break things,
  143: and the latest firmware that's been tested is already included in the
  144: NetBSD build you installed.
  145: 
  146: If you're feeling adventurous (or are the port maintainer), here's what
  147: to test whenever you try new firmware:
  148: 
  149: - Audio
  150: - OMXPlayer (and [[!template id=man name="vchiq"]])
  151: - Serial/framebuffer console
  152: - CPU frequency scaling
  153: 
  154: That goes for all of `rpi[0123]`.
  155: 
  156: Upstream firmware releases are
  157: [on GitHub](https://github.com/raspberrypi/firmware/releases).
  158: Copy all files except `kernel*.img` into `/boot` and reboot.

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