Trouble using config-pin to config P9.28 pin as spi or gpio

[Lindo]

Hi,

I'm trying to use cdsteinkuehler's beaglebone-universal-io to config P9_28-31 as spi interface. After loading cape-universal overlay first, I got the "P9_28 pinmux file not found!" message when I configure P9_28 pin

config-pin P9.28 spi
P9_28 pinmux file not found!
cape-universala overlay not found
run "config-pin overlay cape-universala" to load the cape

I think P9.28 might not actually exported, and then I found that the cape-univeral-00A0.dts file on the github website is different with RobertCNelson's version(I found this file under /opt/source/bb.org-overlays/src/arm/). see detail here: https://www.diffchecker.com/BivnZllE

Is this a bug? or I was doing wrong somewhere? 

Thanks!

Lindo

[Drew Fustini]

On Tue, Jan 24, 2017 at 01:53:17AM -0800, Lindo wrote:
> I'm trying to use cdsteinkuehler's beaglebone-universal-io

> <https://github.com/cdsteinkuehler/beaglebone-universal-io> to config

> P9_28-31 as spi interface. After loading cape-universal overlay first, I
> got the "P9_28 pinmux file not found!" message when I configure P9_28 pin
>
> config-pin P9.28 spi
> P9_28 pinmux file not found!
> cape-universala overlay not found
> run "config-pin overlay cape-universala" to load the cape

You'll need to load cape-universala for P9.28 to be available.

Here is my /boot/uEnv.txt:

cape_enable=bone_capemgr.enable_partno=cape-universala
cmdline=coherent_pool=1M quiet cape_universal=enable
dtb=am335x-boneblack-overlay.dtb
uname_r=4.4.41-ti-r83

I am able to set P9.28 to spi:

root@beaglebone:~# config-pin -l P9.28 spi
default gpio gpio_pu gpio_pd pwm spi pwm2 pruout pruin
root@beaglebone:~# config-pin P9.28 spi
root@beaglebone:~# config-pin -q P9.28
P9_28 Mode: spi


-Drew

[JY Lin]

Thanks, Drew

I'm able to set P9.28 after follow your uEnv.txt content.

But my screen also not working by loading cape-universala (of course it exported all pins),

My idea is cape-universal says it exports all pins not used by HDMIN and eMMC (including audio),

so I should be able to set P9.28 as SPI by loading cape-universal only, but I can't.

And I found that cape-universal dts files are different between Robert's and cdsteinkuehler's, I would like to know do i need to modify dts file by myself?

-Lindo 

Drew Fustini於 2017年1月25日星期三 UTC+8下午3時19分41秒寫道：

[Drew Fustini]

On Wed, Jan 25, 2017 at 4:51 AM, JY Lin <lind...@gmail.com> wrote:
> My idea is cape-universal says it exports all pins not used by HDMIN and
> eMMC (including audio),
> so I should be able to set P9.28 as SPI by loading cape-universal only, but
> I can't.
>
> And I found that cape-universal dts files are different between Robert's and
> cdsteinkuehler's, I would like to know do i need to modify dts file by
> myself?

Charles / Robert:
Should P9.28 be SPI by default?


thanks,
drew

[Charles Steinkuehler]

On 1/27/2017 7:43 PM, Drew Fustini wrote:
>
> Charles / Robert:
> Should P9.28 be SPI by default?

All pins are GPIO by default, with pull up/down set to match the reset
defaults of the processor. To use P9.28 as SPI, in addition to
loading cape-universal, it is necessary to run:

config-pin P9.28 spi

If this does not result in the pinmux being set to spi, it's a bug.

--
Charles Steinkuehler
cha...@steinkuehler.net

[marco....@gmail.com]

Hi all,

I have to bring this thread to life again, as I'm facing the same issue:

all I want to do is to assign p9_29 as "spi_cs" on my BBB running "4.9.78-ti-r94".

Running "config-pin -l p9_28" leads to "default gpio gpio_pu gpio_pd gpio_input spi_cs pwm pruout pruin". So all looks good, as this pin can be used in spi_cs mode.

Now I want to configure the pin to actually work as spi pin:

config-pin p9_28 spi_cs

P9_28 pinmux file not found!

sudo: no askpass program specified, try setting SUDO_ASKPASS

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

The same error is printed when running "config-pin p9_29 spi" or "config-pin p9_31 spi_sclk". However, command "config-pin p9_30 spi" works well.

Would really appreciate if someone can help out here! 

Best regards,

Marco

[Chad Baker]

Did you add the BB-SPIDEV1-00A0.dtbo to the device tree boot list in uEnv.txt?
Chad

--
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/89254b2e-33ca-4ea0-bb9f-3ca89270f89c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rick Mann]

> On Apr 30, 2018, at 08:22 , Chad Baker <cmba...@gmail.com> wrote:
>
> Did you add the BB-SPIDEV1-00A0.dtbo to the device tree boot list in uEnv.txt?

Should that be necessary if one is using CAPE-UNIVERSAL?

> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/30e8fef7-bd03-37a6-b8a9-e4bfad41445d%40gmail.com.

> For more options, visit https://groups.google.com/d/optout.

--
Rick Mann
rm...@latencyzero.com

[Chad Baker]

It is a workaround for a bug, I believe. When I enable the dtbo, I get
the following directory constructed during the boot process
/sys/devices/platform/ocp/ocp:P9_28_pinmux
Without the dtbo, this directory is missing.
Chad

[marco....@gmail.com]

Hi all,

thanks for your responses. I will check once back in office and come back to you with results. 

@cmbaker3/Chad: would it be possibe to share your uEnv.txt file with me (with the dtbo enabled)? Just do be sure that I do the right thing here...

Would be great and thank you so much!!!

Best,

Marco

[Rick Mann]

> On Apr 30, 2018, at 12:47 , Chad Baker <cmba...@gmail.com> wrote:
>
> It is a workaround for a bug, I believe. When I enable the dtbo, I get the following directory constructed during the boot process
> /sys/devices/platform/ocp/ocp:P9_28_pinmux
> Without the dtbo, this directory is missing.

Oh I see, thanks.

> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/22d4ab18-c370-d437-fa7b-c4cf404ea358%40gmail.com.

> For more options, visit https://groups.google.com/d/optout.


--

Rick Mann
rm...@latencyzero.com

[marco....@gmail.com]

Hi guys,

I edited uEnv.txt according to the discussion. In particular I added these lines (I also copied my entire uEnv file in this post; see below):

uboot_overlay_addr0=/lib/firmware/BB-SPIDEV0-00A0.dtbo

uboot_overlay_addr1=/lib/firmware/BB-SPIDEV1-00A0.dtbo

but doesn't change anything; after reboot I still can't use "config-pin p9_28 spi_cs" to enable SPI1.

My system:  uname -a

Linux beaglebone 4.9.78-ti-r94

I also used "/opt/scripts/tools$ ./version.sh" to get more information (please find full log below) and found some interesting lines: 

dmesg | grep pinctrl-single

[    1.404852] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

[    1.648918] pinctrl-single 44e10800.pinmux: pin PIN103 already requested by 481a0000.spi; cannot claim for 48038000.mcasp

[    1.660206] pinctrl-single 44e10800.pinmux: pin-103 (48038000.mcasp) status -22

[    1.667697] pinctrl-single 44e10800.pinmux: could not request pin 103 (PIN103) from group mcasp0_pins  on device pinctrl-single

-> Pin103 is P9_28. 

Any hints what I could try next?

Would really appreciate your help and thank you all in advance!

Best regards,

Marco

##### MY UENV FILE

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

uname_r=4.9.78-ti-r94

#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/BB-SPIDEV0-00A0.dtbo

uboot_overlay_addr1=/lib/firmware/BB-SPIDEV1-00A0.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/<file8>.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 & 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

====================================================

debian@beaglebone:/opt/scripts/tools$ sudo ./version.sh

git:/opt/scripts/:[5935e83ecaedfd4fd88a4b870ffe5af33ded0617]

eeprom:[A335BNLT00C02215BBBK12B4]

model:[TI_AM335x_BeagleBone_Black]

dogtag:[BeagleBoard.org Debian Image 2018-01-28]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.01-00002-g9aa111a004]:[location: dd MBR]

kernel:[4.9.78-ti-r94]

nodejs:[v6.13.0]

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/BB-SPIDEV0-00A0.dtbo]

uboot_overlay_options:[uboot_overlay_addr1=/lib/firmware/BB-SPIDEV1-00A0.dtbo]

uboot_overlay_options:[enable_uboot_cape_universal=1]

pkg:[bb-cape-overlays]:[4.4.20180223.0-0rcnee0~stretch+20180223]

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.404852] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

[    1.648918] pinctrl-single 44e10800.pinmux: pin PIN103 already requested by 481a0000.spi; cannot claim for 48038000.mcasp

[    1.660206] pinctrl-single 44e10800.pinmux: pin-103 (48038000.mcasp) status -22

[    1.667697] pinctrl-single 44e10800.pinmux: could not request pin 103 (PIN103) from group mcasp0_pins  on device pinctrl-single

dmesg | grep gpio-of-helper

[    1.405879] gpio-of-helper ocp:cape-universal: ready

END

[Chad Baker]

My /boot/uEnv.txt differs, I do not use the uboot_overlay_addr lines, they are commented out.
I have a few more lines following the command=coherent ...
The last lines in my file are

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

##Example v3.8.x
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=

##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
cape_enable=bone_capemgr.enable_partno=/lib/firmware/BB-SPIDEV1-00A0.dtbo

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

You might have the cape_enable line as

cape_enable=bone_capemgr.enable_partno=/lib/firmware/BB-SPIDEV0-00A0.dtbo,/lib/firmware/BB-SPIDEV1-00A0.dtbo

Hope this helps,
Chad

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/61eabc32-c58e-460a-9992-e32cf395e19b%40googlegroups.com.

[scott....@gmail.com]

Hello,

I too have run into the issue of not being able to set P9.28 as well using the latest pre-built image from 

https://rcn-ee.com/rootfs/bb.org/testing/2018-12-10/stretch-machinekit/bone-debian-9.6-machinekit-armhf-2018-12-10-4gb.img.xz

To fix the issue, simply disable the uboot audio overlay in /boot/uEnv.txt by uncommenting the line

disable_uboot_overlay_audio=1

And reboot the BBB

You can now set P9.28 as needed.

Best regards,

Scott

[varshne...@gmail.com]

It works! Thanks for your help!

[f.f.r...@gmail.com]

Hi

you should change configuration of pins from HDMI to SPI

type this command in terminal: sudo nano /boot/uEnv.txt

then you should remove # of disable-uboot-overlay-video=1

then you can use from SPI pins

[pstei...@gmail.com]

Hi,

I'm trying to fix an error in my beaglebone green in which several PRU pin directories are not available.  I'm using image 4.19.50-ti-r20. I'm using, Debian 10.2 which I have experienced as working well with the BBB and BBG.  The pins directories that don't show up are a sub-set of the 35 or so real time PRU I/O pins. These pins are supposed to be available are subdirectories of /sys/devices/platform/ocp/, as  follows:

     ocp:P8_11_pinmux

     ocp:P8_12_pinmux*

     ocp:P8_14_pinmux

     ocp:P8_15_pinmux*

     ocp:P8_16_pinmux

     ocp:P8_17_pinmux

     ocp:P8_18_pinmux

     ocp:P9_28_pinmux*

     ocp:P9_29_pinmux*

     ocp:P9_30_pinmux*

     ocp:P9_31_pinmux*

The ones (6 of them) with the asterisk are the real time PRU Input / Output pins that I really really need for my application.

Notes: 

This is on the Beaglebone Green, not the Beaglebone Black, I'll check if the same problem shows up on BBB as well a little later...

This is image 4.19

I have already gone into the /boot/uEnv.txt file and disabled the following: HDMI, audio, emmc.  But I still have this same problem.

Is this a bug in the kernel / image ?  

In reviewing page 211 of Derek Molloy's Exploring Beaglebone book, I can't see a pattern of all these pins belonging to a certain interface, so I cannot even guess  what interface might be causing them to become not available.

Please let me know if you have any ideas on this.

Thanks!!

[Robert Nelson]

On Sat, May 16, 2020 at 8:29 PM <pstei...@gmail.com> wrote:
>
> Hi,

> I'm trying to fix an error in my beaglebone green in which several PRU pin directories are not available. I'm using image 4.19.50-ti-r20. I'm using, Debian 10.2 which I have experienced as working well with the BBB and BBG. The pins directories that don't show up are a sub-set of the 35 or so real time PRU I/O pins. These pins are supposed to be available are subdirectories of /sys/devices/platform/ocp/, as follows:
> ocp:P8_11_pinmux
> ocp:P8_12_pinmux*
> ocp:P8_14_pinmux
> ocp:P8_15_pinmux*
> ocp:P8_16_pinmux
> ocp:P8_17_pinmux
> ocp:P8_18_pinmux
> ocp:P9_28_pinmux*
> ocp:P9_29_pinmux*
> ocp:P9_30_pinmux*
> ocp:P9_31_pinmux*
>
> The ones (6 of them) with the asterisk are the real time PRU Input / Output pins that I really really need for my application.
>
> Notes:
> This is on the Beaglebone Green, not the Beaglebone Black, I'll check if the same problem shows up on BBB as well a little later...
> This is image 4.19
> I have already gone into the /boot/uEnv.txt file and disabled the following: HDMI, audio, emmc. But I still have this same problem.
>
> Is this a bug in the kernel / image ?
>
> In reviewing page 211 of Derek Molloy's Exploring Beaglebone book, I can't see a pattern of all these pins belonging to a certain interface, so I cannot even guess what interface might be causing them to become not available.
>
> Please let me know if you have any ideas on this.

This smells like a mis-configuration, please run:

sudo /opt/scripts/tools/version.sh

and share it's output so we can help debug..

Regards,

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

[Daniel Kulp]

This looks like it's being detected as a BBG Wireless and not a regular BBG.    None of those pins are available on the BBGW.

Dan

[evilwulfie]

LOL   i had this issue on a bunch of boards i bought.

They misprogrammed the eeprom. you will need to write the correct info into
the eeprom. When i notified the company that made the boards they did not give a shit.

--
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/e0a42c84-84c4-42c1-b4d0-a1dfc6be2649%40googlegroups.com.

[pstei...@gmail.com]

It is a BBGW.  Sorry I forgot to mention that initially.  So this is the answer, i.e. these pins are not available on the BBGW, I'm assuming there is no way to make the available either. Thanks Dan.  I'll go to mark your answer as correct.

Paul

To unsubscribe from this group and stop receiving emails from it, send an email to beagl...@googlegroups.com.

[Paul Steinke]

Here is the output of the /sudo /opt/scripts/tools/version.sh

============================================

git:/opt/scripts/:[46d33928c4a396ef472829bcf22761546e550a6f]
eeprom:[A335BNLTGW1ABBGW16061482]
model:[TI_AM335x_BeagleBone_Green_Wireless]
dogtag:[BeagleBoard.org Debian Image 2019-07-07]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-gb96b20de74]:[location: dd MBR]
kernel:[4.19.50-ti-r20]
nodejs:[v10.15.2]
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-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.4.20190610.0-0rcnee0~buster+20190610]
pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~buster+20190227]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~buster+20190327]
pkg:[firmware-ti-connectivity]:[20190114-1]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 cape_universal=enable quiet]
dmesg | grep remote
[    1.866759] remoteproc remoteproc0: wkup_m3 is available
[    1.868907] remoteproc remoteproc1: 4a334000.pru is available
[    1.869492] remoteproc remoteproc2: 4a338000.pru is available
[    2.033739] remoteproc remoteproc0: powering up wkup_m3
[    2.033857] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168
[    2.037391] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
[    1.868907] remoteproc remoteproc1: 4a334000.pru is available
[    1.869094] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully
[    1.869492] remoteproc remoteproc2: 4a338000.pru is available
[    1.869580] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully
dmesg | grep pinctrl-single
[    1.399275] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[    1.411886] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Daniel Kulp]

On Monday, May 18, 2020 at 2:17:36 PM UTC-4, pstei...@gmail.com wrote:

It is a BBGW.  Sorry I forgot to mention that initially.  So this is the answer, i.e. these pins are not available on the BBGW, I'm assuming there is no way to make the available either. Thanks Dan.  I'll go to mark your answer as correct.

Not if you want WIFI and/or bluetooth to work, no.   This is the main reason I regard the BBBW as the worst of the Beagles and strongly recommend my customer/users to not get one.   The BBBW put the wifi adapter on pins that were otherwise unused so all the pins that are pulled out to the header still "work".   The BBGW, on the other hand, uses a bunch of the pins for wifi and bluetooth.   I'm not really sure why.  There is likely some sort of history that I'm not aware of.  Maybe a "wifi" cape (which would obviously need to use pins on the headers) that they then just moved the cape components right onto the beagle as-is.  

Dan