Re: [beagleboard] Re: Trouble using config-pin to config P9.28 pin as spi or gpio

2020-05-18 Thread 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


 

>
> Paul
>
> On Monday, May 18, 2020 at 11:06:36 AM UTC-5, evilwulfie wrote:
>>
>> 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.
>>
>>
>> On 5/18/2020 6:47 AM, Daniel Kulp wrote:
>>
>>
>> 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
>>
>>
>> On Saturday, May 16, 2020 at 9:29:10 PM UTC-4, 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.
>>> Thanks!!
>>>
>>>
>>>
>>> On Tuesday, January 24, 2017 at 6:42:30 AM UTC-6, Lindo wrote: 

 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

 -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/e0a42c84-84c4-42c1-b4d0-a1dfc6be2649%40googlegroups.com
>>  
>> 
>> .
>>
>>
>>

-- 
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

Re: [beagleboard] Re: Trouble using config-pin to config P9.28 pin as spi or gpio

2020-05-18 Thread 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-2-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:[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


On Sat, May 16, 2020 at 8:33 PM Robert Nelson 
wrote:

> On Sat, May 16, 2020 at 8:29 PM  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/
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CACbAPonwhQWsBAAkZxMkhp_0jaMC7bgKNR3sQCvWuZ0MfNpJ%2Bg%40mail.gmail.com.

Re: [beagleboard] Re: Trouble using config-pin to config P9.28 pin as spi or gpio

2020-05-18 Thread psteinke66 
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

On Monday, May 18, 2020 at 11:06:36 AM UTC-5, evilwulfie wrote:
>
> 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.
>
>
> On 5/18/2020 6:47 AM, Daniel Kulp wrote:
>
>
> 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
>
>
> On Saturday, May 16, 2020 at 9:29:10 PM UTC-4, 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.
>> Thanks!!
>>
>>
>>
>> On Tuesday, January 24, 2017 at 6:42:30 AM UTC-6, Lindo wrote: 
>>>
>>> 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
>>>
>>> -- 
> 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 .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/e0a42c84-84c4-42c1-b4d0-a1dfc6be2649%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4842b3c9-6ab5-4937-b2e7-8cf68742f6e2%40googlegroups.com.

Re: [beagleboard] Re: Trouble using config-pin to config P9.28 pin as spi or gpio

2020-05-18 Thread 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.



On 5/18/2020 6:47 AM, Daniel Kulp wrote:


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


On Saturday, May 16, 2020 at 9:29:10 PM UTC-4, 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.
Thanks!!



On Tuesday, January 24, 2017 at 6:42:30 AM UTC-6, Lindo wrote:

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

--
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+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e0a42c84-84c4-42c1-b4d0-a1dfc6be2649%40googlegroups.com 
.


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1af56d1e-7bdd-be66-9de4-18850812c7dc%40gmail.com.

[beagleboard] Re: Trouble using config-pin to config P9.28 pin as spi or gpio

2020-05-18 Thread 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


On Saturday, May 16, 2020 at 9:29:10 PM UTC-4, 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.
> Thanks!!
>
>
>
> On Tuesday, January 24, 2017 at 6:42:30 AM UTC-6, Lindo wrote:
>>
>> 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
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e0a42c84-84c4-42c1-b4d0-a1dfc6be2649%40googlegroups.com.

Re: [beagleboard] Re: Trouble using config-pin to config P9.28 pin as spi or gpio

2020-05-16 Thread Robert Nelson 
On Sat, May 16, 2020 at 8:29 PM  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/

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgYwF9qddfpbTM_oWo%2BmUL%3Ddh6hsoHw0RVsreRr4%2BKrTg%40mail.gmail.com.

[beagleboard] Re: Trouble using config-pin to config P9.28 pin as spi or gpio

2020-05-16 Thread psteinke66 
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!!



On Tuesday, January 24, 2017 at 6:42:30 AM UTC-6, Lindo wrote:
>
> 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
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/679f4102-ae67-4938-86e8-63d972109764%40googlegroups.com.

[beagleboard] Re: Trouble using config-pin to config P9.28 pin as spi or gpio

2019-12-09 Thread f . f . rayan97 
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

On Tuesday, January 24, 2017 at 4:12:30 PM UTC+3:30, Lindo wrote:
>
> 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
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e8282a14-66f8-4b6f-8835-b8322c1872b6%40googlegroups.com.