I can't unexport them.
root@bone-5eca:/sys/class/gpio# echo 116 > unexport
bash: echo: write error: Invalid argument
--Mark A. Yoder, PhD
Electrical and Computer Engineering
Rose-Hulman Institute of Technology
812-233-3219
From: Robert Nelson
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
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
On Wed, Nov 29, 2017 at 5:03 PM, Sunny Mathew wrote:
> Hey Robert, thanks for responding promptly. Here is the output:
>
> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
>
Hi,
I'm currently trying to modify the (custom) MLO of my bare metal
application in order to work with the PocketBeagle. At the moment this MLO
works fine with BBB.
According to the (incredibly small) manual of the Octavo SoC I changed the
initialisation of the DDR and EMIF registers - but
I have discovered that gpsd was causing the PPS device to get created for
/dev/ttyS4. I had to recompile gpsd to turn off PPS support and that solved
that particular part of the problem.
The issue I'm running into now is that when systemd goes to start chronyd,
the kernel has not yet created
> On Nov 29, 2017, at 1:09 PM, Robert Nelson wrote:
>
> On Wed, Nov 29, 2017 at 12:02 PM, Luke Stras
> wrote:
>> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-SPIDEV0-00A0.dtbo]
>
> This ^ disables cape universal…
Ah, I
On Nov 29, 2017 12:09 PM, "Robert Nelson" wrote:
On Wed, Nov 29, 2017 at 12:02 PM, Luke Stras
wrote:
> I am feeling like an idiot here — this used to work a few months back,
but I haven’t touched it in a while, and have done some system
On Wed, Nov 29, 2017 at 12:02 PM, Luke Stras wrote:
> I am feeling like an idiot here — this used to work a few months back, but I
> haven’t touched it in a while, and have done some system updates in the
> meanwhile.
>
> I can’t seem to get config-pin to do anything
I am feeling like an idiot here — this used to work a few months back, but I
haven’t touched it in a while, and have done some system updates in the
meanwhile.
I can’t seem to get config-pin to do anything useful for me:
debian@beaglebone:~$ sudo config-pin P9-23 lo
[sudo] password for debian:
Hi Jason,
Thanks for your information.
I think we will use the U-Boot overlay method as you suggest.
I was comparing the table
(https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual#825-pin-usage.
) with the other sources.
Regards
Andrew
From: Jason Kridner
On Wed, Nov 29, 2017 at 11:23 AM, RPGamer wrote:
> You said that I must patch the kernel. Is that needed with this?
> Can I use the RoboticsCape library to program the BB blue? Thank you.
Correct, "you" must patch the kernel if you use someone's else's Kernel tree..
You said that I must patch the kernel. Is that needed with this?
Can I use the RoboticsCape library to program the BB blue? Thank you.
Regards,
Cyril F.
Le mercredi 29 novembre 2017 18:09:08 UTC+1, RobertCNelson a écrit :
>
> On Wed, Nov 29, 2017 at 10:47 AM, RPGamer >
On Wed, Nov 29, 2017 at 10:47 AM, RPGamer wrote:
> Is there any BB blue kernel defconfig file you recommand to use?
> What patches are needed?
https://github.com/beagleboard/linux
Pick any of these branches:
4.4
4.4-rt
4.9
4.9-rt
4.14
4.14-rt
and use the
It's not part of Buildroot.
Le mercredi 29 novembre 2017 13:04:34 UTC+1, William Hermans a écrit :
>
>
>
> On Tue, Nov 28, 2017 at 5:47 PM, Robert Nelson > wrote:
>
>> On Tue, Nov 28, 2017 at 5:32 PM, RPGamer > > wrote:
>> > OK so what's the official
Is there any BB blue kernel defconfig file you recommand to use?
What patches are needed?
Best regards,
Cyril F.
Le mercredi 29 novembre 2017 01:48:24 UTC+1, RobertCNelson a écrit :
>
> On Tue, Nov 28, 2017 at 5:32 PM, RPGamer > wrote:
> > OK so what's the official
Always CC beagleboard@googlegroups.com when e-mailing me a support
question, otherwise your e-mail is 99.994% sure to go into the dustbin.
I've taken the liberty of putting you in BCC and removing identifying
information in order to provide you with a response that I believe might
benefit both you
Hi , i am a newbie with beaglebone black.I have installed freertos on
beagle bone black .Now i want to use wilink wl1835 cape with beagle bone
black running freertos.Can you provide any links to guide me how to use
wilink wl1835 cape with beagle bone black with example code running on
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
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
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
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
I have a BeagleBone Green Wireless that I would like to replicate onto
multiple other boards. To do this I was thinking of extracting the contents
to an SD card and using that SD card as a master to flash the other boards.
I'm trying to follow the instructions here:
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
I opened a ticket with Microchip on this more then 6 months ago and just
got the reply below.
TLDR; "Since it took us so long to get to this issue, we assume you don’t
care anymore that our silicon doesn’t work correctly”.
Wow.
--
AUTOMATED MESSAGE - SEE RESPONSE METHODS BELOW
On Tue, Nov 28, 2017 at 5:47 PM, Robert Nelson
wrote:
> On Tue, Nov 28, 2017 at 5:32 PM, RPGamer wrote:
> > OK so what's the official kernel sources for the Blue?
> >
> > I tried different sources, the one provided by Buildroot and this one :
> >
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
27 matches
Mail list logo