<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>BBB - Getting ACE working</title><link>/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/bbb---getting-ace-working</link><description>IntroductionThe Beaglebone Black PRU cores are great for high speed operations. The AM3359 chip on the BBB contains an ARM core and two PRU cores amongst other modules. They run as independent CPUs at 200MHz, freeing up the ARM core for continuing to</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: BBB - Getting ACE working</title><link>https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/bbb---getting-ace-working</link><pubDate>Mon, 17 Jun 2013 05:10:03 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:b4fb83a1-fb91-4ec2-9b7b-aa3535274664</guid><dc:creator>morgaine</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;I think I&amp;#39;d probably veer towards using a proper concurrent language for the host side of the PRU communications interface, such as Erlang or Google Go.&amp;nbsp; In both cases the design patterns for concurrent communication are well honed and exceedingly powerful as a result of being an integral part of the language, rather than a framework layered on top of a non-concurrent language.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I like both Erlang and Go, but I&amp;#39;ve not installed either of them on ARM yet.&amp;nbsp; It&amp;#39;s on my TO-DO list.&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=15941&amp;AppID=80&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>