I found the 4.14 RT kernel to be extremely sluggish.

Can you please also try the 4.4 TI RT kernel and report back if it makes
a difference for you?

If you get the 4.14 TI RT kernel working nicely please also report back,

[email protected] writes:

> Thanks Robert! I was able to start up machinekit. Now I need to track down 
> some other quirks... What is ktimersoftd and why is it constantly taking up 
> 40% of the CPU? This is on a freshly installed 4.14 image (see attached).
>
> On Thursday, December 14, 2017 at 1:33:27 PM UTC-7, Robert Nelson wrote:
>>
>> On Thu, Dec 14, 2017 at 2:22 PM, Robert Nelson <[email protected] 
>> <javascript:>> wrote: 
>> > On Thu, Dec 14, 2017 at 2:16 PM,  <[email protected] 
>> <javascript:>> wrote: 
>> >> Found this in dmesg: 
>> >> [   30.418037] pinctrl-single 44e10800.pinmux: pin PIN103 already 
>> requested 
>> >> by 48038000.mcasp; cannot claim for 4a300000.pruss 
>> >> [   30.580322] pinctrl-single 44e10800.pinmux: pin-103 (4a300000.pruss) 
>> >> status -22 
>> >> [   30.692649] pinctrl-single 44e10800.pinmux: could not request pin 
>> 103 
>> >> (PIN103) from group foo_pins  on device pinctrl-single 
>> >> 
>> >> Looks like P9.28 is used by something else. What is mcasp? 
>>
>> PS, i've just added this to the version.sh check..  On a normal boot 
>> when all overlays are correctly combined, it'll only show: 
>>
>> [    2.340306] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 
>> size 568 
>>
>>
>> https://github.com/RobertCNelson/boot-scripts/commit/66e6b465c450a03cc0060589deb163fc5577a476
>>  
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>

-- 
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 [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to