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.
P2_08 is a PocketBeagle reference, I thought you had a normal BBB?
Regards,
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.
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:~$
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..
Regards,
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:[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.
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/
Regards,
On the link there are more than 10 images.
Is there a document that compares their features?
Either use factory 2020-04-06 image
Does it exist on this page ?
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.
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.
Regards,
Frankly speaking I didn’t find any descriptions except name of kernel.
There are 5 images in “stretch” family:
Sincerely,
Pavel.
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
Regards,
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 TIDLI 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 ?
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.
LXQt is a lightweight desktop based on Qt
TIDL = TI Videos | TI.com
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.
Regards,
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.
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
config-pin -l
config-pin -q
config-pin
debian@beaglebone:~$
Contrary to the version, described in the book of Derek Molloy, there is no such options as -a, -i, -f,
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!
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,