--- wikisrc/ports/evbarm/raspberry_pi.mdwn 2017/10/21 23:52:26 1.59 +++ wikisrc/ports/evbarm/raspberry_pi.mdwn 2017/10/22 00:39:08 1.63 @@ -52,6 +52,17 @@ Note that one can also use code for earl # Installation +## SD card structure + +The Raspberry Pi looks for firmware and a kernel on the first FAT32 +partition of the uSD card. 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 on larger cards. + +## Choosing a version + 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 @@ -62,8 +73,8 @@ those, netbsd-8 is probably best. You can either build a release yourself with build.sh, or get one from the NetBSD FTP servers. Both will provide rpi.img.gz and rpi_inst.img.gz. Each is an image to -be written to a uSD card, and it has a FAT32 partition for booting and -an FFS partition for NetBSD. +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. ### Building yourself @@ -85,26 +96,28 @@ NetBSD provides nightly builds on [nyftp ## Installing to uSD -Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for examples +Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for example: - - dd if=rpi.img of=/dev/disk1 + - gunzip rpi.img.gz + - dd if=rpi.i7mg of=/dev/disk1 ### Serial Console 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 edit cmdline.txt and remove '"console=fb"'. - - 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". + - 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". - In Kermit, the command is "set flow none". + In Kermit, the command is "set flow none". - In minicom, run "minicom -s" and set hardware flow control to "no" + 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: - - Connect Ethernet Cable to RPI. + - 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". - 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