I did a fresh install of the BBB console flasher from 3/27/16. I then updated to the 4.4.6-bone-rt-r6 kernel. I want to enable ADC, but I can't find it, so something like this in uEnv.txt doesn't do anything:
Am I overlooking a necessary step?
FWIW, there was no /lib/firmware in the image.
The console currently does not ship with the overlay objects:
sudo apt-get update
sudo apt-get install git-core
git clone https://github.com/beagleboard/bb.org-overlays
Thanks, Robert. Looks like I also need to get dtc installed:
/bin/sh: 1: /usr/bin/dtc-v4.1.x: not found
Makefile:134: recipe for target 'src/arm/BB-CAPE-DISP-CT4-00A0.dtbo' failed
make: *** [src/arm/BB-CAPE-DISP-CT4-00A0.dtbo] Error 127
Makefile:82: recipe for target 'all_arm' failed
make: *** [all_arm] Error 2
I have the following instructions for patching and installing dtc, but they are more than half a year old. Is there a better way or newer version?
$ git clone git://git.kernel.org/pub/scm/utils/dtc/dtc.git
$ cd dtc
$ git reset --hard f8cb5dd94903a5cfa1609695328b8f1d5557367f
$ wget https://patchwork.kernel.org/patch/1934471/raw/ -O dynamic-symbols.patch
$ git apply dynamic-symbols.patch
(warning about whitespace errors seems benign)
sudo apt-get install device-tree-compiler
it's patched to deal with our 4.1.x kernel..
Maybe I spoke too soon.
# dtc --version
Version: DTC 1.4.1
# dtc -O dtb -o MY-DTB-FILE-00A0.dtbo -b 0 -@ MY-DTB-FILE.dts
Error: MY-DTB-FILE.dts:1.1-2 syntax error
FATAL ERROR: Unable to parse input tree
The file starts with:
copy your dts into the bb.org-overlalys/src/arm directory..
Call make, sudo make install from the base directory of bb.org-overlays…
Okay, that works. Hopefully I can figure out how to compile a dts individually, but this'll do for now. Thanks!
I installed the overlays without problems on Debian 8.4 with kernel
4.4.5-bone5. Adding overlays works fine, but removing them fails with
an OOPS. I remember similar problems from the era of 3.x kernels, but
I thought it had been addressed long time ago. Does the problem still
persist, or is it an issue with my setup?
For now, still just reboot when you want to remove an overlay..
ok, thanks. I just wanted to make sure that I did not screw up something badly.