By the way, Universal IO is disabled on both boards. On Wed, Apr 26, 2017 at 7:52 PM, William Hermans <[email protected]> wrote:
> So the image I'm using on two separate boards: > bone-debian-8.7-console-armhf-2017-04-02-1gb.img > > One board has uboot capes enabled, and they do function. The other board > is not using uboot overlays, but seems odd at times. > > So on both board inserting an overlay as such: root@wgd:~# echo BB-UART1 > > /sys/devices/platform/bone_capemgr/slots > > Causes the terminal session to hang directly after the command is issued. > The board is still operational, however after reiitializing an ssh session: > > root@wgd:~# cat /sys/devices/platform/bone_capemgr/slots > 0: ---l-- -1 > 1: ------ -1 > 2: ---l-- -1 > 3: ---l-- -1 > 4: --O--- -1 > > root@wgd:~# dmesg | tail > [ 18.436962] net eth0: initializing cpsw version 1.12 (0) > [ 18.436993] net eth0: initialized cpsw ale version 1.4 > [ 18.437003] net eth0: ALE Table size 1024 > [ 18.445166] net eth0: phy found : id is : 0x7c0f1 > [ 18.462196] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 121.758813] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - > flow control rx/tx > [ 121.758944] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > [346482.260850] bone_capemgr bone_capemgr: part_number 'BB-UART1', version > 'N/A' > [346482.260892] bone_capemgr bone_capemgr: slot #4: override > [346482.260910] bone_capemgr bone_capemgr: slot #4: auto loading handled > by U-Boot > > root@wgd:~# ls /dev |grep ttyO[0-4] > ttyO0 > > The cape is definitely not loading. The output from these commands here is > from the board that is loading overlays via uboot, but I am willing( I have > not checked yet ) the output would be identical on the board that does not > have uboot overlays enabled. Curiously, I did try the old method of loading > the overlay form uEnv.txt, and the overlay did not load correctly then > either. > > One thing of note which may *possibly* be the culprit. Is that I do not > have a board file for either of these loaded specifically. However on at > least the uboot overlay board I have hdmi video and audio both disabled > through the new uboot way. I have not checked if any of those pins conflict > with that overlay or not, because I have not looked. > > I'll make another post following this one to see how this overlay behaves > when i attempt to load via uboot overlays. > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beagleboard/1c0c6094-2b0a-4724-a434-1c6d043e608c%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/1c0c6094-2b0a-4724-a434-1c6d043e608c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpXDAQn9ZMB0PpRpsScXL-WTFNNZf8O360zjw1S%2BCNKtg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
