Hi there,
A quick update on the recent image.
I managed to test it with the cape and right now, the Arduino isn't on the cape isn't reset and therefore the cape doesn't work.
The problem is with the gpio pins and setting them to the right mode. That has changed with the Linux kernel 3.8.
- Dominik
The 3.5 and newer BeagleBone kernels make use of Device Trees. A Device Tree is a text file which describes the layout of a machine, commonly the combination of a system-on-chip (SoC) and a board, so that the kernel can know at what addresses and on which buses hardware is located. The BeagleBone kernels make use of an extension called Capemgr which allows dynamic loading and unloading of device tree fragments both at compile time and from userspace post-boot. Learning about the Device Tree is very essential, if you wish to be able to manipulate pins and be able to use them as inputs/outputs. There is a short guide to it here (part-way down the page). In a nutshell, the device tree can be manipulated by creating a text 'fragment' file that can be converted into a .dtbo file using a program called dtc which is already installed on the BeagleBone Black. The .dtbo file can then be installed and uninstalled as desired. The procedures to install and uninstall are at that link:
echo cape-bone-name > $SLOTS to install, and
echo -<slotnum> > $SLOTS to uninstall, but read through the web page and comments section first to see what $SLOT is set to).
I still haven't wrapped my head around all of it yet.
Len,
Thanks for the links. Indeed, device tree overlays are the way to go. Just have to figure out how to set it up properly.
Will look into it tonight or tomorrow.
- Dominik
--
You received this message because you are subscribed to the Google Groups "OpenROV" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrov+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.