So I've been searching the groups here for the last several hours. I've
tried several things, even noted that the device tree "binary" file
(compiled file in /lib/firmware) was marked as executable. So I set the
executable bit via chmod -x . . .Anyway, this is a custom device tree
overlay binar
By the way, this has been tested consistently on one BBB RevC, and several(
tens ) of BBG's. By me personally, and another person, elsewhere.
On Wed, Oct 12, 2016 at 6:33 PM, William Hermans wrote:
> So I've been searching the groups here for the last several hours. I've
> tried several things,
Additional information if this helps. P9.42 if I recall is one of the pins
that are tied together for mmc_cmd ? So, kind of has my attention.
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P8.8",
"P8.9",
"P8.10",
"P8.
So, it turns out you *do* have to modify the initramfs image, in order to
load a custom overlay file at boot. The hook for /etc/default/capemgr does
not seem to be in place for the image I'm using. Which is fine since this
is just an init script anyhow, which I feel is the wrong way to do this.
Cal
I really dislike gmail / google groups sometimes . . . but I corrected the
problem and showed my worklog in the above mail for those of you using
gmail, it may 'hide' this information under the '...' are the top of the
post.
I've also been informed that Robert has a customization repo, for which o
William,
THANK YOU for doing this! :) I am finding this in Nov 2018 and your
solution is exactly what I'm looking for. I really appreciate you
documenting this. But yeah, Google Groups... lol. TBH I'm really
surprised I was able to find this!
Thanks again.
ST
--
For more options, visit h
