Hi @RobertCNelson

For our HW solution with BBBW we need to use pins in different setup as they are set in universal capes.

We are running with

debian@beaglebone:$ uname -a
Linux beaglebone 4.4.68-ti-r115 #1 SMP Sat Jul 29 21:04:28 UTC 2017 armv7l GNU/Linux
debian@beaglebone:$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.9 (jessie)
Release: 8.9
Codename: jessie
debian@beaglebone:~$ dtc --version
Version: DTC 1.4.4

The problem is that custom cape we created doesn't seems to work. Bellow will you find our cape code
I extracted this code out of universal cape, and modified it. I compiled it along with /opt/source/bb.org-overlays/ inside BBB, so I don't expect that the resulting dtbo is wrong

M2M_MUMA_PINS-00A0.txt

I tried to use our custom cape in /boot/uEnv.txt in

• cape_enable=bone_capemgr.enable_partno=
• dtb_overlay=

I tried to load it using config-pin utility, but none of these possibilities seems to work.

The goal is to have our custom "muma" mode preset. In pinctrl-names "muma" is mentioned

It seems that the cape is loaded, but just partially.
When I cat for pins status, I see the pins I would like to use (as they are present in our custom cape)
debian@beaglebone:~$ sudo cat /sys/devices/platform/ocp/ocp:cape-universal/status
0 P9_31 110 IN 0
1 P9_30 112 IN 0
2 P9_29 111 IN 0
3 P9_27 115 IN 0
4 P9_26 14 IN 0
5 P9_24 15 IN 0

When I query with config-pin -i/-l on particular pin, I don't see in the list our custom mode (muma).
In fact I see the "original" setup for all the pins

debian@beaglebone:$ config-pin -l P9.24
default gpio gpio_pu gpio_pd uart can i2c pru_uart pruin
debian@beaglebone:$ config-pin -i P9.24
Pin name: P9_24
Function if no cape loaded: gpio
Function if cape loaded: default gpio gpio_pu gpio_pd uart can i2c pru_uart pruin
Function information: gpio0_15 default gpio0_15 gpio0_15 gpio0_15 uart1_txd dcan1_rx i2c1_scl pr1_uart0_txd pr1_pru0_pru_r31_16
Cape: cape-universal cape-universala cape-universaln cape-universalh
Kernel GPIO id: 15
PRU GPIO id: 47

I would expect to see "default", "muma";

What am I doing wrong?

BR
Vladimir

Hi,

I applied overlays to beaglebone black but cannot use RS485 overlay.

When I try to make MODBUS communication with UART4, the RTS pin cannot be set.

I can use usbtoRS485 converter and able to communicate but cannot make it with UART4.

I also make OMAP driver as
CONFIG_SERIAL_8250_OMAP=n
CONFIG_SERIAL_OMAP=y

Can anyone help me about that?

Thanks in advance

Disclaimer: I'm brand new to the developer world and this is my first project on the BeagleBone, so bear with me here.

I have a BeagleBone Black running Debian 9.3, kernel 4.9.82-ti-r102

I'm trying to edit this file so that I can read the temperature from two different DS18B20 sensors. Before editing, I tried to just compile this file to see that it works. I ran the command:

dtc -O dtb -o BB-W1-P9.12-00A0.dtbo -b 0 -@ BB-W1-P9.12-00A0.dts

I got this error: BB-W1-P9.12.dts:14.1-9 syntax error

Eventually, I'd like to edit the file to connect a sensor to P8.11, but I have to make this work first. Any advice?

Hello,
I am using the Debian-Jessie-8.4-2016-05-13-Standalone Image with a new sd card and also this repo: https://github.com/beagleboard/bb.org-overlays

root@beaglebone:# dtc --version
Version: DTC 1.4.1-g1e75ebc9

After executing ./install.sh I reboot my system.

If i try this commando I get the following error:

root@beaglebone:/# echo BB-I2C1 > /sys/devices/platform/bone_capemgr/slots
bash: echo: write error: File exists
Maybe it's because the Kernel-Version?

After I tried this on:

root@beaglebone:/sys/devices/platform/bone_capemgr# sudo sh -c "echo 'BB-I2C1' > slots"
sh: echo: I/O error

root@beaglebone:/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-universaln

If i delete cape_universal=enable from uEnv.txt, it works fine. But i don't know if this is the best solutions. I would be very pleased about an answer.

I need assistance migrating a custom overlay to work with the new debian jessie build, Im posting the original and what I've been able to come up with so far. The overlay exposed ttyO1 previously that I was able to use to connect to a modem and some leds. Any help will be greatly appreciated.

ORIGINAL

/dts-v1/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "BB-Test";
board-name = "Bone-Black-Test-A2";
version = "00A0";
exclusive-use = "P8.15", "P9.11", "P9.12", "P9.13", "P9.14", "P9.15", "P9.22", "P9.23", "P9.24", "P9.26", "P9.27", "uart1";

fragment@0 {
    target = <0xdeadbeef>;

    __overlay__ {

        pinmux_bb_test_pins {
            pinctrl-single,pins = <0x3c 0x7 0x70 0x27 0x78 0x27 0x74 0x7 0x40 0x7 0x48 0x27 0x150 0x7 0x44 0x27 0x184 0x0 0x180 0x20 0x1a4 0x7>;
            linux,phandle = <0x1>;
            phandle = <0x1>;
        };
    };
};

fragment@1 {
    target = <0xdeadbeef>;

    __overlay__ {
        status = "okay";
        pinctrl-names = "default";
        pinctrl-0 = <0x1>;
    };
};

__symbols__ {
    bb_test_pins = "/fragment@0/__overlay__/pinmux_bb_test_pins";
};

__fixups__ {
    am33xx_pinmux = "/fragment@0:target:0";
    uart2 = "/fragment@1:target:0";
};

__local_fixups__ {
    fixup = "/fragment@1/__overlay__:pinctrl-0:0";
};

};

NEW CODE - NEEDS LOVE

/dts-v1/;
/plugin/;

include <dt-bindings/board/am335x-bbw-bbb-base.h>

include <dt-bindings/pinctrl/am33xx.h>

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";

/* identification */
part-number = "BB-Test";
board-name = "Bone-Black-Test-A2";
version = "00A0";

/* state the resources this cape uses */
exclusive-use = 
   /* the pin header uses */
   "P8.15", 
   "P9.11", 
   "P9.12", 
   "P9.13", 
   "P9.14", 
   "P9.15", 
   "P9.22", 
   "P9.23", 
   "P9.24", 
   "P9.26", 
   "P9.27", 
   "uart1";

fragment@0 {
    target = <&am33xx_pinmux>;
    __overlay__ {
        bb_test_pins:pinmux_bb_test_pins {
            pinctrl-single,pins = <
               BONE_P8_15 (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* 0x7 */
               BONE_P9_11 (PIN_INPUT_PULLDOWN | MUX_MODE7)  /* 0x27 */
               BONE_P9_12 (PIN_INPUT_PULLDOWN | MUX_MODE7)  /* 0x27 */
               BONE_P9_13 (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* 0x7 */
               BONE_P9_14 (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* 0x7 */
               BONE_P9_15 (PIN_INPUT_PULLDOWN | MUX_MODE7)  /* 0x27 */
               BONE_P9_22 (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* 0x7 */
               BONE_P9_23 (PIN_INPUT_PULLDOWN | MUX_MODE7)  /* 0x7 */
               BONE_P9_24 (PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* uart1_txd.uart1_txd */ /* 0x0 */
               BONE_P9_26 (PIN_INPUT_PULLUP | MUX_MODE0)    /* uart1_rxd.uart1_rxd */ /* 0x20 */
               BONE_P9_27 (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* 0x7 */

        /* Add more pins here */
        /* OUTPUT  GPIO(mode7) 0x07 pulldown, 0x17 pullup, 0x?f no pullup/down */
        /* INPUT   GPIO(mode7) 0x27 pulldown, 0x37 pullup, 0x?f no pullup/down */
            >;
        };
    };
};

fragment@1 {
    target = <&am33xx_pinmux>;
    __overlay__ {
        status = "okay";
        pinctrl-names = "default";
        pinctrl-0 = <bb_uart2_pins>;
    };
};

};

Hi,

There is now more than one week i search everywhere the answer to this simple error when i try to compil with this line :

root@beaglebone:~/bb.org-overlays/src/arm# dtc -O dtb -o BB-BONE-LCD7-01-00A3.dtb BB-BONE-LCD7-01-00A3.dts

Error: BB-BONE-LCD7-01-00A3.dts:13.1-9 syntax error
FATAL ERROR: Unable to parse input tree

It seems that is line is the problem.
#include dt-bindings/board/am335x-bbw-bbb-base.h (remove quote to post corectly else you don't see the rest after include)

I'm sur of it cause i move it on line 15 and problem point on line 15.

I don't understand why i can't just compile a simple scratch BB-BONE-LCD7-01-00A3.dts

I already reinstalled from scratch all my BBB with the latest version 4.4.9.
I followed all the steps you mentioned even if i'm not sure of what it does exactly after install.sh concerning kernel?
i try to use this version :

v4.4.x mainline:
sudo ./update_kernel.sh --lts-4_4 --bone-channel

There was some error and it complain about the fact that this version is for 4.4.19 and i'm only 4.4.9. So i don't know if this step is required but it seems to not finished completly.

Also the dt-bindings/board/am335x-bbw-bbb-base.h exist in the good folder so download from git is ok .

My lcd works fine by unloading hdmi and loading this LCD device tree. I need to modify it only for the touchscreen cause it uses in the dts channel 4 5 6 7 but channel 7 on BBB is wired to a 1.65V reference voltage.

I have seen in other men that had the same issue, but the answer on how to solve it was not clear ( just said to check manual...).

Thank you very much for your precious help cause in my previous 3.8 version and 4.0 dtc, i had no issue.

Florian :)

Hello, i have a feeling i am unable to sent any CAN bus packets to the P9_24 , P9_26 pins as i am not able to work with BB-CAN1-00A0.dtbo active.

virtual Can0 worked and i was able to send packets..... progressing to a real physical Can0 i am unable to see any transmission on the GPOI pins (P9 - 24&26) i monitored both with my oscilloscope while i only expect one to transmit.

for some reason in the capemgr/slots keeps showing "cape-universaln"
and cant get BB-CAN1 active.

I checked my pinmux and that says the GPIO is UNCLAIMED of these pins..... i would think this should show some reference to CAN1.

i just want to ask opinion of people who will know far more than me!! "if i find a way to disable cape-universaln..... would this be a good move? i have seen a reference to it in the uEnv.txt file

any advice will be appreciated, if this is the wrong place to post this question sorry.

Hi,

I'm trying to activate a second SDIO connection on the P8 Header to test some in-house HW.

I'm stuck at the stage where I'm trying to add the BB-BONE-eMMC1 overlay to /sys/devices/platform/bone_capemgr/slots.

I experimented adding another (randomly selected) which I can find under /lib/firmware/, then checking the process using 'dmesg':
debian@arm:/etc/init.d$ sudo sh -c "echo 'BB-UART1' > /sys/devices/platform/bone_capemgr/slots"
debian@arm:/etc/init.d$ sudo cat /sys/devices/platform/bone_capemgr/slots
0: PF---- -1
1: PF---- -1
2: PF---- -1
3: PF---- -1
9: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-BONE-BACONE
18: P-O-L- 1 Override Board Name,00A0,Override Manuf,BB-UART1
debian@arm:/etc/init.d$ dmesg
[ 3357.065970] bone_capemgr bone_capemgr: part_number 'BB-UART1', version 'N/A'
[ 3357.073315] bone_capemgr bone_capemgr: slot #18: override
[ 3357.083113] bone_capemgr bone_capemgr: Using override eeprom data at slot 18
[ 3357.092748] bone_capemgr bone_capemgr: slot #18: 'Override Board Name,00A0,Override Manuf,BB-UART1'
[ 3357.118427] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 188, base_baud = 3000000) is a 8250
[ 3357.138683] bone_capemgr bone_capemgr: slot #18: dtbo 'BB-UART1-00A0.dtbo' loaded; overlay id #1

Now, when I do the same with BB-BONE-EMMC1 it fails:

debian@arm:/etc/init.d$ sudo sh -c "echo 'BB-BONE-eMMC1' > /sys/devices/platform/bone_capemgr/slots"
sh: echo: I/O error
debian@arm:/etc/init.d$ dmesg
[ 3924.210823] bone_capemgr bone_capemgr: part_number 'BB-BONE-eMMC1', version 'N/A'
[ 3924.218735] bone_capemgr bone_capemgr: slot #20: override
[ 3924.229681] bone_capemgr bone_capemgr: Using override eeprom data at slot 20
[ 3924.242892] bone_capemgr bone_capemgr: slot #20: 'Override Board Name,00A0,Override Manuf,BB-BONE-eMMC1'

Any idea?
Thanks for any help you can provide,

MarcDorval

I am trying to get audio to output on the I2S port with a Beaglebone Green Wireless. I have installed the Debian 8.6 2016-11-06 4GB SD SeeedStudio IoT image and run apt-get update/upgrade. I have also updated to the latest 4.9 kernel using ./update_kernel.sh --ti-channel --lts-4_9. The output of uname -a is 4.9.10-ti-r23. I have noticed that some overlays will load fine, such as univ-bbgw. With the univ-bbgw, aplay -L shows default, null, and pulse. I was expecting to see default:CARD=black. Running speaker-test does not show any output on p28, which I believe to be the audio output pin for I2S. Note that I don't actually have an I2S device hooked up at the moment. This is just a test before I purchase a device.

After that I tried to load BB-BONE-AUDI-02 in which case I get an error
[54270.254981] OF: resolver: of_resolve_phandles: Could not find symbol 'clk_mcasp0'
[54270.263050] bone_capemgr bone_capemgr: slot #6: Failed to resolve tree

Is there a different cape I should be loading to get audio output?

Hi @RobertCNelson

I'm trying to use pins P9.24 and P9.26 as a UART on a BBB with Debian Stretch, but I do not know the correct way to set the pins. Previously in Debian Jessie I used the configuration cape_enable = bone_capemgr.enable_partno = BB-UART1 but in the new version apparently this configuration is not valid.
At another time I tried to use the config-pin but it returns an error:

P9_24 pinmux file not found!
Pin has no cape: P9_24

I would also like this to be done at boot time.

Thank you for your help

My version.sh output:

git:/opt/scripts/:[e307a944e0be0610ff5296e0abe4ad31a6e70daa]
eeprom:[A335BNLT00C02215BBBK0512]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-03-05]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.01-00002-ge9ff418fb8]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.01-00002-ge9ff418fb8]:[location: dd MBR]
kernel:[4.9.82-ti-r102]
nodejs:[v6.14.1]
pkg:[bb-cape-overlays]:[4.4.20180424.0-0rcnee0stretch+20180424]
pkg:[bb-wl18xx-firmware]:[1.20180328-0rcnee2stretch+20180328]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]
cmdline:[console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait]
dmesg | grep pinctrl-single
[ 1.359939] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[ 1.361042] gpio-of-helper ocp:cape-universal: ready
END

Hi,
I'm using stretch and am trying to load a custom cape. I can't seem to affect the log file at all with respect to loading capes. Everything I try yields the same log showing nothing about my cape.

The dtbo is: BB-BONE-PRU-00A0.dtbo
I have placed this file in /lib/firmware.

I have modified my uEnv.txt with the line: enable_uboot_overlays=1

I have tried the following in uEnv.txt:
dtb_overlay=/lib/firmware/BB-BONE-PRU-00A0.dtbo

and also at a separate time:
uboot_overlay_addr0=/lib/firmware/BB-BONE-PRU-00A0.dtbo

I have also tried adding the following line to /etc/default/capemgr:
CAPE=BB-BONE-PRU (also tried CAPE=BB-BONE-PRU-00A0.dtbo)

I never see any change in the boot log. There is nothing about my cape and I always see the line " bone_capemgr.uboot_capemgr_enabled=1" in the log even if I set it to 0.

I'm sure I'm missing something about the new cape system. I am excited to get it working. It might help with some issues on my board with loading the cape after bootup. Hot swapping cape files was a neat idea, but I think in practical use, rebooting each time you want to change a cape is just fine.

Thanks for any help.

(I'm using this image: https://debian.beagleboard.org/images/bone-debian-9.2-iot-armhf-2017-10-10-4gb.img.xz)

• Eric McKenzie

I am trying to get encoder input using eQEP on the BBB. I am running the Ubuntu 16.04 image downloaded from rcn-ee website.

ubuntu@arm:/sys/firmware/devicetree/base/bone_capemgr$ uname -r
4.9.54-ti-r68
ubuntu@arm:~$ ls -ltr /sys/devices/platform/bone_capemgr
total 0
-rw-r--r-- 1 root root 4096 Dec  6 17:29 uevent
lrwxrwxrwx 1 root root    0 Dec  6 17:29 subsystem -> ../../../bus/platform
drwxr-xr-x 2 root root    0 Dec  6 17:30 power
lrwxrwxrwx 1 root root    0 Dec  6 17:30 of_node -> ../../../firmware/devicetree/base/bone_capemgr
-r--r--r-- 1 root root 4096 Dec  6 17:30 modalias
-rw-r--r-- 1 root root 4096 Dec  6 17:30 driver_override
lrwxrwxrwx 1 root root    0 Dec  6 17:30 driver -> ../../../bus/platform/drivers/bone_capemgr
ubuntu@arm:~$ ls -ltr /sys/firmware/devicetree/base/bone_capemgr/
total 0
-r--r--r-- 1 root root 16 Dec  6 17:53 compatible
-r--r--r-- 1 root root 20 Dec  6 17:53 nvmem-cells
-r--r--r-- 1 root root  4 Dec  6 17:53 #slots
-r--r--r-- 1 root root  5 Dec  6 17:53 status
drwxr-xr-x 4 root root  0 Dec  6 17:53 baseboardmaps
-r--r--r-- 1 root root 13 Dec  6 17:53 name
-r--r--r-- 1 root root 34 Dec  6 17:53 nvmem-cell-names
ubuntu@arm:~$ cat /sys/firmware/devicetree/base/bone_capemgr/#slots
�ubuntu@arm:~$ 

I tried following the readme, but this crucial file 'slots' is missing!! Could you please help?

config-pin -l P9.14 pwm
default gpio gpio_pu gpio_pd gpio_input pwm

root@beaglebone:/sys/class/pwm/pwmchip0# config-pin P9.14 pwm
P9_14 pinmux file not found!
Pin has no cape: P9_14

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,am33xx_pwm
5: P-O-L- 1 Override Board Name,00A0,Override Manuf,bsana_AIN0_39
6: P-O-L- 2 Override Board Name,00A0,Override Manuf,bspwm_P9_14_6
7: P-O-L- 3 Override Board Name,00A0,Override Manuf,bspwm_P9_16

Sys system:

sys/class/pwm# tree
.
├── pwmchip0 -> ../../devices/platform/ocp/48300000.epwmss/48300100.ecap/pwm/pwmchip0
├── pwmchip1 -> ../../devices/platform/ocp/48300000.epwmss/48300200.pwm/pwm/pwmchip1
├── pwmchip3 -> ../../devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip3
├── pwmchip5 -> ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm/pwmchip5
└── pwmchip6 -> ../../devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip6

Hi,
I got beaglebone black industrial with kernel 4.14 and uboot 2018.
I'm not able to set my gpio pin.

sudo config-pin P9.23 gpio
P9_23 pinmux file not found!
Pin has no cape: P9_23

Under /sys/devices/platform/ocp there are only devices for P9_19 and P9_20.
With an earlier Image capeuniversal enabled much more pins.
Where are they now?
My version.h output:

git:/opt/scripts/:[871a0ada4779d046081f2b29f4a95d44db2f954d]
eeprom:[A335BNLTAIA04917BBBI4331]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-03-05]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.01-00002-ge9ff418fb8]:[location: dd MBR]
kernel:[4.14.35-ti-r44]
nodejs:[v6.13.0]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180424.0-0rcnee0~stretch+20180424]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[    1.044157] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[    1.045371] gpio-of-helper ocp:cape-universal: ready
END

My uEnv.txt:

#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.14.35-ti-r44
#uuid=
#dtb=


###U-Boot Overlays###
###Documentation: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
###Master Enable
enable_uboot_overlays=1
###
###Overide capes with eeprom
#uboot_overlay_addr0=/lib/firmware/<file0>.dtbo
#uboot_overlay_addr1=/lib/firmware/<file1>.dtbo
#uboot_overlay_addr2=/lib/firmware/<file2>.dtbo
#uboot_overlay_addr3=/lib/firmware/<file3>.dtbo
###
###Additional custom capes
#uboot_overlay_addr4=/lib/firmware/<file4>.dtbo
#uboot_overlay_addr5=/lib/firmware/<file5>.dtbo
#uboot_overlay_addr6=/lib/firmware/<file6>.dtbo
#uboot_overlay_addr7=/lib/firmware/<file7>.dtbo
###
###Custom Cape
#dtb_overlay=/lib/firmware/ADAFRUIT-SPI0-00A0.dtbo
###
###Disable auto loading of virtual capes (emmc/video/wireless/adc)
#disable_uboot_overlay_emmc=1
#disable_uboot_overlay_video=1
#disable_uboot_overlay_audio=1
#disable_uboot_overlay_wireless=1
#disable_uboot_overlay_adc=1
###
###PRUSS OPTIONS
###pru_rproc (4.4.x-ti kernel)
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo
###pru_uio (4.4.x-ti, 4.14.x-ti & mainline/bone kernel)
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
###
###Cape Universal Enable
enable_uboot_cape_universal=1
###
###Debug: disable uboot autoload of Cape
#disable_uboot_overlay_addr0=1
#disable_uboot_overlay_addr1=1
#disable_uboot_overlay_addr2=1
#disable_uboot_overlay_addr3=1
###
###U-Boot fdt tweaks... (60000 = 384KB)
#uboot_fdt_buffer=0x60000
###U-Boot Overlays###

cmdline=coherent_pool=1M net.ifnames=0 quiet

#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e

##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

Btw. I do not understand the concept of adding custom capes per 'uboot_overlay_addr4=' and 'dtb_overlay=/lib/firmware/' at all.
Please help!

When I first tried to work with config-pin, I had no idea what format I should specify the pin numbers and what would be available, so I was looking around for an option to list all valid pins. Perhaps it would make sense to add one?

I am trying to get spi to work on Beaglebone with 4.1.21-bone-rt-r20 (but this does not matter). I had it working fine with 3.8. No matter what I do I get the spidev1.0, but the pin assignment fails they do not change mode to 0 nor set input output.. They remain default 0x37.

My default in uEnv.txt is to disable universal cape and HDMI:

dtb=am335x-boneblack-emmc-overlay.dtb
cmdline=coherent_pool=1M quiet cape_universal=disable

after boot I can just be lazy and load the overlay dtb BBB-SPIDEV0, or....

Anyone can help? thanks
Henryk Birecki

Hello,

I was told by this fellow tonight on irc #beagle that this is the place to get things done. Now, although I do not understand everything, I can do some type of switch-a-roo every now and then.

This is what I am saying. I changed some library in Python, Adafruit_BBIO's Adafruit_I2C, to get this Motor Bridge Cape to work. I had some trouble w/ this Cape from Seeed-Studio at the beginning and during the last week while updating Adafruit_BBIO, going to bbb.io/latest-images and getting their latest image, and by whatever else has been transpiring w/out my knowledge w/ updates/upgrades.

So,

In hindsight, I would like to add support for this Cape, the Motor Bridge Cape, to whatever it is that needs to be finalized so that it works "out-of-the-box" w/ our current configurations.

I think I may have changed things to suit specific boards but I may be proved wrong. I would like to supply you and anyone else w/ this info. to do whatever you need to do to make this Cape accessible for people who have purchased it in the past and for people that will purchase it in the future.

Seth

P.S. Please let me know what I need to supply you in order to make my understanding your understanding. Commands and/or changed software is what I can provide and I think I may have changed some extra lines in the uEnv.txt file, too. So, let me know. I will return service.

I work on the firmware for Replicape, and we're having an issue on recent images/kernels that we seem to lose our GPIO pins for the steppers. Our code manipulates these pins from the PRUs, which we access via UIO.

I'm currently experimenting with your bone-ubuntu-16.04.3-console-armhf-2018-02-09-2gb. version.sh shows this:

# /opt/scripts/tools/version.sh
git:/opt/scripts/:[aa257709957bdaab058ef4428469b87bb2c2f19e]
eeprom:[A335BNLT00C02916BBBK16F0]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[Umikaze 2.1.2-rc2 Tue Mar  6 23:51:34 UTC 2018]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.01-00002-g9aa111a004]:[location: dd MBR]
kernel:[4.14.17-ti-r32]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180126.0-0rcnee0~xenial+20180126]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~xenial+20180104]
WARNING:pkg:[firmware-ti-connectivity]:[NOT_INSTALLED]
groups: ‘ubuntu’: no such user
groups:[]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait uboot_detected_capes=BB-BONE-REPLICAP, coherent_pool=1M net.ifnames=0 quiet consoleblank=0 fbcon=rotate:1 omap_wdt.nowayout=0 video=HDMI-A-1:1024x768@60e]
dmesg | grep pinctrl-single
[    0.930807] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[    0.932402] gpio-of-helper ocp:cape-universal: ready
END

I'm using a rev 0B3A board, which uses this overlay: https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BONE-REPLICAP-0B3A.dts

I'm wondering if there are changes we need to make because we're making the change from kernel-loaded overlays to U-Boot-loaded overlays?

Some other interesting things I've observed:

• With a logic analyzer, I can verify that STEP_X and DIR_X are always low. It seems like the pins in pruicss_stepper_pins are somehow in an incorrect state.
• I can trigger all of the endstops, so end_stop_pins in the overlay seem to be fine.
• I can also observe that the stepper drivers do power up on command, so the bone_replicape_spi1_pins seem to be working.
• There aren't any errors from pinmux in the kernel logs.

Do you have any suggestions for what might be going wrong here?

In src/arm/BB-ADC-00A0.dts
line 21:

    /* the pin header uses */
    "P9.31",    /* AIN0 */

AIN0 is P9.39

Hi guys. The Feb 21 change to BB-SPIDEV0-00A0.dts to remove the “compatible = …” line/property is causing my latest Deb 8.10 upgrade (4.4.9-ti-r25) to produce the dmesg error:

[    2.467085] bone_capemgr bone_capemgr: slot #4: override
[    2.467098] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[    2.467112] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-SPIDEV0'
[    2.467501] bone_capemgr bone_capemgr: initialized OK.
[    2.478068] bone_capemgr bone_capemgr: slot #4: No compatible property for 'BB-SPIDEV0’    <========
[    2.486219] bone_capemgr bone_capemgr: slot #4: Failed verification

I'm of course loading it via /boot/uEnv.txt:bone_capemgr.enable_partno=BB-SPIDEV0. If I add the compatible property back into the current .dts file of a bb.org-overlays fork and ./install.sh the problem goes away. I’m suspicious that my 8.10 release is still using a 4.4.9 kernel built last May. But I don’t understand how you check which kernel is supposed to be part of a current distribution. A dpkg -l | grep linux shows 4.4.9-ti-r25 as the current package for my 8.10 which has been incrementally dist-upgraded since 8.5.

Anyway, I’ve got customers world-wide with a device I sell containing a BBG. I always tell them NOT to do a dist-upgrade until I can do some QA. But some of them can’t help themselves I guess.

Thanks for your time.

According to the diagram, https://github.com/beagleboard/pocketbeagle/blob/master/docs/PocketBeagle_pinout.png
And to the PocketBeagle dts:
https://github.com/beagleboard/bb.org-overlays/blob/master/tools/pinmux-generator/PocketBeagle.dts#L564

There is a mismmatch in the universal cape : https://github.com/beagleboard/bb.org-overlays/blob/master/tools/beaglebone-universal-io/config-pin#L399

P2_25 (MOSI) should be defaulted to spi1_d1 (not sp1_cs0):
P2_25_INFO="spi1_cs0 default gpio1_9 gpio1_9 gpio1_9 spi1_d1 spi1_cs0 uart4_txd dcan1_rx i2c1_scl"

Question about Chip Select:
Looking at BBB we have BOTH CS0 and CS1 on SPI1
https://github.com/beagleboard/bb.org-overlays/blob/master/tools/pinmux-generator/BeagleBone_Black.dts#L835

Would it be logical that we keep the same logic and have a spi1_cs0 on the PocketBeagle ?

Are there any plans to add capes for CTS/RTS pins setup for each UART?

The documentation recommends installing dtc-1.4.1 which no longer has the '-@' option. However when I remove '-@' from the Makefile I still get an error (see below). When I use dtc-1.4.0 it runs smoothly.

make

DTC src/arm/BB-I2C1-PCA9685-00A0.dtbo
Error: src/arm/BB-I2C1-PCA9685-00A0.dts:9.2-8 syntax error
FATAL ERROR: Unable to parse input tree
Makefile:133: recipe for target 'src/arm/BB-I2C1-PCA9685-00A0.dtbo' failed
make[1]: *** [src/arm/BB-I2C1-PCA9685-00A0.dtbo] Error 1
Makefile:81: recipe for target 'all_arm' failed
make: *** [all_arm] Error 2

System:
Linux bb 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Linux
dtb=am335x-boneblack-overlay.dtb

Example:
$ BB-UART1 > /sys/devices/platform/bone_capemgr/slots

$ cat /sys/devices/platform/bone_capemgr/slots
 0: PF----  -1 
 1: PF----  -1 
 2: PF----  -1 
 3: PF----  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART1

Device is added successfully, but when I try to remove:

$ echo -4 > /sys/devices/platform/bone_capemgr/slots
Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  217.928790] Internal error: : 1028 [#1] SMP ARM

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.016638] Process bash (pid: 1580, stack limit = 0xdab6e218)

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.022501] Stack: (0xdab6fad8 to 0xdab70000)

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.026880] fac0:                                                       dab6fb14 dab6fae8

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.035104] fae0: c0673b98 c066d518 c0673b14 dc3ec010 dc3ec010 00000000 c0f93140 00000008

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.043328] fb00: dc3ec010 c0f93140 dab6fb24 dab6fb18 c06ee2a0 c0673b20 dab6fb3c dab6fb28

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.051570] fb20: c0030300 c06ee270 c00302e4 dc3ec010 dab6fb54 dab6fb40 c06efe30 c00302f0

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.059813] fb40: 0000000c dc3ec010 dab6fb6c dab6fb58 c06efeac c06efdf4 0000000c c00302e4

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.068056] fb60: dab6fbc4 dab6fb70 c06f03f4 c06efe88 60000093 c0f93a88 c008b150 dab6e000

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.076299] fb80: dc1f4c10 c008ab2c dab6fbc4 dab6fb98 c008ab2c dc8ba61e 00000000 dc3ec010

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.084541] fba0: 00000000 dc3ec074 00000004 dc3ec018 dc1f4c10 dc3f09c0 dab6fbec dab6fbc8

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.092784] fbc0: c06f0ae8 c06f02d0 0000000d dc3ec010 00000004 dc3ec074 60000013 dc3ec018

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.101027] fbe0: dab6fc0c dab6fbf0 c06f0d58 c06f0a04 dc3ec610 dc3ec010 c10269e8 c113c6a4

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.109270] fc00: dab6fc24 dab6fc10 c0672a80 c06f0ce4 dc3ec010 dc3ec010 dab6fc3c dab6fc28

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.117513] fc20: c06e7b58 c0672a64 dc3ec010 c102416c dab6fc54 dab6fc40 c06e5ba8 c06e7b30

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.125756] fc40: dc3ec044 dc3ec010 dab6fc6c dab6fc58 c06e5c50 c06e5b20 dc01fa30 dc3ec010

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.133998] fc60: dab6fc8c dab6fc70 c06e48f0 c06e5c30 00000000 dc3ec000 dc3ec010 c0f93a88

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.142240] fc80: dab6fccc dab6fc90 c06e0dd4 c06e4800 dac2b460 c0a516e0 dab6fcc4 dab6fca8

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.150482] fca0: c0a516f0 dc8ba61e dc3ec000 dc3ec000 dc3ec000 ffffffff 00000000 c10360e0

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.158724] fcc0: dab6fcec dab6fcd0 c06e79f0 c06e0cb4 c10269e8 dc3ec000 dc3ec000 00000005

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.166967] fce0: dab6fd04 dab6fcf0 c06e7a78 c06e79d8 c10269e8 dc3ec010 dab6fd1c dab6fd08

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.175209] fd00: c08b22d8 c06e7a68 dc8ba61e c0f93a88 dab6fd44 dab6fd20 c08b2778 c08b2248

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.183451] fd20: c0825db8 dc8ba61e ffffffff dab6fdb0 00000005 ffffffff dab6fd6c dab6fd48

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.191692] fd40: c0065e94 c08b26f8 ffffffff c10472e8 dab6fdb0 00000005 c1073b60 da9df020

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.199935] fd60: dab6fd94 dab6fd70 c00662f0 c0065e4c 00000000 daa18a30 c0f93a88 df939f84

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.208176] fd80: 00000000 c0f93a88 dab6fdac dab6fd98 c0066330 c00662a4 00000000 c05bbfc4

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.216419] fda0: dab6fdd4 dab6fdb0 c08b39e0 c0066314 df939e0c df939f84 daac2980 dc8ba61e

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.224661] fdc0: c0f93a88 dab6fde4 dab6fe14 dab6fdd8 c08b3a64 c08b3968 da9df020 dc3f09c0

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.232904] fde0: dab6fe14 daac25c0 daac2840 00000005 df939e0c df939f84 daac2980 dc8ba61e

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.241147] fe00: daac2140 daa18d98 dab6fe5c dab6fe18 c08b4608 c08b3a04 c023ff8c daac2840

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.249389] fe20: daa18d98 00000002 daa18a00 00000000 00000000 dc8ba61e dab6fe5c daa18d80

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.257631] fe40: 00000000 daa18da0 daa18d98 dc222810 dab6fe7c dab6fe60 c08ba158 c08b4570

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.265874] fe60: daa89410 dc222810 00000004 dc3f0100 dab6fe94 dab6fe80 c070f69c c08ba0cc

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.274116] fe80: daa89410 c0f93a88 dab6fecc dab6fe98 c070ff30 c070f628 00000000 c01b1670

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.282359] fea0: 00000004 dc8ba61e dc3f0100 dc3f09cc 00000003 dab6ff70 00000000 00000000

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.290601] fec0: dab6fedc dab6fed0 c06dfe0c c070fc8c dab6fef4 dab6fee0 c023e88c c06dfdf0

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.298844] fee0: c023e838 dc3f0100 dab6ff2c dab6fef8 c023e01c c023e844 00000000 00000000

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.307087] ff00: c01c30f4 db493180 00000003 01e51408 dab6ff70 01e51408 dab6e000 00000000

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.315329] ff20: dab6ff3c dab6ff30 c01c2ae8 c023df60 dab6ff6c dab6ff40 c01c33bc c01c2acc

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.323572] ff40: 00000000 c01e29f0 db493180 c0f93a88 db493180 00000003 01e51408 dab6e000

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.331813] ff60: dab6ffa4 dab6ff70 c01c3dc4 c01c3328 00000000 00000000 dabd0680 dc8ba61e

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.340055] ff80: 00000000 00000003 01e51408 b6f25b50 00000004 c0011024 00000000 dab6ffa8

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.348298] ffa0: c0010e60 c01c3d6c 00000003 01e51408 00000001 01e51408 00000003 00000000

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.356540] ffc0: 00000003 01e51408 b6f25b50 00000004 00000003 00000000 000c5758 00000000

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.364782] ffe0: 00000000 bea9a8a4 b6e88c85 b6ec3f26 40000030 00000001 00000000 00000000

Message from syslogd@bb at Jan 10 11:45:47 ...
 kernel:[  218.669499] Code: e8bd4000 e5d0204d e5903008 e0831211 (e5d10000)

After this, cannot print the file /sys/devices/platform/bone_capemgr/slots or reboot with success. There are something I forgot?

Thanks

Unable to configure pins

I am attempting to setup Beagle Bone Wireless using the new U-Boot Overlays.
When I try to configure any of the pins I get the following errors:

GPIO:
debian@beaglebone:/var/lib/cloud9$ config-pin P8.03 gpio
P8_03 pinmux file not found!
Pin has no cape: P8_03

PWM:
debian@beaglebone:/var/lib/cloud9$ config-pin P9.14 pwm
P9_14 pinmux file not found!
Pin has no cape: P9_14

Following recommendations found for related issues I have updated the kernal and the boot loader.
I have tried configuring many other pins with the same result.
Based on documentation here: https://github.com/cdsteinkuehler/beaglebone-universal-io all pins are enabled and in a default condition.
It looks like Cape Universal is not loading.

What am I doing wrong?

Best regards,

Jack Walker

Hi Robert.

I have problem in using audio cape with the BBB . I'm using deb 8.7 (bone-debian-8.6-iot-armhf-2017-03-19-4gb).

Firs thing i did, i changed the uEnv.txt in the /boot dir and uncommented below line:
dtb=am335x-boneblack-emmc-overlay.dtb

After reboot, i tried to load the audio cape overlay(BB-BONE-AUDI-02), but i did not success beacause of this error:
Could not find symbol 'clk_mcasp0'.

After some tries, i added clk_mcasp0 node to am335x-boneblack-emmc-overlay.dts and recompiled it.

/{
clk_mcasp0_fixed: clk_mcasp0_fixed {
#clock-cells = <0>;
compatible = "fixed-clock";
clock-frequency = <24576000>;
};
clk_mcasp0: clk_mcasp0 {
#clock-cells = <0>;
compatible = "gpio-gate-clock";
clocks = <&clk_mcasp0_fixed>;
enable-gpios = <&gpio1 27 GPIO_ACTIVE_HIGH>; /* BeagleBone Black Clk enable on GPIO1_27 */
};
};
};

after that, i could load the audio overlay and palying audio with speaker-test utility.

But now i have problem with recording audio. When i use arecord utility,it has no error but
it records nothing. and the volume size of the recordrd file is always 44 bytes, independent of lenght of recording time.

what is the source of the problem?

Regards,

Hi,
I've follwed your instructions in readme, everything works till I cat slots.

I don't get empty slots as shown I have universaln in slot 4.

If I try to add anything it reports an I/O error, I can't remove the slot (issue 13) so I comment out universal in uEnv.txt, the BBB just hangs and won't boot.

I have an LCD cape (BB-CAPE-DISP-CT4-00A0) that works by adding the hardware and booting, but I want to mess about with the LCD settings to drive another LCD.

I changed the source for the cape, finally managed to compile it to dtbo using make instead of dtc, I compared the dtbo with the original, it was different but nothing changes in reality hence I'm trying to enable the overlay manually.

I'm new to this, I bought Derek Molloy's book and have worked through it to chapter 6 so I'm not a complete duffer but I seem to have got to a step where my kernel version doesn't correspond with any of the advice given and everything I try gets me nearly but not quite there. I'm using 4.4.45 but followed your upgrade to 4.4.49. Sorry if I'm asking stupid questions, I'm at my wits end trying to do something that I reckon should be simple.

Would appreciate your help.

Hi

while I am trying to do dtos I cannot see all the slots loaded after exporting and doing " cat $SLOTS "
it shows till slots 4 and 5. And when i look into bone_capemgr.9 directory, I cannot see slots 7 and 8. By the way, I am using debian Image 7.8 on my beaglebone balck. Please help me, Im just a beginner.

debian@beaglebone:$ export SLOTS=/sys/devices/bone_capemgr.9/slots
debian@beaglebone:$ export PINS=/sys/kernel/debug/pinctrl/44e10800.pinmux/pins
debian@beaglebone:$ nano /.profile
debian@beaglebone:$ source /.profile
debian@beaglebone:$ cat $SLOTS
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
debian@beaglebone:$ cd /lib/firmware/
debian@beaglebone:/lib/firmware$ ls SPI
ADAFRUIT-SPI0-00A0.dtbo ADAFRUIT-SPI1-00A0.dtbo
debian@beaglebone:/lib/firmware$ ls UART
ADAFRUIT-UART1-00A0.dtbo ADAFRUIT-UART2-00A0.dtbo ADAFRUIT-UART4-00A0.dtbo ADAFRUIT-UART5-00A0.dtbo
debian@beaglebone:/lib/firmware$ cd /sys/devices/bone_capemgr.9/
debian@beaglebone:/sys/devices/bone_capemgr.9$ ls
baseboard driver modalias power slot-4 slot-5 slots subsystem uevent
debian@beaglebone:/sys/devices/bone_capemgr.9$

Thanks

@RobertCNelson I'm running 4.16.0-rc1-bone2 kernel just to give it a try and I noticed that config-pin seems to fail.

root@beaglebone:~# uname -a
Linux beaglebone 4.16.0-rc1-bone2 #1 Fri Feb 16 01:27:36 UTC 2018 armv7l GNU/Linux
root@beaglebone:~# config-pin -q p9.12
P9_12 pinmux file not found!
Cannot read pinmux file: /sys/devices/ocp.*/P9_12_pinmux.*/state

It looks like the path has changed from /sys/devices/ocp to /sys/devices/platform/ocp?

root@beaglebone:~# find /sys/devices/ -type f |grep P9_12_pinmux 
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/runtime_active_kids
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/runtime_suspended_time
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/autosuspend_delay_ms
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/runtime_enabled
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/runtime_active_time
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/control
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/async
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/runtime_usage
/sys/devices/platform/ocp/ocp:P9_12_pinmux/power/runtime_status
/sys/devices/platform/ocp/ocp:P9_12_pinmux/driver_override
/sys/devices/platform/ocp/ocp:P9_12_pinmux/modalias
/sys/devices/platform/ocp/ocp:P9_12_pinmux/state
/sys/devices/platform/ocp/ocp:P9_12_pinmux/uevent
root@beaglebone:~# cat /sys/devices/platform/ocp/ocp:P9_12_pinmux/state
default

Hi,
Running a fresh 9.1 LXQT from microSD with the Newhaven 7" display. Display works as expected, but the GPIO pins are not available (i.e. P9_12).
The /sys/class/gpio shows only export gpiochip0 ...gpiochip96
I can't see the allocation of the pins, when the LCD is disconnected I see
export gpio14 gpio23 gpio31 ... gpiochip0 ... etc etc

Is this a known issue? Is there a configuration that works? Tried all sorts over the last five days.
uEnv.txt only has these lines enabled, the rest is commented out:
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
uname_r=4.9.45-ti-r57
enable_uboot_overlays=1
enable_uboot_cape_universal=1
cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable

version.sh shows this:

git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
eeprom:[A335BNLT000C1750BBBG0502]
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.09-rc2-00002-g7c9353]
kernel:[4.9.45-ti-r57]
nodejs:[v6.11.2]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1stretch+20170728]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

Any help would be greatly appreciated.
Thanks Maurice

I am facing huge issues with trying to use the PRUs on the BeagleBone Blue. I am unable to get my code up and running because:

1. Disabling it in /boot/uEnv.txt just doesn't work at all because the blue doesn't support u-boot overlays yet

2. there's no simple way to build a custom 4.9-ti dt with uio-pruss instead of remoteproc-pru

3. while the 4.9-bone dt does use uio-pruss, it looks like it just hasn't been kept in sync at all

Please advise on what can be done. I am trying to run a blinky sketch on the PRU, but the pinmux is not set right at all.

I'm guessing that the dts files under src/arm are designed for the 4.1.x and 4.4.x kernels, right?

I had to downgrade my kernel to 3.8.13 due to RobertCNelson#4 and I was wondering where I could find the dts files for 3.8.x. Thank you 😄

We need to have 2 devices on spi1, following the overlay logic, we mapped using config:
config-pin P2_30 spi_cs
cat /sys/devices/platform/ocp/ocp:P2_30_pinmux/state == spi_cs

but this is just a mapping, so the driver does not reload and the new port is not present
ls /dev/spi*
/dev/spidev0.0 /dev/spidev1.1

Do we need to make a new DTS for the Pocket or there is a method to map within uEnv.txt ?

Best regards

Hello Robert

We are updating the BBLUE Image - Kernel and Configuration
We want to implement config-pins and replace:
echo pruecapin_pu > /sys/devices/platform/ocp/ocp:P8_15_pinmux/state
with
sudo config-pin P8_15 pruecapin_pu
But we get this error:
Invalid mode: pruecapin_pu

Using config-pin list gives:
sudo config-pin -l P8_15
default gpio gpio_pu gpio_pd gpio_input qep pru_ecap pruin
Seems that pruecapin_pu is not in the profile

And if we try
sudo config-pin P8_15 pru_ecap
We have this error:
[ 494.769840] bone-pinmux-helper ocp:P8_15_pinmux: Failed to find state pru_ecap
dash: echo: I/O error
Cannot write pinmux file: /sys/devices/platform/ocp/ocp:P8_15_pinmux/state

We had a similar issue a few weeks ago: #57
Resolved with sudo apt upgrade bb-cape-overlays

debian@beaglebone:$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[714e162ba98cf3d2897e7fc95e951c6df15a7d0a]
eeprom:[A335BNLTBLA21712EL004215]
model:[TI_AM335x_BeagleBone_Blue]
dogtag:[BeagleBoard.org Debian Image 2018-01-21]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.01-00002-g9aa111a004]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.11-00002-g7b415acfc1]
kernel:[4.9.78-ti-rt-r94]
nodejs:[v6.12.3]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180126.0-0rcnee0stretch+20180126]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2stretch+20180104]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0stretch+20170830]
dmesg | grep pinctrl-single
[ 1.624335] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 1.671098] pinctrl-single 44e10800.pinmux: pin PIN85 already requested by 48024000.serial; cannot claim for ocp:P9_21_pinmux
[ 1.682649] pinctrl-single 44e10800.pinmux: pin-85 (ocp:P9_21_pinmux) status -22
[ 1.690093] pinctrl-single 44e10800.pinmux: could not request pin 85 (PIN85) from group pinmux_P9_21_uart_pin on device pinctrl-single
[ 1.711226] pinctrl-single 44e10800.pinmux: pin PIN84 already requested by 48024000.serial; cannot claim for ocp:P9_22_pinmux
[ 1.722592] pinctrl-single 44e10800.pinmux: pin-84 (ocp:P9_22_pinmux) status -22
[ 1.730031] pinctrl-single 44e10800.pinmux: could not request pin 84 (PIN84) from group pinmux_P9_22_uart_pin on device pinctrl-single
[ 1.753287] pinctrl-single 44e10800.pinmux: pin PIN97 already requested by 48022000.serial; cannot claim for ocp:P9_24_pinmux
[ 1.764660] pinctrl-single 44e10800.pinmux: pin-97 (ocp:P9_24_pinmux) status -22
[ 1.772098] pinctrl-single 44e10800.pinmux: could not request pin 97 (PIN97) from group pinmux_P9_24_uart_pin on device pinctrl-single
[ 1.793400] pinctrl-single 44e10800.pinmux: pin PIN96 already requested by 48022000.serial; cannot claim for ocp:P9_26_pinmux
[ 1.804766] pinctrl-single 44e10800.pinmux: pin-96 (ocp:P9_26_pinmux) status -22
[ 1.812203] pinctrl-single 44e10800.pinmux: could not request pin 96 (PIN96) from group pinmux_P9_26_uart_pin on device pinctrl-single
[ 1.839066] pinctrl-single 44e10800.pinmux: pin PIN100 already requested by ocp:P9_31_pinmux; cannot claim for 481a0000.spi
[ 1.850286] pinctrl-single 44e10800.pinmux: pin-100 (481a0000.spi) status -22
[ 1.857466] pinctrl-single 44e10800.pinmux: could not request pin 100 (PIN100) from group pinmux_P9_31_spi_pin on device pinctrl-single
END

Has anyone had any luck with the CBB-Serial cape? It does not seem to be working in the latest 4.1.13-ti-r35 kernel. I can add the can0 device, and bring it up with ifconfig, but no data coming over candump. I have tried using the CBB-Serial-r01.dts, and the virtual cape DCAN1. Neither is working. I have a Waveshare RS 485 CAN cape that is connecting fine using the DCAN1, so the network is OK. Something weird about this cape.

Cannot set pru_ecap , all other modes can be set:

debian@beaglebone:~$ config-pin -l P2_18
default gpio gpio_pu gpio_pd gpio_input qep pru_ecap pruin

debian@beaglebone:~$ sudo config-pin P2_18 pru_ecap
[sudo] password for debian:
dash: echo: I/O error
Cannot write pinmux file: /sys/devices/platform/ocp/ocp:P2_18_pinmux/state

Look ok on DTS: https://github.com/beagleboard/bb.org-overlays/blob/master/tools/pinmux-generator/PocketBeagle.dts#L570

Latest Debian 9.2 IoT + rt 4.14

I've found that the actual working one in all my situations is that of MCP3008.

I've modified my BB-SPIDEV0-00A0.dts so that it uses

bb_spi0_pins: pinmux_bb_spi0_pins {
pinctrl-single,pins = <
BONE_P9_22 (PIN_INPUT_PULLUP | MUX_MODE0) /* spi0_sclk.spi0_sclk /
BONE_P9_21 (PIN_INPUT_PULLUP | MUX_MODE0) / spi0_d0.spi0_d0 /
BONE_P9_18 (PIN_OUTPUT_PULLUP | MUX_MODE0) / spi0_d0.spi0_d1 /
BONE_P9_17 (PIN_OUTPUT_PULLUP | MUX_MODE0) / spi0_cs0.spi0_cs0 */
>;
};

And all works fine, ever.

The pins occupied by HDMI audio on the BBB do not work in combination with the TI RT kernels e.g.:
Linux beaglebone 4.4.54-ti-rt-r93 #1 SMP PREEMPT RT Fri Mar 17 15:25:04 UTC 2017 armv7l GNU/Linux.

Config pins accessing the state pin reports following error:

sudo config-pin P9_25 in

[sudo] password for machinekit:  
bash: /sys/devices/platform/ocp/ocp*P9_25_pinmux/state: No such file or directory

Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_25_pinmux/state

It looks like the driver is not loaded correctly:

machinekit@beaglebone:~$ ls /sys/devices/platform/ocp/ocp*P9_28_pinmux/
driver_override  modalias  of_node  power  subsystem  uevent

I could verify this problem with the following pins:

P9.25
P9.28
P9.29
P9.31

I'm currently testing analog inputs on a BeagleBone Black with BB-ADC-00A0.dts. The OS image being used is bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img.xz form here.

uname -a outputs:

Linux beaglebone 4.1.1-bone9 #1 Tue Jun 30 06:09:30 UTC 2015 armv7l GNU/Linux

Assuming the analog inputs image below is correct, then P9.39 should be reserved for AIN0 here, not P9.31.

Also, the channel numbers 1 through 7 here appear to be incorrect. I think channel numbers should be 0 through 6. For example, if overlay BB-ADC-00A0.dts is used and an analog sensor is connected to AIN5 (P9.36), the raw value appears in /sys/bus/iio/devices/iio:device0/in_voltage5_raw, but I'd expect it to appear in /sys/bus/iio/devices/iio:device0/in_voltage6_raw. If the same analog sensor is connected to AIN0 (P9.39) the raw value doesn't appear in /sys/bus/iio/devices/iio:device0/in_voltage1_raw. Note that there is no file called /sys/bus/iio/devices/iio:device0/in_voltage0_raw.

If P9.39 rather than P9.31is reserved for AIN0 and the channel numbers are 0 through 6 rather than 1 through 7, everything functions as expected. The raw value for AIN5 appears in /sys/bus/iio/devices/iio:device0/in_voltage5_raw, which is to be expected this time, and there is a file called /sys/bus/iio/devices/iio:device0/in_voltage0_raw for AIN0 which is also to be expected.

The documentation here (if it's the correct documentation) also indicates that channel numbering starts at 0.

Hi,
would be possible to add this 10/100 BASE ethernet adapter?
https://shop.mikroe.com/eth-wiz-click
This is much better than the ETH Click which is a 10base adapter available as cape atm.

Thanks
Maurice

If the BB-ADC DT overlay is loaded, the process battery_monitor which initially doesn't appear to have much to do immediately starts using as much CPU time as it can, in this case ~100%.

This was observed on a BeagleBone Black with "Debian 8.6 2016-12-09 4GB SD IoT" downloaded at BeagleBoard.org Latest Firmware Images. The BeagleBone Black was running from a wall power supply, not a battery.

Here's the output of top before loading BB-ADC:

top - 12:30:40 up 5 min,  1 user,  load average: 0.04, 0.50, 0.33
Tasks:   1 total,   0 running,   1 sleeping,   0 stopped,   0 zombie
%Cpu(s):  6.2 us,  7.1 sy,  0.0 ni, 86.3 id,  0.2 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem:    499736 total,   122160 used,   377576 free,     9144 buffers
KiB Swap:        0 total,        0 used,        0 free.    49056 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND      
  882 root      20   0   57256   1524   1428 S  0.0  0.3   0:00.34 battery_mon+ 

And here's the output of top slightly less than 40 minutes after loading BB-ADC:

top - 13:09:40 up 44 min,  1 user,  load average: 1.00, 1.00, 1.00
Tasks:   1 total,   1 running,   0 sleeping,   0 stopped,   0 zombie
%Cpu(s): 86.3 us,  1.2 sy,  0.0 ni, 12.3 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem:    499736 total,   123408 used,   376328 free,     9376 buffers
KiB Swap:        0 total,        0 used,        0 free.    49452 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND      
  882 root      20   0   57256   1524   1428 R 99.9  0.3  38:05.04 battery_mon+ 

Apologies if this issue was created in the wrong place.

When I execute the following command,

$ sudo sh -c "echo 'bone_eqep0' > /sys/devices/platform/bone_capemgr/slots"

/sys/devices/platform/ocp/48300000.epwmss/48300180.eqep/ is appeared.
But there is no function directory (like "eqep") and also "driver" symbolic link.

$ ls /sys/devices/platform/ocp/48300000.epwmss/48300180.eqep/
driver_override modalias of_node power subsystem uevent

I expect there is a function directory which contains "enable", "mode", "position" ...

My environment is Ubuntu 16.04.

$ uname -a
Linux beaglebone 4.4.9-ti-r25 #1 SMP Fri May 6 10:28:56 UTC 2016 armv7l armv7l armv7l GNU/Linux

tieqep module is seems to be loaded.

$ lsmod
Module Size Used by
pwm_tiehrpwm 4706 1
tieqep 8739 0
pruss_intc 3592 0
8021q 17828 0
garp 5769 1 8021q
mrp 7175 1 8021q
stp 2219 1 garp
llc 5123 2 stp,garp
usb_f_ecm 9400 1
g_ether 4976 0
usb_f_rndis 22191 2 g_ether
u_ether 11917 3 usb_f_ecm,usb_f_rndis,g_ether
libcomposite 43461 3 usb_f_ecm,usb_f_rndis,g_ether
snd_soc_simple_card 8385 0
pru_rproc 11295 0
omap_aes_driver 18917 0
omap_sham 21629 0
pruss 11615 1 pru_rproc
omap_rng 4423 0
rng_core 7471 1 omap_rng
snd_soc_davinci_mcasp 16596 2
snd_soc_edma 1290 1 snd_soc_davinci_mcasp
snd_soc_omap 3058 1 snd_soc_davinci_mcasp
spi_omap2_mcspi 10764 0
snd_soc_hdmi_codec 5842 1
snd_soc_core 155592 5 snd_soc_hdmi_codec,snd_soc_davinci_mcasp,snd_soc_edma,snd_soc_omap,snd_soc_simple_card
snd_pcm_dmaengine 5209 2 snd_soc_core,snd_soc_omap
snd_pcm 82689 5 snd_soc_hdmi_codec,snd_soc_davinci_mcasp,snd_soc_core,snd_soc_omap,snd_pcm_dmaengine
snd_timer 19720 1 snd_pcm
snd 59559 3 snd_soc_core,snd_timer,snd_pcm
soundcore 7601 1 snd
evdev 10695 2
uio_pdrv_genirq 3539 0
uio 8822 1 uio_pdrv_genirq
bluetooth 417817 2
rfkill 18226 3 bluetooth
tilcdc 26364 0
tda998x 12754 0

There is a driver directory for eqep.

$ ls /sys/bus/platform/drivers/eqep/
bind module uevent unbind

dmesg shows some errors. But I cannot understand it..

[ 3804.958336] bone_capemgr bone_capemgr: part_number 'bone_eqep0', version 'N/A'
[ 3804.958411] bone_capemgr bone_capemgr: slot #6: override
[ 3804.958454] bone_capemgr bone_capemgr: Using override eeprom data at slot 6
[ 3804.958500] bone_capemgr bone_capemgr: slot #6: 'Override Board Name,00A0,Override Manuf,bone_eqep0'
[ 3804.972553] platform 48300180.eqep: Cannot lookup hwmod 'eqep0'
[ 3804.992710] eqep 48300180.eqep: could not find pctldev for node /ocp/interrupt-controller@48200000, deferring probe
[ 3804.993069] bone_capemgr bone_capemgr: slot #6: dtbo 'bone_eqep0-00A0.dtbo' loaded; overlay id #2

In dtc-overlay.sh, I renamed :
server="git://git.kernel.org/pub/scm/utils/dtc"
to:
server="https://git.kernel.org/pub/scm/utils/dtc"

to make it work.

kernel version - uname -r: 4.1.33-bone24
dtc --version: Version: DTC 1.4.1-g1e75ebc9

After running ./install.sh in bb.org-overlays:

echo cape-universala > /sys/devices/platform/bone_capemgr/slots

[ 259.444391] bone_capemgr bone_capemgr: part_number 'cape-universala', version 'N/A'
[ 259.452290] bone_capemgr bone_capemgr: slot #6: override
[ 259.457733] bone_capemgr bone_capemgr: Using override eeprom data at slot 6
[ 259.464803] bone_capemgr bone_capemgr: slot #6: 'Override Board Name,00A0,Override Manuf,cape-universala'
[ 259.546047] of_resolve_phandles: Could not find symbol 'gpio4'
[ 259.551975] bone_capemgr bone_capemgr: slot #6: Failed to resolve tree
bash: echo: write error: Invalid argument

cat /sys/devices/platform/bone_capemgr/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-univ-hdmi

cape-universaln uses gpio0-3 while cape-universala uses gpio1-4. Config-pin needs cape-universala to run properly on my system.

Suggestions? Thanks.

Version states

/* identification */
    part-number = "BB-I2C2";
    version = "00A0";

But Filename has 0A00
I think this led to my problem:

Loading BB-I2C2 overlay
sh: write error: No such file or directory
Error loading device tree overlay file: BB-I2C2

Not quite sure how to build the cape definitions using the bitbake system .

Has anybody made a working recipe ?