> On 26 Jul 2017, at 21:03, Daren Schwenke <darenschwe...@gmail.com> wrote:
> 
> I would be happy to help with this. 
> Point me to an image I should use to get started and I'll have the physical 
> up this evening.

Thanks for helping out Daren!

> My version of cross compiling is probably not what is used anymore, so I may 
> need some help there as well.
> 
> 
> 
>> On Wed, Jul 26, 2017 at 2:45 PM, Charles Steinkuehler 
>> <char...@steinkuehler.net> wrote:
>> On 7/26/2017 11:06 AM, Robert Nelson wrote:
>> > On Wed, Jul 26, 2017 at 10:32 AM, Charles Steinkuehler
>> > <char...@steinkuehler.net> wrote:
>> >> On 7/26/2017 10:12 AM, Robert Nelson wrote:
>> >>> On Tue, Jul 25, 2017 at 8:43 PM, Daren Schwenke 
>> >>> <darenschwe...@gmail.com> wrote:
>> >>>> I can confirm the both the BBG and BBGW will boot with this image from 
>> >>>> an SD
>> >>>> card:
>> >>>> https://rcn-ee.com/rootfs/bb.org/testing/2017-02-12/machinekit/bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz
>> >>>>
>> >>>> Getting wireless to actually work is a whole other ball game which I 
>> >>>> have
>> >>>> yet to achieve, but at least the image boots now.
>> >>>
>> >>> Correct, that "3.8.x" based image will support the BBGW/BBBW but with
>> >>> wireless disabled.  To enable wireless, sadly you will need a v4.4.x+
>> >>> kernel.  While we have a xenomai based v4.4.x build, it's based on
>> >>> Xenomai 3.0.x, and not the 2.6.x based Xenomai machinekit expects..
>> >>
>> >> Machinekit can also run with the 4.x preempt_rt kernel on the 'bone,
>> >> but the PRU driver hasn't been updated for the re-arranged files in
>> >> /sysfs so it won't work "out of the box".
>> >
>> > What is it looking for in /sysfs? With the v4.4.x-rt we can enable the
>> > 3.8.13 compatible uio driver, then as long as config-pin is used, it
>> > should sync up with what it use to do with 3.8.13..
>> 
>> IIRC, several of the setup scripts are looking for the slots file to
>> verify/load an overlay, some code is looking for the ADC entries in
>> sysfs (which have moved IIRC), and the actual HAL driver for the PRU
>> may have a sysfs path or two hard-coded (I'd have to check).
>> 
>> So nothing really that complex (particularly vs. updating to Xenomai
>> 3), but a 4.x kernel won't work without a few tweaks and maybe a bit
>> of coding.
>> 
>> Anyone with a BBG/BBGW want to try getting things running with a 4.x
>> kernel?  I can provide guidance and maybe do the bit of coding if
>> someone's willing to help with the shell scripts and do testing.
>> 
>> Deemarc / Daren?
>> 
>> --
>> Charles Steinkuehler
>> char...@steinkuehler.net
>> 
>> --
>> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
>> https://github.com/machinekit
>> ---
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Machinekit" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/machinekit/RrNLUo4ASP4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> machinekit+unsubscr...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/machinekit.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to machinekit+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to