Hello,

I don't see a way to configure SPI1 D0 as output (MOSI). Is there a way to change it? If not, can you please tell me where I should change in the source code to swap MOSI and MISO (D1 and D0)

Hello,
my setup:

1. uname -a
   -> Linux beaglebone 3.8.13-xenomai-r83 #1 Thu Jan 5 01:32:32 UTC 2017 armv7l GNU/Linux
2. /boot/uEnv.txt
   ...
   ##Disable HDMI
   cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
   ...
3. "beaglebone-universal-io" (2018-3-23, commit e75cd0c) is installed
4. load cape-universalh with "config-pin overlay cape-universalh"
5. THE Problem: If I type "config-pin P8_33 qep", I will get
   "bash: /sys/devices/ocp./P8_33_pinmux./state: No such file or directory
   Cannot write pinmux file: /sys/devices/ocp./P8_33_pinmux./state".Same with P8_35. P9_27, P92, P8_11 and P8_12 does work.

Any suggestions are welcome :-)

Best regards,
DDoIt

Can we use this to configure 1 wire support ? I have used it for uart,GPIO it works great.

When I ran the make.sh file, it gave error, stating that the command is erroneous.

I tried compiling with the command dtc -O dtb -o cape-universal-00A0.dtbo cape-universal-00A0.dts .
It worked fine with another .dts I had used earlier, but here it is giving the following error:
Error: cape-universal-00A0.dts:2.2-8 syntax error
FATAL ERROR: Unable to parse input tree

Please help.
If you can give the .dtbo file for the same, it will be appreciated.

P.S. - I am using Ubuntu 14.03 on BeagleBone Black A5C

When loading the cape-universaln overlay, I get the following error message:

$ echo cape-universaln > /sys/devices/bone_capemgr.*/slots
echo: write error: file exists

Also with config-pin:

$ config-pin overlay cape-universaln                           
Loading cape-universaln overlay
zsh:echo:1: write error: file exists
Error loading device tree overlay file: cape-universaln

Here are my loaded overlays:

$ cat /sys/devices/bone_capemgr.*/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

And my kernel version:

$ uname -a                                                                                                                        
Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l GNU/Linux

How can I troubleshoot this?

Hello,
when i do

make install

I get the following error:
compiling file cape-universal-00A0.dts
dtc: invalid option -- @

Hi guys, 2 days ago there was a commit that checked for kernel 4.1; the commit is " adapt to kernel (4.1.x) changes..." which simply checks for the existance of /sys/devices/platform/. This is not correct, because this directory exists on 3.8.13-bone47. Thus config-pin is currently broken on non-4.1 kernels, giving a spurious "pinmux file not found" error when you try to change a pin's function. Commenting out the changed lines fixes the issue. I suggest a simple 'uname -r' replacement but that is up to you.

I'm not sure I'm understanding the readme, but I guessed if I wanted to use all pins, I'd do the following:

config-pin overlay cape-universal
config-pin overlay cape-univ-emmc
config-pin overlay cape-univ-hdmi

This works fine for me, but once I try to configure the pins I get this error for a number of them:

WARNING: GPIO pin not exported, cannot set direction or value!

It seems the GPIO sysfs files (/sys/class/gpio/gpio*/direction) aren't there for the last two overlays (emmc, hdmi), but they are for the first loaded overlay. This also goes when I switch the order in which I load the overlays. It seems only the first one loads correctly, all overlays after that cannot be used correctly.

If I check the slots file it seems the overlays are loaded correctly. You can also see that I've disabled the default capes in uEnv.txt:

$ cat /sys/devices/bone_capemgr.9/slots
 0: 54:PF--- 
 1: 55:PF--- 
 2: 56:PF--- 
 3: 57:PF--- 
 4: ff:P-O-- Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
 7: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-univ-emmc
 8: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-univ-hdmi
 9: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-universal

I've used the following config-pin file to test what was happening: https://gist.github.com/bobvanderlinden/7fa5012acf00eac1bd0e

I've tried all this with the latest machinekit image on a BeagleBone Black.

Is this the correct way to use config-pin? Could you give some more information that would let me use any pin as gpio?

Hello,

Thank you so much for putting this universal cape together. It has been a tremendous help to me in getting up to speed with device trees and beagle bone programming.

I'm new to this git stuff, so I'm not sure if this is the best way to report this error, but I thought I ought to give it a shot.

In my work I noticed that P9_29 and P9_31 were not being automatically exported the way the rest of the pins are. I found that in the cape-universal-00A0.dts file the gpio number assigned to these pins were short by 10... so

where P9_29 is supposed to have a "gpio4 25" it has a "gpio4 15"

and
where P9_31 is supposed to have a "gpio4 24" it has a "gpio4 14"

I have not been using config-pin, but I noticed in my grepping that the same error occurs in config-pin as well.

Correcting this things resolved the issue and the pins are now properly exported.

Thanks again!

Bill

Hi,

Looking at the overlay dts file, I noticed that some hardware resources (uarts, i2c, spi, pru, etc.) are claimed.

Does this mean that when the cape is loaded, these hardware modules are powered on? I'm worried that doing this will increase power consumption, which is not good for my battery powered application.

If the answer is yes (hardware modules are turned on), would this be prevented by removing fragment@10 to fragment@40 from the dts file?

Trying to set up a serial connection for a GPS.

I have also tried RCN's Really Simple Cape Manager. No success on setting up pins.

$ sudo setserial -g /dev/ttyO*
/dev/ttyO0, UART: 8250, Port: 0x0000, IRQ: 88
/dev/ttyO1, UART: 8250, Port: 0x0000, IRQ: 89
/dev/ttyO2, UART: 8250, Port: 0x0000, IRQ: 90
/dev/ttyO4, UART: 8250, Port: 0x0000, IRQ: 61
/dev/ttyO5, UART: 8250, Port: 0x0000, IRQ: 62

Currently, the config-pin utility sleeps after loading a cape. However, it might be more suitable to wait for the cape to actually appear instead as described here: https://groups.google.com/d/msg/machinekit/V0LWXYFQXfM/VSV3J7QHBAAJ

Hello,
I made changes to your Makefile to make it usable in a cross-compile environment for example the setup from RobertCNelson.
(Using conditional variable assignment ?= )

Usage (in bb-kernel dir):
git clone https://github.com/cdsteinkuehler/beaglebone-universal-io
cd beaglebone-universal-io
export FIRMWAREPATH="../KERNEL/lib/firmware"
export PREFIX="../KERNEL/usr/bin"
make
make install

Patch:

diff --git a/Makefile b/Makefile
index dfff72e..ca468ae 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
-PREFIX := /usr/bin
-FIRMWAREPATH := /lib/firmware
+PREFIX ?= /usr/bin
+FIRMWAREPATH ?= /lib/firmware
BUILDPATH = .

SRC = cape-universal-00A0.dts
@@ -10,7 +10,7 @@ SRC += cape-univ-audio-00A0.dts

TARGET = config-pin

-all: ensure_buildpath build
+all: ensure_path build

install: install_overlays install_target

@@ -19,8 +19,10 @@ $(BUILDPATH)/%.dtbo : %.dts
@echo "Compiling file: $<"
dtc -@ -I dts -O dtb -o $@ $&lt;

-ensure_buildpath:
+ensure_path:
mkdir -p $(BUILDPATH)

•   mkdir -p $(PREFIX)
  

•   mkdir -p $(FIRMWAREPATH)
  

  build : $(SRC:%.dts=$(BUILDPATH)/%.dtbo)

Hello,
the mode of P9_26_can_pin is not correct, it must not have receive-mode
and it would be nice to add config-pin support to the pins P9_19 and P9_20
in the cape-universal for custom capes that do not use cape-eeprom.
I made some posts to this on
https://eewiki.net/display/linuxonarm/BeagleBone+Black+Comments?focusedCommentId=41418755#comment-41418755

diff --git a/cape-universal-00A0.dts b/cape-universal-00A0.dts
index 2c3fca7..9fbcd44 100644
--- a/cape-universal-00A0.dts
+++ b/cape-universal-00A0.dts
@@ -552,7 +552,7 @@
P9_24_uart_pin: pinmux_P9_24_uart_pin {
pinctrl-single,pins = <0x184 0x30>; }; /* Mode 0, Pull-Up, RxActive */
P9_24_can_pin: pinmux_P9_24_can_pin {

•            pinctrl-single,pins = <0x184  0x32>; };     /\* Mode 2, Pull-Up, RxActive */
  

•            pinctrl-single,pins = <0x184  0x32>; };     /\* Mode 2, dcan1_rx, Pull-Up, RxActive _/
       P9_24_i2c_pin: pinmux_P9_24_i2c_pin {
           pinctrl-single,pins = <0x184  0x33>; };     /_ Mode 3, Pull-Up, RxActive _/
       P9_24_pruin_pin: pinmux_P9_24_pruin_pin {
  

  @@ -586,7 +586,7 @@
  P9_26_uart_pin: pinmux_P9_26_uart_pin {
  pinctrl-single,pins = <0x180 0x30>; }; /_ Mode 0, Pull-Up, RxActive */
  P9_26_can_pin: pinmux_P9_26_can_pin {

•            pinctrl-single,pins = <0x180  0x32>; };     /\* Mode 2, Pull-Up, RxActive */
  

•            pinctrl-single,pins = <0x180  0x12>; };     /\* Mode 2, dcan1_tx, Pull-Up, TxActive _/
       P9_26_i2c_pin: pinmux_P9_26_i2c_pin {
           pinctrl-single,pins = <0x180  0x33>; };     /_ Mode 3, Pull-Up, RxActive */
       P9_26_pruin_pin: pinmux_P9_26_pruin_pin {
  

Hi,
Im struggling with getting the pin devices on my BeagleBone Black Industrial.
In uEnv.txt I set enable_uboot_cape_universal=1 but only two devices show up.
I had to load cape-universal also with uboot_overlay_addr4=/lib/firmware/univ-bbb-xxx-00A0.dtbo.
No I get a lot of pins under /sys/devices/platform/ocp.
This seems not the right way to do it, but the only way I found that works.
My setup:

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.9.82-ti-r102]
nodejs:[v6.13.0]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/univ-bbb-xxx-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180305.0-0rcnee0~stretch+20180305]
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 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[    1.494309] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[    1.506710] gpio-of-helper ocp:cape-universal: ready

I also tried kernel 4.14 but the behavior was the same.

Using:

##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
dtb=am335x-boneblack-overlay.dtb

Results in:

root@arm:~# 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,univ-all
root@arm:~# config-pin -q P8.18
Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P8_18_pinmux/state

Have been using config-pin for sometime with no problem, but for
some reason am having trouble with P8.40. When I type

config-pin P8.40 in-

I get

P8_40 pinmux file not found!
cape-universala overlay not found
run "config-pin overlay cape-universala" to load the cape

When I type cat /sys/devices/platform/bone_capemgr/slots, I get

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
5: P-O-L- 1 Override Board Name,00A0,Override Manuf,BB-ADC

If I run config-pin overlay cape-universala, I get

config-pin overlay cape-universala
Loading cape-universala overlay
bash: line 0: echo: write error: File exists
Error loading device tree overlay file: cape-universala

Please let me know what I am doing wrong.

Thanks,

Jon Turner

Hello,

I'm trying to use the CAN bus with cape-univerisal.
After booting the BeagleBone executes this commands with sudo:

config-pin P9.24 can
config-pin P9.26 can
modprobe can
modprobe can-dev
modprobe can-raw
ip link set can0 up type can bitrate 250000
ifconfig can0 up

Afterwards with ifconfig, the can should be running:
can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:207

However I'm not able to read the bus with candump or write the bus with cansend. The commands are not returning an error, but nothing happens.

In the utility config-pin, function config_pin(), case $2: "# GPIO with pull-up enabled"
for configuration state HIGH+, code line 989 is : MODE=gpio_pd;

Should that setting not be : MODE=gpio_pu; as in the other 3 pull-up enabled states above it?

Trying to initialize some GPIO pins at boot as pulled-up outputs via a systemd startup script, Ubuntu 18.04 on Beaglebone Black.

I can see that this is universal cape which uses almost all the pins of BeagleBone. Now, after loading this, if we try to use other cape like LCD with this, it gives error. Can you please clarify how to use other capes with universal-cape?

when trying to enable pin P8_33 and P8_35 or P8_41 and P8_42 and i get Invalid mode: qep

I'm am getting:

[  281.131733] bone_capemgr bone_capemgr: part_number 'cape-universala', version 'N/A'
[  281.131779] bone_capemgr bone_capemgr: slot #4: override
[  281.131801] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[  281.131824] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,cape-universala'
[  281.153568] __of_adjust_tree_phandle_references: Illegal property (size) 'fixup' @/__local_fixups__
[  281.163122] bone_capemgr bone_capemgr: slot #4: Failed to resolve tree

kernel version - uname -r: 4.1.33-bone24-00149-gea9e337

command: # echo cape-universaln > /sys/devices/platform/bone_capemgr/slots
result:
[ 2742.848488] bone_capemgr bone_capemgr: part_number 'cape-universaln', version 'N/A'
[ 2742.856294] bone_capemgr bone_capemgr: slot #7: override
[ 2742.861745] bone_capemgr bone_capemgr: Using override eeprom data at slot 7
[ 2742.868819] bone_capemgr bone_capemgr: slot #7: 'Override Board Name,00A0,Override Manuf,cape-universaln'
[ 2742.928609] of_resolve_phandles: Could not find symbol 'gpio4'
[ 2742.934584] bone_capemgr bone_capemgr: slot #7: Failed to resolve tree
bash: echo: write error: Invalid argument

command: # cat /sys/devices/platform/bone_capemgr/slots
result:
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

It also happens if the univ-hdmi cape is not installed. What am doing wrong?
Thanks, in advance...

ChrisB

Hi There,

In the config-pin utility, there is only one "pwm" option for pin P9_28. However P9_28 is either EHRPWM0_syncouin, or ECAPPWM2 output, which is far more useful. P9_28 can be set to PWM output via "echo pwm2 > state" in /sys/devices/platform/ocp/ocp:P9_28_pinmux, but it would be spiffy if the config-pin utility had both options.

Thanks,
terachip

I have a doubt whether this cape can be used for I2C communication. If yes, can you please let me know where the pins P9_17 and P9_18 be mapped? /dev/i2c-1 or /dev/i2c-2?

When I try to load the cape-universala on a BBB with the following kernel

$ uname -a    
Linux arm 4.1.17-ti-rt-r46 #1 SMP PREEMPT RT Sun Feb 7 17:10:04 CET 2016 armv7l GNU/Linux

I get the error

[ 231.974830] bone_capemgr bone_capemgr: part_number 'cape-universala', version 'N/A'
[ 231.982715] bone_capemgr bone_capemgr: slot #5: override
[ 231.991542] bone_capemgr bone_capemgr: Using override eeprom data at slot 5
[ 232.000615] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Override Manuf,cape-universala'
[ 232.096232] of_resolve_phandles: Could not find symbol 'gpio4'
[ 232.102140] bone_capemgr bone_capemgr: slot #5: Failed to resolve tree

My uEnv.txt contains the following:

uname_r=4.1.17-ti-rt-r46
dtb=am335x-boneblack-overlay.dtb

Any help is dearly appreciated.

On the Beaglebone Black Rev C, debian 9.3, 4.4.68-ti-r110, the device tree sources /opt/source/bb.org-overlays/src/arm/cape_universal*-00A0.dts show that when P9_24 and P9_26 are set up as pruin, the pad control should be:
P9_24_pruin_pin: pinmux_P9_24_pruin_pin {
pinctrl-single,pins = <0x184 0x36>; }; /* Mode 6, Pull-Up, RxActive /
and
P9_26_pruin_pin: pinmux_P9_26_pruin_pin {
pinctrl-single,pins = <0x180 0x36>; }; / Mode 6, Pull-Up, RxActive */
The command line: "config-pin p9.24 pruin && config-pin -q p9.24" shows "P9_24 Mode: pruin"
however, the command "grep 984 pins" shows "pin 97 (44e10984.0) 00000026 pinctrl-single" this should be 36 rather than 26 i.e. it shows pull-down rather than pull-up.
The results are similar for p9.26.
Decompiling the corresponding dtbo(s), show that the 26 is the correct(?) value.
Either the dts or dtb(s) should be modified to bring them into sync.
My preference, fwiw, is the pull-up configuration to give two pruin pins a pullup input rather than all pull-downs.

Hello,

Can we add how to automate the config-pin commands . I have tried using
/etc/rc.local
Initd
Monit
But for some reason I wasnt able to have the system work reliably. ( I am using the latest debian wheezy image)

Can you please add this info to wiki?
Thanks a lot
Rifo

Hello!
I have issues using the config-pin -f .bbio command.

My bbio file, generated with the GUI is:
DT-mk-probotix-bb.txt
But, as RobertCNelson recommended, I removed the lines

overlay cape-universal
overlay cape-bone-iio

When I run
sudo /opt/scripts/tools/version.sh
I get

git:/opt/scripts/:[9599f8c47e18db5cdd36ee11355593ecdfe50979]
eeprom:[A335BNLTEIA05116BBBK3FEC]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[Machinekit Debian Image 2019-10-01]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-gf15b99f0b6]:[location: dd MBR]
kernel:[4.19.72-bone-rt-r39]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_video=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 check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.4.20190922.0-0rcnee0~stretch+20190922]
pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]
groups:[machinekit : machinekit adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc admin spi tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet]
dmesg | grep remote
[    1.168353] remoteproc remoteproc0: wkup_m3 is available
[    1.283105] remoteproc remoteproc0: powering up wkup_m3
[    1.283124] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168
[    1.285180] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[    0.736328] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[    0.747789] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

but when using config-pin -f DT-mk-probotix-bb.bbio, I obtain a Invalid mode: in
I attach my uEnv.txt configuration file.
uEnv.txt

I plan to use this BBIO for Machinekit configuration for the Beaglebone Black

thanks in advance

regards,

Sergio Salinas

I'm so confused. I thought one of these was with HDMI disabled, but none of them seem to actually use the HDMI pins. What is going on here?

The README states:

If using a 3.14 or newer kernel, make sure your device tree inclues the pinmux helper entries required for the pins you want to use. If you're using an RCN built kernel (if you don't know, you probably are), these should be present by default.

What are the "pinmux helper entries"?

I came to this repository while researching an answer to a question I posted on Stack Overflow:

https://stackoverflow.com/questions/27892485/how-can-i-edit-a-pinmux-for-beaglebone-black-on-linux-kernel-3-17

The "state" directory is not being created when I load both capes. Only cape-universal creates this specific directory. What could have happened?

Hello,
the new boards are using debian. Is there an patch or version which will work with that ?

I have a systemd service that uses config-pin to load the cape-universal overlay and then uses a file with config-pin to configure the pins. When it starts I get a bunch of noise in the systemd journal like:

Apr 06 10:11:21 beaglebone sudo[547]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/bash -c echo cape-universal > /sys/devices/bone_capemgr.*/slots
Apr 06 10:11:21 beaglebone sudo[547]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 06 10:11:22 beaglebone sudo[547]: pam_unix(sudo:session): session closed for user root
Apr 06 10:11:23 beaglebone sudo[789]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/bash -c echo low > /sys/class/gpio/gpio66/direction
Apr 06 10:11:23 beaglebone sudo[789]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 06 10:11:23 beaglebone sudo[789]: pam_unix(sudo:session): session closed for user root
Apr 06 10:11:23 beaglebone sudo[803]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/bash -c echo gpio > /sys/devices/ocp.3/P8_07_pinmux.14/state
Apr 06 10:11:23 beaglebone sudo[803]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 06 10:11:23 beaglebone sudo[803]: pam_unix(sudo:session): session closed for user root

There are similar messages for each direction/state setting.

Is there anyway to suppress these messages? They add a lot of noise to the journal.

Thanks

There are some pins on beaglebone which uses same PWM module. For example, P8_13 and P8_46 uses same EHRPWM2B module.

Now, I write "pwm" in ocp status of both pins and I also write "6" in /sys/class/pwm/export to export 6th pwm pin. Now if I change duty cycle of that 6th pwm, what will be effect on pin values? Will it give output on both pins?