I'm trying to understand the current state of device tree overlays. Is it
correct that the cape manager is now obsolete, and device tree overlays
should be set up through /boot/uEnv.txt? What about config-pin? Is that an
alternative to device tree overlays, or something orthogonal?
The system I
On Tue, Nov 28, 2017 at 12:45 AM, Ken Shirriff wrote:
> I'm trying to understand the current state of device tree overlays. Is it
> correct that the cape manager is now obsolete, and device tree overlays
> should be set up through /boot/uEnv.txt? What about config-pin? Is that an
> alternative to
I've just downloaded the latest test iot image (BeagleBoard.org Debian
Image 2017-11-26) and tried config-pin on the BeagleBone Black
bone$ *config-pin -l P9_31 spi_sclk*
default gpio gpio_pu gpio_pd spi_sclk pwm pruout pruin
So far so good, but I want to use SPI, so
bone$ *sudo config-pin P9_3
On Tue, Nov 28, 2017 at 6:38 PM, Mark A. Yoder wrote:
> I've just downloaded the latest test iot image (BeagleBoard.org Debian Image
> 2017-11-26) and tried config-pin on the BeagleBone Black
>
> bone$ config-pin -l P9_31 spi_sclk
> default gpio gpio_pu gpio_pd spi_sclk pwm pruout pruin
>
> So far
On Tuesday, November 28, 2017 at 12:33:35 PM UTC-5, RobertCNelson wrote:
> On Tue, Nov 28, 2017 at 12:45 AM, Ken Shirriff wrote:
> > I'm trying to understand the current state of device tree overlays. Is it
> > correct that the cape manager is now obsolete, and device tree overlays
> > should
Hi Rick,
> Is there any better documentation than this somewhere? I have a custom audio
> (and other stuff) cape I was working on a couple years ago and had to put
> aside. I would like to get back to that soon, and I see now that there's a
> new way to configure it. Is there anything that talk
bone $ *uname -r*
4.9.63-ti-r79
Looks like many aren't synced. How do I sync them?
bone $ *sudo config-pin P9_30 spi*
P9_30 pinmux file not found!
bash: /sys/devices/platform/ocp/ocp*P9_30_pinmux/state: No such file or
directory
Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_30_pinm
On Tue, Nov 28, 2017 at 7:47 PM, Mark A. Yoder wrote:
> bone $ uname -r
> 4.9.63-ti-r79
>
> Looks like many aren't synced. How do I sync them?
>
> bone $ sudo config-pin P9_30 spi
> P9_30 pinmux file not found!
> bash: /sys/devices/platform/ocp/ocp*P9_30_pinmux/state: No such file or
> directory
bone$ *dpkg --list | grep cape*
ii bb-cape-overlays
4.4.20171120.0-0rcnee1~stretch+20171120 armhfDevice tree
overlays for Beaglebone.
ii roboticscape
0.3.4-git20170602-0rcnee4~stretch+20171108armhfRobotics Cape
Library and
On Tue, Nov 28, 2017 at 8:02 PM, Mark A. Yoder wrote:
> bone$ dpkg --list | grep cape
> ii bb-cape-overlays
> 4.4.20171120.0-0rcnee1~stretch+20171120 armhfDevice tree
> overlays for Beaglebone.
> ii roboticscape
> 0.3.4-git20170602-0rcnee4~stretch+20171108armhfRobotics
On Tue, Nov 28, 2017 at 7:06 PM, Robert Nelson
wrote:
> On Tue, Nov 28, 2017 at 8:02 PM, Mark A. Yoder
> wrote:
> > bone$ dpkg --list | grep cape
> > ii bb-cape-overlays
> > 4.4.20171120.0-0rcnee1~stretch+20171120 armhfDevice tree
> > overlays for Beaglebone.
> > ii roboticscape
That fixed it. Thanks...
Now I see all sorts of gpios are already exported.
export gpio114 gpio13 gpio22 gpio30 gpio46 gpio50 gpio66 gpiochip0
gpio110 gpio115 gpio14 gpio23 gpio31 gpio47 gpio51 gpio67 gpiochip32
gpio111 gpio116 gpio15 gpio26 gpio4 gpio48 gpio60 gpio68 gp
On Wed, Nov 29, 2017 at 7:27 AM, Mark A. Yoder
wrote:
> That fixed it. Thanks...
>
> Now I see all sorts of gpios are already exported.
> export gpio114 gpio13 gpio22 gpio30 gpio46 gpio50 gpio66 gpiochip0
> gpio110 gpio115 gpio14 gpio23 gpio31 gpio47 gpio51 gpio67
> gpiochip32
>
Unfortunately, that's the command that gives me the error message. Someone
else has control of those gpio's and I can unexport them, even as root.
--Mark
On Wednesday, November 29, 2017 at 9:34:35 AM UTC-5, William Hermans wrote:
>
>
>
> On Wed, Nov 29, 2017 at 7:27 AM, Mark A. Yoder > wrote:
On Wed, Nov 29, 2017 at 9:01 AM, Mark A. Yoder wrote:
> Unfortunately, that's the command that gives me the error message. Someone
> else has control of those gpio's and I can unexport them, even as root.
>
> --Mark
cape-universal exported them..
Something like this should work:
https://gist.g
In fact, that is the LCD display I have working on the Blue and am trying
to move to the Black.
I need to find 3 gpio pins that cape-universal hasn't taken. Any
suggestions?
--Mark
On Wednesday, November 29, 2017 at 10:05:35 AM UTC-5, RobertCNelson wrote:
>
> On Wed, Nov 29, 2017 at 9:01 AM
I see that if I edit */boot/uEnv.txt* and comment out:
#enable_uboot_cape_universal=1
I can then access all sorts of gpio pins. But now I can't run config-pin on
them since there is no pinmux entry in /sys/devices/platform/ocp.
Is there a way to free up a few gpio pins to drive the LCD and keep t
On Wed, Nov 29, 2017 at 8:08 PM, Mark A. Yoder wrote:
> I see that if I edit /boot/uEnv.txt and comment out:
> #enable_uboot_cape_universal=1
> I can then access all sorts of gpio pins. But now I can't run config-pin on
> them since there is no pinmux entry in /sys/devices/platform/ocp.
>
> Is the
on
Sent: Wednesday, November 29, 2017 9:22:10 PM
To: Beagle Board; Mark Yoder
Subject: Re: [beagleboard] Is cape manager obsolete? What about device tree
overlays?
On Wed, Nov 29, 2017 at 8:08 PM, Mark A. Yoder wrote:
> I see that if I edit /boot/uEnv.txt and comment out:
> #enable_uboot_cape_u
Thanks for the explanation, but could you elaborate a bit more on it?
As far as I understand the world as it is now works this way:
0- If you are running anything beyond kernel 4.1 you should be using uboot
overlays. Be careful to load the latest bb-cape overlays and be sure that
uboot is the
On Thu, Nov 30, 2017 at 11:40 PM, Johan Henselmans
wrote:
> Thanks for the explanation, but could you elaborate a bit more on it?
>
> As far as I understand the world as it is now works this way:
>
> 0- If you are running anything beyond kernel 4.1 you should be using uboot
> overlays. Be careful
lid argument
>
>
> --Mark A. Yoder, PhD
> Electrical and Computer Engineering
> Rose-Hulman Institute of Technology
> 812-233-3219
> --
> *From:* Robert Nelson >
> *Sent:* Wednesday, November 29, 2017 9:22:10 PM
> *To:* Beagle Board; Mark Y
*From:* Robert Nelson
>> *Sent:* Wednesday, November 29, 2017 9:22:10 PM
>> *To:* Beagle Board; Mark Yoder
>> *Subject:* Re: [beagleboard] Is cape manager obsolete? What about device
>> tree overlays?
>>
>> On Wed, Nov 29, 2017 at 8:08 PM, Mark A. Yoder
Hi
I am having the same problem and can't solve it. Here is the output of "*sudo
/opt/scripts/tools/version.sh "*
*git:/opt/scripts/:[0aa8fd09a1821f6f9197aada6ec69e9746e91f67]*
*eeprom:[A335BNLT00C05016BBBK1BDB]*
*model:[TI_AM335x_BeagleBone_Black]*
*dogtag:[rcn-ee.net console Ubuntu Image 2018-
gument
>>>
>>>
>>> --Mark A. Yoder, PhD
>>> Electrical and Computer Engineering
>>> Rose-Hulman Institute of Technology
>>> 812-233-3219
>>> --
>>> *From:* Robert Nelson
>>> *Sent:* Wedn
On Tue, Oct 9, 2018 at 9:29 AM wrote:
>
> Hi
>
> I am having the same problem and can't solve it. Here is the output of "sudo
> /opt/scripts/tools/version.sh "
>
> git:/opt/scripts/:[0aa8fd09a1821f6f9197aada6ec69e9746e91f67]
> eeprom:[A335BNLT00C05016BBBK1BDB]
> model:[TI_AM335x_BeagleBone_Black]
On Tue, Oct 9, 2018 at 9:59 AM Fred Gomes wrote:
>
> The problem is that I need to configure the pins P28 - P31 (Because I am
> using the SPI1) and when I ran "config-pin P9.31 spi_sclk" I got the
> following error: "Cannot write pinmux file:
> /sys/devices/platform/ocp/ocp*P9_31_pinmux/state"
27 matches
Mail list logo
