On Wednesday, December 7, 2016 at 9:33:22 PM UTC-5, RobertCNelson wrote:
>
> removing capes works in 1-5% of overlays...
>
> from /boot/uEnv.txt remove the cape_universal=enable and it'll come up
> with nothing on your next bootup..
>
> Regards,
> --
> Robert Nelson
> https://rcn-ee.com/
>
> OK, so let's say I have a version 4.4.30-ti-r64 kernel, and I get this after
> boot:
>
> debian@BBG2:/sys/devices/platform/bone_capemgr$ cat slots
> 0: PF -1
> 1: PF -1
> 2: PF -1
> 3: PF -1
> 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,cape-universal
>
>
On Monday, March 21, 2016 at 9:54:12 PM UTC-4, RobertCNelson wrote:
>
> We look at the eeprom:
>
>
> http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/am335x_evm.h;h=150c5235d230f597641bd8a8fbd8e4afa0fd16cd;hb=HEAD#l164
>
>
> Regards,
>
>
> --
> Robert Nelson
> https://rcn-ee.com/
I think that's a significant piece of info in understanding how the device
tree data structure works for the Beaglebones.
I've got several books on the Beaglebone + Google searching did not yield
an answer.
Thanks!
Greg
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You
On Mon, Mar 21, 2016 at 8:21 PM, Greg wrote:
> I am trying to learn how a Device Tree Blob is selected (BeagleBoneBlack)
> if:
>
> 1. No cape is plugged in.
> 2. All dtb and cape lines in uEnv.txt are commented.
>
> In other words a default set-up with no specific DTB
I am trying to learn how a Device Tree Blob is selected (BeagleBoneBlack)
if:
1. No cape is plugged in.
2. All dtb and cape lines in uEnv.txt are commented.
In other words a default set-up with no specific DTB or DTBO specified.
What is the process or data used for determining which DTB is