<?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>Self-repairing processor</title><link>/technologies/embedded/b/blog/posts/self-repairing-processor</link><description>CRISP has developed a multi-core processor that will test and repair itself, sort of. There is an on-board resource manager that will test to see if a core is malfunctioning, and if so, send the tasks to a functioning core. The idea is to creat...</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Self-repairing processor</title><link>https://community.element14.com/technologies/embedded/b/blog/posts/self-repairing-processor</link><pubDate>Sun, 27 Mar 2011 09:10:34 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:a5f5f18e-6255-49b9-9135-fc0111ed51f6</guid><dc:creator>Former Member</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;I think that fault-tolerant&amp;nbsp; better describes this solution then self-repairing , because from what I understand&lt;/p&gt;&lt;p&gt;it cannot repair corrupted parts only reallocate tasks from them to other cores.&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=12271&amp;AppID=7&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Self-repairing processor</title><link>https://community.element14.com/technologies/embedded/b/blog/posts/self-repairing-processor</link><pubDate>Thu, 24 Mar 2011 23:45:19 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:a5f5f18e-6255-49b9-9135-fc0111ed51f6</guid><dc:creator>DAB</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;There was a lot of work done on this subject by TRW during the 1990&amp;#39;s for integrated avionics.&amp;nbsp; They approached the problem by using one processor to come up as the master, but each processor in turn would have a timed delay to see if the a master had asserted control.&amp;nbsp; If not, then the next processor that timed out would assume master control and allocate the processors to tasks as needed.&amp;nbsp; Based on the block diagram, a similar approach would probably work here.&lt;/p&gt;&lt;p&gt;Thanks,&lt;/p&gt;&lt;p&gt;DAB&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=12271&amp;AppID=7&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>