Jeremy, thank you; any chance you can field one more (probably not too
intelligent) question as I'm only starting on git?
git clone git://github.com/adafruit/adafruit-beaglebone-io-python
Fatal Python error: Py_Initialize: Unable to get the locale encoding
File
Jeremy, please ignore; sudo apt-get install git-all did the trick.
On Tuesday, December 10, 2013 4:15:18 PM UTC-5, Bit Pusher wrote:
Jeremy, thank you; any chance you can field one more (probably not too
intelligent) question as I'm only starting on git?
git clone
On 12/10/2013 05:45 PM, Bit Pusher wrote:
Jeremy, please ignore; sudo apt-get install git-all did the trick.
On Tuesday, December 10, 2013 4:15:18 PM UTC-5, Bit Pusher wrote:
Jeremy, thank you; any chance you can field one more (probably not
too intelligent) question as I'm only
Zach, your suggestions worked. I changed fragment@1 to:
fragment@1 {
target = ocp;
__overlay__ {
test_pru_iomap: pru_iomap {
compatible = bone-pinmux-helper;
pinctrl-names = default;
pinctrl-0 = mygpio;
status = okay;
};
};
recompiled, and
On 12/09/2013 08:11 AM, Bit Pusher wrote:
Zach, your suggestions worked. I changed fragment@1 to:
fragment@1 {
target = ocp;
__overlay__ {
test_pru_iomap: pru_iomap {
compatible = bone-pinmux-helper;
pinctrl-names = default;
pinctrl-0 = mygpio;
I'm glad to hear it's working!
Jeremy posted the correct link for the source code. It is written in C
with support for calls through Python.
As far as useful Devicetree links, the Usage one you posted is useful,
though since they write it to be very generic, it can be hard to follow.
A few
Odd, dmesg has no errors, but there is definitely a conflict between the
two.
Someone can correct me if I am wrong as this is a guess based on the
behavior of the system (I'll have to look it up later) but loading a device
tree will dynamically map a bunch of hardware register to the file
Could you post or send me your overlay? I can load it on one of my BBBs and
take a look for you.
Zach
On Tuesday, December 3, 2013 8:39:35 PM UTC-6, Bit Pusher wrote:
If I load my device tree overlay to use the high-speed GPIO pins first, and
then try to read the ADC using Adafruit_BBIO, it
:
Subject: [beagleboard] Re: Deleting Device Tree Overlays
If I load my device tree overlay to use the high-speed GPIO pins first,
and then try to read the ADC using Adafruit_BBIO, it kicks me out of python:
~/pru\ sudo python
Python 2.7.5+ (default, Sep 19 2013, 14:17:30)
[GCC 4.8.1] on linux2
Zach, that would be very good of you; I got if from searching on the net
and it is barely changed (if at all) from what I found (but I didn't record
who I copied it from so I apologize for not giving credit). The *.dts is
below. I might mention that if I load my overlay only, then using cat
Correct me if I am wrong, but it appears that you simply want to use ADC
and PRU pins whose pins DO NOT physically overlap on the board? The
cape-bone-iio device tree only grabs the ADC0-ADC7 pins plus analog power
and ground, so it should not interfere with the PRU pins.
What issue are you
If I load my device tree overlay to use the high-speed GPIO pins first, and
then try to read the ADC using Adafruit_BBIO, it kicks me out of python:
~/pru\ sudo python
Python 2.7.5+ (default, Sep 19 2013, 14:17:30)
[GCC 4.8.1] on linux2
Type help, copyright, credits or license for more
From: Bit Pusher ken.w.mar...@gmail.com
Reply-To: beagleboard@googlegroups.com
Date: Tuesday, December 3, 2013 at 6:39 PM
To: beagleboard@googlegroups.com
Subject: [beagleboard] Re: Deleting Device Tree Overlays
If I load my device tree overlay to use the high-speed GPIO pins first
if you actually run echo -9 $SLOTS as the root user do you still have
this issue?
On Sunday, December 1, 2013 7:42:06 PM UTC-6, Bit Pusher wrote:
I am trying to use both the A/D and the high-speed PRU direct I/O. I have
the A/D working using Adafruit_BBIO.ADC and separately, I can write
I did a sudo su - and then echo -7 /sys/devices/bone_capemgr.9/slots
(as Adafruit_BBIO.ADC had loaded into slot 7). The command appeared to
work, but it also dropped me back to my regular user status so something
went wrong. When, as a regular user, I cat $SLOTS, it locked up the
terminal the
As far as I know trying to remove a device tree overlay while the BBB is
running the OS will always cause a crash.
In order to remove device tree overlays, pass the appropriate parameters to
the kernel via uEnv.txt / uboot
Such as : optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
On 12/2/2013 5:16 PM, William Hermans wrote:
However I get the sense you really do not care about this specifically and
would possibly like to tweak a device tree overlay file ( make changes etc
) remove and then reload the modified version. Unfortunately I do not think
this is possible
Charles, where do you get your information from ? Not trying to be rude or
condescending, or anything of that nature. I only ask because I have actual
hands experience with this feature and have often wondered if there
could be a potential work around( through code ).
On Mon, Dec 2, 2013 at
On 12/2/2013 5:48 PM, William Hermans wrote:
Charles, where do you get your information from ? Not trying to be rude or
condescending, or anything of that nature. I only ask because I have actual
hands experience with this feature and have often wondered if there
could be a potential work
In all honesty, there really should be no hotplug anyhow. At not for this
sort of thing. The device should be powered down when wiring new circuitry
to it anyhow right ?
On Mon, Dec 2, 2013 at 5:15 PM, Charles Steinkuehler
char...@steinkuehler.net wrote:
On 12/2/2013 5:48 PM, William Hermans
20 matches
Mail list logo
