On 5/8/2013 10:34 AM, Ian McMahon wrote:
> I started with Michaels's BBW work here:
>
> http://static.mah.priv.at/public/beaglebone/
>
> The BBW 3.2 kernel won't work on the BBB, so I had to build a kernel. Here's
> a working 3.8.10 kernel for BBB:
>
> kernel-3.8.10-vanilla.tgz
>
> It's a vanilla
I started with Michaels's BBW work here:
http://static.mah.priv.at/public/beaglebone/
The BBW 3.2 kernel won't work on the BBB, so I had to build a kernel. Here's a
working 3.8.10 kernel for BBB:
kernel-3.8.10-vanilla.tgz
It's a vanilla kernel; there's no xenomai for 3.8 yet, so you're not go
On Sun, May 5, 2013 at 4:12 AM, Ian McMahon wrote:
> I started a repository of test code here:
>
> https://bitbucket.org/imcmahon/beagleboneblack-gpio_driver
>
> Is there a concise discussion somewhere of how to get a development system
for linuxcnc running for BBB?
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Start with the README and README.stepgen files in
configs/pru-examples, that should be enough to get a couple pins
twiddling.
Note I have a setup.sh script in that directory that puts pins into
the proper mode for PRU access. This is the nasty, dange
I'd like to spend a little bit of time messing with your PRU code... got any
tips on the best way to get started with it?
On May 7, 2013, at 5:04 PM, Charles Steinkuehler
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Awesome! I'm looking forward to playing with this!
>
> ...n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Awesome! I'm looking forward to playing with this!
...now where did I put all that free time?!? :)
On 5/7/2013 2:52 PM, Ian McMahon wrote:
> There's a mostly functionally complete bb_gpio driver in the
> bb-hal-gpio branch:
>
> http://git.mah.priv
There's a mostly functionally complete bb_gpio driver in the bb-hal-gpio branch:
http://git.mah.priv.at/gitweb?p=emc2-dev.git;a=shortlog;h=refs/heads/bb-hal-gpio
It doesn't solve all pin-conflict issues yet, but the good news is it seems to
fail in pinmuxing if a pin isn't available. The crash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/5/2013 8:30 PM, Ian McMahon wrote:
> What Michael and I had discussed was using the sysfs mechanism to
> request the pins at driver load, and only "claim" the pins that
> succeed, or fail if a user has asked for pins that we can't claim,
> or so
The kernel GPIO driver actually sort of gives you some accounting like this...
to get access to a GPIO, you echo the pin number into /sys/class/gpio/export,
and that reserves the pin for GPIO access (using gpio_request() i believe) and
creates the sysfs files to interact with it. If anyone els
Steve Stallings wrote:
>> -Original Message-
>> From: Jon Elson [mailto:el...@pico-systems.com]
>>
>>
>> Or, you could do it as 5 fields of 8 characters and the last
>> one 6 chars.
>> That would be a lot more manageable.
>>
>> Jon
>>
>>
>
> Well I got something different from t
Dave,
Thanks for all the great information!
I especially like your idea of thinking of the BBB as a BBW with an eMMC/HDMI
cape on it.
Ian
On May 5, 2013, at 2:52 PM, David Bagby wrote:
> Hi Ian,
>
> I read your post (and the IRC conversation log that Michael pointed to a
> couple of days a
> -Original Message-
> From: Jon Elson [mailto:el...@pico-systems.com]
> Sent: Sunday, May 05, 2013 5:21 PM
> To: d...@calypsoventures.com; EMC developers
> Subject: Re: [Emc-developers] Some initial BBB GPIO code
>
> David Bagby wrote:
> > Hi Ian,
> >
David Bagby wrote:
> Hi Ian,
>
> I read your post (and the IRC conversation log that Michael pointed to
> a couple of days ago) and I too suspect that a 46 char string is
> probably not the preferred interface for setting Pin states or mux
> modes on a Bone board.
>
Or, you could do it as 5 fiel
On 5/5/2013 3:09 PM, David Bagby wrote:
> Wow, That was all nicely formatted and readable, then I pasted into
> Thunderbird and hit send
Funny, David, I found your message so readable I didn't even notice the
reformatting---or maybe I'm just desensitized to the problem because
it's so common
Wow, That was all nicely formatted and readable, then I pasted into
Thunderbird and hit send
Please excuse the odd format conversions that crept in (bold turned to
*, and underlined stuff only underlined the 2st and last chars of the
phrase and sentence periods seem to have lost spaces after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/5/2013 3:12 AM, Ian McMahon wrote:
> I started a repository of test code here:
>
> https://bitbucket.org/imcmahon/beagleboneblack-gpio_driver
Great start! Keep up the good work!
> The complexity that I see in this is that, from a user's point
On 5 May 2013, at 09:12, Ian McMahon wrote:
> I have a vision of user-configuring the driver with a pair of nasty 46-char
> strings which represent each P8/P9 header and what you want each pin in that
> header to be:
The way this works in Hostmot2 is that each pin defaults to input(?) and th
Hi Ian,
great start, almost there!
Am 05.05.2013 um 10:12 schrieb Ian McMahon :
> I started a repository of test code here:
>
> https://bitbucket.org/imcmahon/beagleboneblack-gpio_driver
>
> The complexity that I see in this is that, from a user's point of view, you
> have pins on expansion
I started a repository of test code here:
https://bitbucket.org/imcmahon/beagleboneblack-gpio_driver
The complexity that I see in this is that, from a user's point of view, you
have pins on expansion headers, but from the system's point of view, there are
GPIO ports with pins inside them, and c
19 matches
Mail list logo
