Home » embedded

embedded

[-]

Cyclabile, a labile bike lane

by ao2, August 26, 2018
in

Cyclabile is an experiment about showing a moving bike lane on the road: the image moves according to the bike movement, producing the effect of riding on an actual bike lane, even when there isn't one.

The effectiveness of projecting an image on the paving instead of using a traditional light can be argued, of course.

For now the project purpose is more about having some fun and making a statement (there should be more bike lanes) rather than building an actual usable product.

Translations:
[-]

Linux Device-Tree and gpio-keys driver on BeagleBone Black

by ao2, July 13, 2018
in

I had to wire up a simple navigation keypad to a BeagleBone Black for a prototype, and I used the gpio-keys driver configured via a device tree overlay.

Translations:
[-]

Teclast X98 Air 3G: unbricking a Bay Trail tablet

by ao2, December 30, 2014
in

While I was trying to boot a vanilla linux kernel on the Teclast X98 Air 3G I messed up a bit with the UEFI firmware settings: the battery was not recognized anymore, the tablet was rebooting right after showing the UEFI firmware boot screen, and USB-host was not working either; so no keyboard for accessing the firmware menu to restore the default settings, and no ADB for running flashrom or the Intel FPT to reflash the firmware with.

Teclast X98 Air 3G, internals
Teclast X98 Air 3G, mainboard
ISP with a logic level converter, top
ISP with a logic level converter, angle
Translations:
[-]

Acer C110 pico projector with BeagleBone Black

by ao2, July 15, 2013
in

I was having a hard time getting the Acer C110 USB pico projector work when connected to the BeagleBone Black, it wasn't showing up on the USB bus at all, no sign of it in the kernel messages and consequently no sign of it in lsusb.

Projecting the Ångström login screen
Cable setup 1
Cable setup 2
Translations:
[-]

Neat compile/run cycle with git and OpenEmbedded

by ao2, May 27, 2010
in

No matter how much careful we are when writing code, whatever changes we are making to a piece of software we must test them before production, even Donald Knuth once said: Beware of bugs in the above code; I have only proved it correct, not tried it. :).

Moreover, if the software we are working on is targeting an embedded system and needs cross-compilation and depends on other software, then testing can be more tedious: we have to prepare patches/archives and instruct the target SDK to pick our latest code, or we could code directly in the SDK working tree, but that would not be very clean. If you use git and OpenEmbedded there is a very neat way to build directly from our own working directory on the filesystem.

Translations: