Diff for /wikisrc/ports/evbarm/raspberry_pi.mdwn between versions 1.48 and 1.63

version 1.48, 2017/04/21 14:48:31 version 1.63, 2017/10/22 00:39:08
Line 2 Line 2
   
 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 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.  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]]
   
Line 10  Initial, limited, Raspberry Pi support w Line 10  Initial, limited, Raspberry Pi support w
   
 <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
   
   # CPU types
   
   Note that one can also use code for earlier models on later models.
   
    - Raspberry Pi 1 uses "earmv6hf".
    - Raspberry Pi 2 uses "earmv7hf".
    - Raspberry Pi 3 uses "earmv7hf".  (NetBSD does not yet have 64-bit support.)
   
 # Installation  # Installation
  - 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'  
    - <i>gunzip and dd</i> this img to your sd card. For example,  
   
            dd if=rpi.img of=/dev/disk1  ## SD card structure
   
  - Using a serial console  The Raspberry Pi looks for firmware and a kernel on the first FAT32
    - 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)  partition of the uSD card.  The NetBSD kernel will then use the FFS
   partition as the root filesystem.
   
            edit cmdline.txt and remove '"console=fb"'  A 2 GB card is the smallest workable size.  The NetBSD filesystem will
   be expanded to fit on larger cards.
   
    - 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".  ## Choosing a version
   
       In Kermit, the command is "set flow none".  First, decide if you want to install a formal release (7.1), a stable
   branch build (netbsd-7, netbsd-8), or current.  Note that 7.1 predates
   Raspberry Pi 3 support.  For people who don't know how to choose among
   those, netbsd-8 is probably best.
   
       In minicom, run "minicom -s" and set hardware flow control to "no"  ## Getting bits to install
   
  - Growing the root file-system (**not required with NetBSD -current after 2015-04-07, or by NetBSD 7 after 2015-08-06**)  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.
            Type "y" and press return.  Pick a CPU type alias and pass it to build.sh with -m.  Examples:
    - ./build.sh -m earmv6hf -u release
    - ./build.sh -m evbarm -a earmv6hf -u release
    - ./build.sh -m evbarm -a earmv7hf -u release
   
    - partition> prompt type "a" and press return.  ### NetBSD FTP servers
   
            Filesystem type prompt, press return to use the current value (4.2BSD).  NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.
            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.   - 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 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/201710201440Z/evbarm-earmv6hf/binary/gzimg)    
    - The not-yet-released 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/)
   
            Confirm this choice by typing "y" at the Label disk prompt.  ## Installing to uSD
            Type "Q" and press return to quit disklabel.  
   
    - At the # prompt (shell), type  Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for example:
   
            fsck -fy /dev/rld0a   - gunzip rpi.img.gz
            resize_ffs -y /dev/rld0a   - dd if=rpi.i7mg of=/dev/disk1
   
    - This may take a few minutes, be patient!  ### Serial Console
   
            fsck -fy /dev/rld0a  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
            mount_msdos /dev/ld0e /boot  edit cmdline.txt and remove '"console=fb"'.
            mv /boot/cmdline.txt.orig /boot/cmdline.txt  
            reboot  
   
     - When the system comes back up, the root file-system will have been expanded to   - 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".
            fill the SD card.  
   
 # Installation with sshramdisk image     In Kermit, the command is "set flow none".
  - You may use the  rpi_inst.img.gz file created by an evbarm build.  
  - Connect Ethernet Cable to RPI.     In minicom, run "minicom -s" and set hardware flow control to "no"
   
   ### 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.  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
   
 You probably don't want to do this. Firmware updates can break things,  As an alternative to the standard installation images, Jun Ebihara
 and the latest firmware that's been tested is already included in the  provides an install image for Raspberry Pi that includes packages.  It
 NetBSD build you installed.  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
 If you're feeling adventurous (or are the port maintainer), here's what  every few weeks.
 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]`.   - [https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README](https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README)
   
 Upstream firmware releases are  ## Updating the kernel
 [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.   - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.
   
          ...           ...
Line 118  Copy all files except `kernel*.img` into Line 147  Copy all files except `kernel*.img` into
  - reboot   - reboot
   
 # Wireless Networking  # Wireless Networking
   
     Note that the built-in WiFi in the RPI3 is not yet supported.
   
  - 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 160  $ retroarch-joyconfig -o gamepad.cfg Line 192  $ retroarch-joyconfig -o gamepad.cfg
 $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc  $ retroarch --appendconfig gamepad.cfg -L /usr/pkg/lib/libretro/gambatte_libretro.so game.gbc
 """]]  """]]
   
 # What works (NetBSD 7.0+)  # Developer notes
  - 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.  
  - RaspberryPi 2 SMP  
   
 # What needs work  These notes are for people working on improvements to RPI support in NetBSD.
  - USB (host); isochronous transfers.  
   ## 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.48  
changed lines
  Added in v.1.63


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