When writing Yocto recipes there are some common variables that can be used, espcially in the do_install() section An example of this would be: do_install() { install -d ${D}${bindir} install -m 0644 ${S}/my_program ${D}${bindir} } These variables are defined in… Read more
How to Set Up a Yocto Build Server as a Remote Package Repository
If you are using Yocto to create your embedded linux system, it can really useful to set your server up to act as a package repository. Setting up Assuming that you have set your local.conf to have PACKAGE_CLASSES ?= “package_ipk”… Read more
Setting a GPIO pin from the Device Tree on AM335x, OSD335x and Beaglebones
It seems like a common enough thing to want to do – set a GPIO pin high or low at boot. The first thing you will need to do is find the name of the GPIO pin you want to… Read more
Pinmux for Beaglebone Black, AM335x and OSD335x
I keep finding that I need to translate GPIO pin names and numbers depending on if I am talking to our hardware designer, writing DTBs or looking up solutions based on the BeagleBone Black. This normally involves looking up data… Read more
Compiling u-boot for the BeagleBone Black and Octavo Systems OSD335x
If you have created your own design based around the BeagleBone family, then one of the issues you may well encounter is trying to boot your board with u-boot with a blank EEPROM and the standard method of creating a… Read more
BeagleBone Black and OSD335x EEPROM during boot
There is a 32Kbit (4KB) EEPROM that is used by software such as u-boot to identify the board. If you have developed your own board, then the contents of the EEPROM will initially be blank, which can make life ‘interesting’,… Read more