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.11",
        "P8.12",
        "P8.13",    /* EHRPWM2B */
        "P8.13",
        "P8.14",
        "P8.15",
        "P8.16",
        "P8.17",
        "P8.18",
        "P8.19",    /* EHRPWM2A */
        "P8.26",
        "P8.27",
        "P9.11",    /* UART4_RX */
        "P9.12",
        "P9.13",    /* UART4_TX */
        "P9.14",    /* EHRPWM1A  */
        "P9.15",
        "P9.16",    /* EHRPWM1B  */
        "P9.21",    /* EHRPWM0A  */
        "P9.22",    /* EHRPWM0B  */
        "P9.23",
        "P9.25",
        "P9.27",
        "P9.28",
        "P9.29",
        "P9.30",
        "P9.31",
        *"P9.42",*
        /* the hardware ip uses */
        "uart4",
        "ehrpwm0A",
        "ehrpwm0B",
        "ehrpwm1A",
        "ehrpwm1B",
        "ehrpwm2A",
        "ehrpwm2B";

On Wed, Oct 12, 2016 at 6:37 PM, William Hermans <yyrk...@gmail.com> wrote:

> 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 <yyrk...@gmail.com>
> wrote:
>
>> 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 binary, that enabled several GPO's 6 GPI's, and all 3 "dual
>> channel" pwm modules. Plus I think uart4. The overlay fails to load at boot
>> via /boot/uEnv.txt.
>>
>> william@beaglebone:~$ dmesg |grep controller
>> [    0.000000] Kernel command line: console=tty0 console=ttyO0,115200n8
>> bone_capemgr.enable_partno=controller root=/dev/mmcblk0p1 rootfstype=ext4
>> rootwait coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
>> . . .
>> [    2.167008] IPv6: Loaded, but administratively disabled, reboot
>> required to enable
>> [    2.426546] bone_capemgr bone_capemgr: enabled_partno PARTNO
>> 'lcontroller' VER 'N/A' PR '0'
>> [    2.426586] bone_capemgr bone_capemgr: slot #4: 'Override Board
>> Name,00A0,Override Manuf,controller'
>> [    3.437016] bone_capemgr bone_capemgr: loader: failed to load slot-4
>> controller:00A0 (prio 0)
>>
>>
>>
>> I have tried this with cape_universal=enable, as well as commented out(
>> simply removed the text ).
>>
>> william@beaglebone:~$ uname -r
>> 4.4.14-ti-r34
>> william@beaglebone:~$ cat /etc/dogtag
>> BeagleBoard.org Debian Image 2016-05-01
>> william@beaglebone:~$ dtc -v
>> Version: DTC 1.4.1
>>
>> So here is the funny part.
>>
>> william@beaglebone:~$ sudo config-pin overlay controller
>> [sudo] password for william:
>> Loading led-controller overlay
>>
>> william@beaglebone:~$ dmesg |grep controller
>> [    0.000000] Kernel command line: console=tty0 console=ttyO0,115200n8
>> bone_capemgr.enable_partno=controller root=/dev/mmcblk0p1 rootfstype=ext4
>> rootwait coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
>> [    2.426546] bone_capemgr bone_capemgr: enabled_partno PARTNO
>> 'controller' VER 'N/A' PR '0'
>> [    2.426586] bone_capemgr bone_capemgr: slot #4: 'Override Board
>> Name,00A0,Override Manuf,controller'
>> [    3.437016] bone_capemgr bone_capemgr: loader: failed to load slot-4
>> controller:00A0 (prio 0)
>> [ 1972.395048] bone_capemgr bone_capemgr: part_number 'controller',
>> version 'N/A'
>> [ 1972.395115] bone_capemgr bone_capemgr: slot #5: 'Override Board
>> Name,00A0,Override Manuf,controller'
>> [ 1972.526297] bone_capemgr bone_capemgr: slot #5: dtbo
>> 'controller-00A0.dtbo' loaded; overlay id #0
>>
>>
>>
>> Is this a known issue ? Or maybe I'm doing something wrong ? Maybe I need
>> a different board file loaded at boot ?
>>
>> william@beaglebone:~$ cat /boot/uEnv.txt
>> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
>>
>> uname_r=4.4.14-ti-r34
>> #uuid=
>> #dtb=
>>
>> ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)
>>
>> ##BeagleBone Black: HDMI (Audio/Video) disabled:
>> dtb=am335x-boneblack-emmc-overlay.dtb
>>
>> ##BeagleBone Black: eMMC disabled:
>> #dtb=am335x-boneblack-hdmi-overlay.dtb
>>
>> ##BeagleBone Black: HDMI Audio/eMMC disabled:
>> #dtb=am335x-boneblack-nhdmi-overlay.dtb
>>
>> ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
>> #dtb=am335x-boneblack-overlay.dtb
>>
>> ##BeagleBone Black: wl1835
>> #dtb=am335x-boneblack-wl1835mod.dtb
>>
>> ##BeagleBone Green: eMMC disabled
>> #dtb=am335x-bonegreen-overlay.dtb
>>
>> cmdline=coherent_pool=1M quiet cape_universal=enable ipv6.disable=1
>> #cmdline=ipv6.disable=1 quiet
>>
>> #In the event of edid real failures, uncomment this next line:
>> #cmdline=coherent_pool=1M quiet cape_universal=enable
>> video=HDMI-A-1:1024x768@60e
>>
>> ##Example v3.8.x
>> #cape_disable=capemgr.disable_partno=
>> #cape_enable=capemgr.enable_partno=
>>
>> ##Example v4.1.x
>> #cape_disable=bone_capemgr.disable_partno=
>> cape_enable=bone_capemgr.enable_partno=controller
>>
>> ##enable Generic eMMC Flasher:
>> ##make sure, these tools are installed: dosfstools rsync
>> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>>
>>
>> william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>>  0: PF----  -1
>>  1: PF----  -1
>>  2: PF----  -1
>>  3: PF----  -1
>>  5: P-O-L-   0 Override Board Name,00A0,Override Manuf,controller
>>
>>
>>
>> The overlay source file does have some aspects similar to the universal
>> IO overlays. dir-changable, init-hi/lo etc.
>>
>>
>>
>> --
>> 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 beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/408d8389-6999-4d06-8b60-21795c240e92%40googlegroups.com
>> <https://groups.google.com/d/msgid/beagleboard/408d8389-6999-4d06-8b60-21795c240e92%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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORocg8wFy9mXdn8jxiWwCf22HEM%3Dqj4VJM9pyPkr%2Bk08WQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to