FreeBSD 10.1-BETA3 SOEKRIS Image
Image file here.
Similar Posts
Building my own wireless point
I got interested in building my own wireless point after seeing some of the wireless firmware issues like this. Besides, I’ve always been interested in embedded devices and FreeBSD. So, the first step was a device. I chose to use a Wandboard. I’m a committer to Crochet-FreeBSD, so I built out the device support for…
The mystery of uart0
The FDT file for Raspberry Pi, declares UART. I’ve had quite a bit of trouble understanding how declaring a uart in the FDT results in /dev/tty0 and /dev/cuau0 appearing in /dev/ Here are the relevant lines from the FDT: uart0: uart0 { compatible = “broadcom,bcm2835-uart”, “broadcom,bcm2708-uart”, “arm,pl011”, “arm,primecell”; reg = <0x201000 0x1000>; interrupts = <65>;…
freebsd-arm-tools
I’ve had the opportunity to make some updates to the freebsd-arm-tools. If you’re interested in trying FreeBSD-current on a Raspberry Pi, I’ve posted a build at http://files.khubla.com/freebsd-raspberry-pi/ which has full Wifi and pf support. If you’re interested, the kernel configuration is here. Installing the FreeBSD on the Pi is simple. Firstly, get an image, such…
Building U-boot 2014 on FreeBSD
I’m upgrading the U-boot version used for Wandboard by Crochet-BSD. The first step is to upgrade the Device Tree Compiler (DTC); there are instructions here. Once you have the U-boot 2014 source, the build is trivial: gmake SED=gsed HOSTCC=cc CROSS_COMPILE=armv6-freebsd- wandboard_quad_config gmake SED=gsed HOSTCC=cc CROSS_COMPILE=armv6-freebsd-
Enabling i2c on FreeBSD Wandboard
FreeBSD-11 has support for i2c on Wandboard. The working boot image is here, and the boot log is here. In order to enable it, there were three steps Enable the kernel options Update the files.imx6 file Create the DTS mappings The kerne config for Wandboard-Quad is here, however, most of the kernel options for Wandboard…
Identifying unknown hardware a Pi running FreeBSD
I’ve been building FreeBSD-CURRENT images for my Pi, and I’ve noticed I have this: ugen0.5: <vendor 0x7392> at usbus0 So, it turns out I have one of these plugged in, and it seems likely that the unknown USB device is ugen0.5. So firstly, there is the question of “ugen”. You can read about it here….