config-pin tool doesn't work.

[Pavel Yermolenko]

Hello,

I tried config-pin example from Exploring BeagleBone, 2nd Ed.:

debian@beaglebone:~$ config-pin -l p2.08
ERROR: open() for /sys/firmware/devicetree/base/ocp/P2_08_pinmux/pinctrl-names failed, No such file or directory
debian@beaglebone:~$

Any comments ?

Thanks.

[Robert Nelson]

P2_08 is a PocketBeagle reference, I thought you had a normal BBB?

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Pavel Yermolenko]

Oh yes, I didn't notice that example is for PocketBeagle.

So, for BBB it should be something like this: config-pin -l p9.08 or config-pin -l p8.08?

Regards.

On Wednesday, September 9, 2020 at 4:45:46 PM UTC+2, RobertCNelson wrote:

[Pavel Yermolenko]

Just tried p8 and p9:

debian@beaglebone:~$ config-pin -l p9.08
ERROR: open() for /sys/firmware/devicetree/base/ocp/P9_08_pinmux/pinctrl-names failed, No such file or directory
debian@beaglebone:~$ config-pin -l p8.08
ERROR: open() for /sys/firmware/devicetree/base/ocp/P8_08_pinmux/pinctrl-names failed, No such file or directory
debian@beaglebone:~$

[Robert Nelson]

On Wed, Sep 9, 2020 at 9:58 AM Pavel Yermolenko <py.o...@sunrise.ch> wrote:
>
> Just tried p8 and p9:
>
> debian@beaglebone:~$ config-pin -l p9.08
> ERROR: open() for /sys/firmware/devicetree/base/ocp/P9_08_pinmux/pinctrl-names failed, No such file or directory

P9.08 is a SYS_5V, definitely not user touchable...

> debian@beaglebone:~$ config-pin -l p8.08
> ERROR: open() for /sys/firmware/devicetree/base/ocp/P8_08_pinmux/pinctrl-names failed, No such file or directory
> debian@beaglebone:~$

debian@bbb-pwr02-ser10:~$ config-pin -l P8.08

Available modes for P8_08 are: default gpio gpio_pu gpio_pd gpio_input timer

Please run:

sudo /opt/scripts/tools/version.sh

and we can help point out what's wrong..

[Pavel Yermolenko]

On Wednesday, September 9, 2020 at 5:19:37 PM UTC+2, RobertCNelson wrote:

Thanks. Here it is:

debian@beaglebone:~$ config-pin -l P8.08

ERROR: open() for /sys/firmware/devicetree/base/ocp/P8_08_pinmux/pinctrl-names failed, No such file or directory

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]
eeprom:[A335BNLT000C2017BBBG0292]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-g07d5700e21]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack.dts]
kernel:[4.19.94-ti-r42]
nodejs:[v10.21.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-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.14.20200814.0-0~buster+20200814]
pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~buster+20200813]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy sudo audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[   30.277069] remoteproc remoteproc0: wkup_m3 is available
[   31.377520] remoteproc remoteproc0: powering up wkup_m3
[   31.377555] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168
[   31.377855] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[    0.452881] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[    0.454615] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
debian@beaglebone:~$

Regards,

Pavel.

[Robert Nelson]

> Thanks. Here it is:
>
> debian@beaglebone:~$ config-pin -l P8.08
> ERROR: open() for /sys/firmware/devicetree/base/ocp/P8_08_pinmux/pinctrl-names failed, No such file or directory
> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> [sudo] password for debian:
> git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]
> eeprom:[A335BNLT000C2017BBBG0292]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-g07d5700e21]:[location: dd MBR]
> UBOOT: Booted Device-Tree:[am335x-boneblack.dts]

Your booting the mainline kernel default device tree, thus config-pin
will not work.

Either use factory 2020-04-06 image or feel free to grab a newer snapshot:

https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/

[Pavel Yermolenko]

On the link there are more than 10 images.

Is there a document that compares their features?

[Pavel Yermolenko]

Either use factory 2020-04-06 image

Does it exist on this page ?

[Pavel Yermolenko]

I've also tried on the image that I built using create-sdcard.sh script from TI SDK (when booted from SD card):

root@am335x-evm:~# config-pin -l P8.08
-sh: config-pin: command not found
root@am335x-evm:~#

Here is link where the procedure is described: Linux SD Card Creation Guide

By the way this Linux image is quite strange as some standard Linux commands aren't recognized, e.g. apt package manager.

Concerning this link
https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/

I've found only one image that matches closely BBB ... at least it follows from its name:

BBB-blank-debian-10.5-console-armhf-2020-09-07-1gb.img.xz

from:

https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-console/

In other "stretch" folders from this repository I didn't find images that start with BBB or am335.

So, the only available image for BBB is BBB-blank-debian-10.5-console-armhf-2020-09-07-1gb.img.xz ?

Sincerely,

Pavel.

[Robert Nelson]

On Thu, Sep 10, 2020 at 2:31 AM Pavel Yermolenko <py.o...@sunrise.ch> wrote:
>
> On the link there are more than 10 images.
> Is there a document that compares their features?

This page has more descriptions:

https://elinux.org/Beagleboard:Latest-images-testing

[Robert Nelson]

On Thu, Sep 10, 2020 at 4:33 AM Pavel Yermolenko <py.o...@sunrise.ch> wrote:
>
> I've also tried on the image that I built using create-sdcard.sh script from TI SDK (when booted from SD card):
>
> root@am335x-evm:~# config-pin -l P8.08
> -sh: config-pin: command not found
> root@am335x-evm:~#

config-pin is a beagleboard.org script...

>
> Here is link where the procedure is described: Linux SD Card Creation Guide
> By the way this Linux image is quite strange as some standard Linux commands aren't recognized, e.g. apt package manager.

They use yocto, apt isn't installed by default..

>
> Concerning this link
> https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/
> I've found only one image that matches closely BBB ... at least it follows from its name:
> BBB-blank-debian-10.5-console-armhf-2020-09-07-1gb.img.xz
> from:
> https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-console/
>
> In other "stretch" folders from this repository I didn't find images that start with BBB or am335.
> So, the only available image for BBB is BBB-blank-debian-10.5-console-armhf-2020-09-07-1gb.img.xz ?

any image with bone-* is for am335x.

[Pavel Yermolenko]

Frankly speaking I didn't find any descriptions except name of kernel.

There are 5 images in "stretch" family:

• Console
• IoT
• IoT TIDL
• LXQt
• LXQt TIDL

I suppose that Console stands for image without graphical environment ?

All others are perhaps with graphical environment. Correct ?

Then IoT stands for image with support of some network protocols, e.g MQTT ?

LXQt probably stands for image wit Qt preinstalled ?

But what signifies TIDL ?

Sincerely,

Pavel.

On Thursday, September 10, 2020 at 5:34:58 PM UTC+2, RobertCNelson wrote:

[Robert Nelson]

On Thu, Sep 10, 2020 at 12:38 PM Pavel Yermolenko <py.o...@sunrise.ch> wrote:
>
> Frankly speaking I didn't find any descriptions except name of kernel.
> There are 5 images in "stretch" family:
>
> Console
> IoT
> IoT TIDL
> LXQt
> LXQt TIDL
>
> I suppose that Console stands for image without graphical environment ?
> All others are perhaps with graphical environment. Correct ?
> Then IoT stands for image with support of some network protocols, e.g MQTT ?
> LXQt probably stands for image wit Qt preinstalled ?
> But what signifies TIDL ?

Console = smallest, very little installed
IoT = bigger than console with out of box BeagleBoard.org stuff
(Cloud9, Node-Red, etc..).
LXQt = IoT + LXQt

TIDL = TI https://training.ti.com/texas-instruments-deep-learning-tidl-overview

[Pavel Yermolenko]

On Thursday, September 10, 2020 at 8:02:53 PM UTC+2, RobertCNelson wrote:

On Thu, Sep 10, 2020 at 12:38 PM Pavel Yermolenko <py....@sunrise.ch> wrote:
>
> Frankly speaking I didn't find any descriptions except name of kernel.
> There are 5 images in "stretch" family:
>
> Console
> IoT
> IoT TIDL
> LXQt
> LXQt TIDL
>
> I suppose that Console stands for image without graphical environment ?
> All others are perhaps with graphical environment. Correct ?
> Then IoT stands for image with support of some network protocols, e.g MQTT ?
> LXQt probably stands for image wit Qt preinstalled ?
> But what signifies TIDL ?

Console = smallest, very little installed

Ok

IoT = bigger than console with out of box BeagleBoard.org stuff
(Cloud9, Node-Red, etc..).

Does exist somewhere the whole list of features ?

LXQt = IoT + LXQt

Frankly speaking, didn't understand.

TIDL = TI https://training.ti.com/texas-instruments-deep-learning-tidl-overview

In the preview they are talking on AM57x. So, does not work for BBB?

Sincerely,

Pavel

P.S. Is my supposition correct that all images except console feature graphical environment ?

[Robert Nelson]

>> Console = smallest, very little installed
>
> Ok
>
>> IoT = bigger than console with out of box BeagleBoard.org stuff
>> (Cloud9, Node-Red, etc..).
>
> Does exist somewhere the whole list of features ?

It's just the default out of box experience, so things really get
added all the time, whether from GSOC or any other code events.

>> LXQt = IoT + LXQt
>
> Frankly speaking, didn't understand.

https://lxqt.github.io/

LXQt is a lightweight desktop based on Qt

>> TIDL = TI https://training.ti.com/texas-instruments-deep-learning-tidl-overview
>
> In the preview they are talking on AM57x. So, does not work for BBB?

TIDL is AM57xx only, it takes a ton of room, so those libraries are
not installed on a base image.

> Sincerely,
> Pavel
> P.S. Is my supposition correct that all images except console feature graphical environment ?

Only the LXQt images have xorg installed.

[Pavel Yermolenko]

After flashing bone-eMMC-flasher-debian-10.5-iot-armhf-2020-08-25-4gb.img the tool config-pin works.

Thanks !

Before I had this image in eMMC:

bone-debian-10.3-iot-armhf-2020-04-06-4gb.img

that I've got from: BeagleBoard.org Latest Firmware Images

Why on BBB-dedicated page they put "mainline kernel default device tree" image ?

Sincerely.

Pavel.

[Pavel Yermolenko]

I was a little hasty to say what works.

The version of config-pin, installed on my system, is quite shrinked.

debian@beaglebone:~$ config-pin -h

GPIO Pin Configurator

Usage: config-pin -c <filename>
       config-pin -l <pin>
       config-pin -q <pin>
       config-pin <pin> <mode>

debian@beaglebone:~$

Contrary to the version, described in the book of Derek Molloy, there is no such options as -a, -i, -f,

[Pavel Yermolenko]

Moreover, the -q option (pin querry) doesn't provide information of the pin mode (direction) and its value:

debian@beaglebone:~$ config-pin -q P9.12

Current mode for P9_12 is:     gpio

debian@beaglebone:~$

In fact, there is no information at all!

[Robert Nelson]

it got rewritten and replaced by something that's maintainable.

Patches welcome..

https://github.com/beagleboard/bb.org-overlays/tree/master/tools/pmunts_muntsos



Regards,

> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c215f6ce-3dfb-4cf0-8bec-882bc536133eo%40googlegroups.com.

[Robert Nelson]

ps the in/out macro's are implemented now:

https://github.com/beagleboard/bb.org-overlays/commits/master/tools/pmunts_muntsos

[Pavel Yermolenko]

Hi Robert,

I've tried the version from your link.

It seems that nothing changed:

debian@beaglebone:~$ wget https://raw.githubusercontent.com/pmunts/muntsos/master/bootkernel/initramfs/config-pin.c

--2020-09-14 14:52:27--  https://raw.githubusercontent.com/pmunts/muntsos/master/bootkernel/initramfs/config-pin.c
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.112.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.112.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5571 (5.4K) [text/plain]
Saving to: 'config-pin.c'

config-pin.c                         100%[===================================================================>]   5.44K  --.-KB/s    in 0.002s  

2020-09-14 14:52:27 (2.78 MB/s) - 'config-pin.c' saved [5571/5571]

debian@beaglebone:~$ ls
bin  config-pin.c  exploringbb
debian@beaglebone:~$ gcc config-pin.c -o config-pin
debian@beaglebone:~$ ls
bin  config-pin  config-pin.c  exploringbb
debian@beaglebone:~$ ./config-pin -i P9.12
ERROR: open() for /sys/devices/platform/ocp/ocp:-I_pinmux/state failed, No such file or directory
debian@beaglebone:~$ ./config-pin -h

GPIO Pin Configurator

Usage: config-pin -c <filename>
       config-pin -l <pin>
       config-pin -q <pin>
       config-pin <pin> <mode>

debian@beaglebone:~$

Sincerely,

Pavel

On Monday, September 14, 2020 at 4:48:35 PM UTC+2, RobertCNelson wrote:

it got rewritten and replaced by something that's maintainable.

Patches welcome..

https://github.com/beagleboard/bb.org-overlays/tree/master/tools/pmunts_muntsos



Regards,

On Mon, Sep 14, 2020 at 8:23 AM Pavel Yermolenko <py....@sunrise.ch> wrote:
>
> Moreover, the -q option (pin querry) doesn't provide information of the pin mode (direction) and its value:
>
> debian@beaglebone:~$ config-pin -q P9.12
>
> Current mode for P9_12 is:     gpio
>
> debian@beaglebone:~$
>
> In fact, there is no information at all!
>
> On Monday, September 14, 2020 at 3:15:26 PM UTC+2, Pavel Yermolenko wrote:
>>
>> I was a little hasty to say what works.
>> The version of config-pin, installed on my system, is quite shrinked.
>>
>> debian@beaglebone:~$ config-pin -h
>>
>> GPIO Pin Configurator
>>
>> Usage: config-pin -c <filename>
>>        config-pin -l <pin>
>>        config-pin -q <pin>
>>        config-pin <pin> <mode>
>>
>> debian@beaglebone:~$
>>
>> Contrary to the version, described in the book of Derek Molloy, there is no such options as -a, -i, -f,
>
> --
> 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 beagl...@googlegroups.com.

[Robert Nelson]

On Mon, Sep 14, 2020 at 9:57 AM Pavel Yermolenko <py.o...@sunrise.ch> wrote:
>
> Hi Robert,
>
> I've tried the version from your link.
> It seems that nothing changed:

patches welcome

Regards,

[Pavel Yermolenko]

Which version of config-pin did Derek Molloy use in his book?

It no longer exists ?

On Monday, September 14, 2020 at 5:03:51 PM UTC+2, RobertCNelson wrote:

[Robert Nelson]

On Mon, Sep 14, 2020 at 10:08 AM Pavel Yermolenko <py.o...@sunrise.ch> wrote:
>
> Which version of config-pin did Derek Molloy use in his book?
> It no longer exists ?

It's stored locally under:

/opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin

cp it to /usr/local/bin/

[Dennis Lee Bieber]

On Mon, 14 Sep 2020 06:15:25 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Pavel Yermolenko

<py.ohayo-FOWRGO...@public.gmane.org> wrote:

>I was a little hasty to say what works.

>The version of *config-pin*, installed on my system, is quite shrinked.
>

The older config-pin is, as I recall, a shell script. The current
config-pin is a compiled executable.

debian@beaglebone:~$ which config-pin
/usr/bin/config-pin
debian@beaglebone:~$ sudo find / -iname "config-pin*"
[sudo] password for debian:
/opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
/opt/source/bb.org-overlays/tools/pmunts_muntsos/config-pin.c
/usr/bin/config-pin


debian@beaglebone:~$
/opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
config-pin [-a] <pin> <mode>
Set <pin> to <mode>, configuring pin multiplexing and optionally
configuring the gpio. Valid <mode> strings vary based on <pin>,
however all pins have a default and gpio mode. The default mode is
the reset state of the pin, with the pin mux set to gpio, the pull
up/down resistor set to it's reset value, and the pin receive buffer
enabled. To setup gpio, the following <mode> strings are all valid:

gpio :
Set pinmux to gpio, existing direction and value unchanged
in | input:
Set pinmux to gpio and set gpio direction to input
out | output :
Set pinmux to gpio and set gpio direction to output
hi | high | 1 :
Set pinmux to gpio and set gpio direction to output driving
high
lo | low | 0 :
Set pinmux to gpio and set gpio direction to output driving low

To enable pull-up or pull-down resistors, a suffex may be appended to
any of the above gpio modes. Use + or _pu to enable the pull-up
resistor
and - or _pd to enable the pull-down resistor. Examples:

in+ | in_pu:
Enable pull-up resistor and setup pin as per input, above.
hi- | hi_pd:
Enable pull-down resistor and setup pin as per high, above.
While the pull-down resistor will be enabled, it will not do
much
until application software changes the pin direction to input.

config-pin -l <pin>
list valid <mode> values for <pin>

config-pin -i <pin>
show information to <pin>

config-pin -q <pin>
query pin and report configuration details

config-pin -f [file]
Read list of pin configurations from file, one per line
Comments and white-space are allowed
With no file, or when file is -, read standard input.
config-pin -h
Display this help text

debian@beaglebone:~$ config-pin

GPIO Pin Configurator

Usage: config-pin -c <filename>
config-pin -l <pin>
config-pin -q <pin>
config-pin <pin> <mode>

debian@beaglebone:~$

>Contrary to the version, described in the book of Derek Molloy, there is no

>such options as *-a*, *-i*, *-f*,

ANYTIME you are following a book and encounter a difference, you need
to study which version of the OS was present at that time. Even the 2nd
Edition of the book was likely behind a version or two by the time it was
printed.

Per page 32 of the book, it was written when Debian Stretch was still
in use. Standard images have been Debian Buster since April of this year
(though the config-pin change might have occurred anytime in 2019, or even
late 2018, as the 2nd edition shipped [from Amazon] January 14 2019). Based
on some screen captures, the book was using a February 2018 image, and the
examples were run in April 2018. That's a whole 2.5 years ago.

{Side note: Raspberry-Pi went to Buster in the summer of 2019, about two
weeks before Debian Buster was officially released -- the R-Pi 4B was
different enough that all the work to get it to run was done on pre-release
Buster.}

>Moreover, the -q option (pin querry) doesn't provide information of the pin
>mode (direction) and its value:
>
>debian@beaglebone:~$ config-pin -q P9.12
>
>Current mode for P9_12 is: gpio
>
>debian@beaglebone:~$
>
>In fact, there is no information at all!

debian@beaglebone:~$
/opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q
P9.12
P9_12 Mode: default Direction: in Value: 1
debian@beaglebone:~$


--
Dennis L Bieber

[Pavel Yermolenko]

Ok, thanks !

On Monday, September 14, 2020 at 5:12:23 PM UTC+2, Dennis Bieber wrote:

On Mon, 14 Sep 2020 06:15:25 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Pavel Yermolenko

[Szabó Benedek Ákos]

Hi there!

I have the same problem, with my BeagleBone.

When I run the command:

root@beaglebone:~# /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q P2_06

I get this error msg:

P2_06 pinmux file not found!

bash: /sys/devices/platform/ocp/ocp*P2_06_pinmux/state: No such file or directory

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

As I read, I only have to flash a new image which is bone-eMMC-flasher-debian-10.5-iot-armhf-2020-08-25-4gb.img as Pavel mentioned it?

Then it will work?

Thx

Regards,

Bence

py.o...@sunrise.ch a következőt írta (2020. szeptember 14., hétfő, 17:29:19 UTC+2):

Ok, thanks !

On Monday, September 14, 2020 at 5:12:23 PM UTC+2, Dennis Bieber wrote:

On Mon, 14 Sep 2020 06:15:25 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Pavel Yermolenko

[Szabó Benedek Ákos]

Tried flashing the new image, didnt boot with the eMMC flasher image.

Also tried the new IoT image, still the same error :(

Can anyone help?