Simple way to setup an arm chroot for building packages for your arm devices. This is an alternative to cross-compiling where you are limited to only linking against the libs in your toolchain.
You can store the chroot wherever you like. I choose to store it in a disk-image which I mount to my filesystem.
| _____________ /\ ____________ | |
| /\_ _ __ ___ \ \/ / __ _ _ __ / |_ | |
| / /_)/ '__/ _ \ \ / / _` | '_ \| __| | |
| / ___/| | | (_) \ \/ / (_| | | | | |_ | |
| \/ |_| \___/ \__/ \__,_|_| |_|\__| |
Unlike your typical computer where you usually shutdown properly, I cannot rely on this during the use of my Raspberry Pi. If the Raspberry Pi is improperly shutdown too many times, data corruption in the file system leading to unbootable SD card may result. So we should use a read-only file system.
Full instructions and explanations are obtained from this link but you can run these commands directly. I modified some of the instructions for personal convenience.
Login with default username: alarm, password: alarm
#Optionally enable root over SSH. The rest of these instructions assume u are in root.
This document is research for the selection of a communication platform for robot-net.
The purpose of this component is to enable rapid, reliable, and elegant communication between the various nodes of the network, including controllers, sensors, and actuators (robot drivers). It will act as the core of robot-net to create a standardized infrastructure for robot control.
Requirements:
| //The source texture that will be transformed | |
| uniform sampler2D tex0; | |
| //The texture coordinate passed in from the vertex shader (the default luxe vertex shader is suffice) | |
| varying vec2 tcoord; | |
| //x: width of the texture divided by the radius that represents the top of the image (normally screen width / radius) | |
| //y: height of the texture divided by the radius representing the top of the image (normally screen height / radius) | |
| uniform vec2 sizeOverRadius; |
| #!/usr/bin/env python | |
| ''' | |
| Simple and functional REST server for Python (2.7) using no dependencies beyond the Python standard library. | |
| Features: | |
| * Map URI patterns using regular expressions | |
| * Map any/all the HTTP VERBS (GET, PUT, DELETE, POST) | |
| * All responses and payloads are converted to/from JSON for you |
Download this script and make it executable: https://gist.github.com/meatballhat/12997137db1a9394f39c
Invoke the script like so:
$ ./run-travis-docker-image image_name
where image_name is one of the travis_<name> images here: https://quay.io/organization/travisci
e.g. ./run-travis-docker-image python
| #!/bin/bash | |
| sudo mount -o remount,size=10G,noatime /tmp | |
| echo "Done. Please use 'df -h' to make sure folder size is increased." |
This explains how to setup for GitHub projects which automatically generates Doxygen code documentation and publishes the documentation to the gh-pages branch using Travis CI.
This way only the source files need to be pushed to GitHub and the gh-pages branch is automatically updated with the generated Doxygen documentation.
Get an account at Travis CI. Turn on Travis for your repository in question, using the Travis control panel.
To create a clean gh-pages branch, with no commit history, from the master branch enter the code below in the Git Shell. This will create a gh-pages branch with one file, the README.md in it. It doesn't really matter what file is uploaded in it since it will be overwritten when the automatically generated documentation is published to th
The new Raspberry Pi 3 released on 29 Feb 2016 has issues with its UART port as the pinout GPIO 14/15 on the pin header is now based on a low throughput mini-UART.
To understand the issue better than reading the wall of text below, you can see the talk I gave on this issue.
The actual hardware UART on the BCM2837 SoC has now been assigned to handle Bluetooth with the BCM43438 Wifi/Bluetooth chip. More details can be found here and here.
This mini-UART does not produce a stable baud rate as it fluctuates based on the Core clock speed whenever it rises or falls. The result is that the serial debug output is practically unusable. On Raspbian you may see garbage or nothing at all. The solution is simple, add core_freq=250 to /boot/config.txt to cap the core frequency to a constant value. This optio