<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.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/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Understanding the nRF54H20DK DeviceTree for multi-core</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124644/understanding-the-nrf54h20dk-devicetree-for-multi-core</link><description>My understanding from the documentation is that: 
 - The application core (app) can use any pins/peripherals 
 - The radio core (rad) can use any pins/peripherals 
 - The PPR (ppr) core can use any pins/peripherals that are low-speed (16MHz) 
 - The FLPR</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 29 Sep 2025 12:44:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124644/understanding-the-nrf54h20dk-devicetree-for-multi-core" /><item><title>RE: Understanding the nRF54H20DK DeviceTree for multi-core</title><link>https://devzone.nordicsemi.com/thread/550024?ContentTypeID=1</link><pubDate>Mon, 29 Sep 2025 12:44:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f34be9e9-920f-4f81-9bc3-69946b22a51b</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Only the domain that have the peripheral defined in the devicetree can use the peripheral yes. By default everything might be setup to be used by the appcore, so if you want other domains or cores to use a specific peripheral then you need to add overlay files that ensure the peripheral is allocated to the domain you want to use the peripheral yes. One thing to be aware is the following text in the OPS that apply to the flpr and ppr cores:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1759149696285v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;So I would say it&amp;#39;s like this:&lt;/p&gt;
&lt;p&gt;If you search through the ncs repositories for instance for&amp;nbsp;status = &amp;quot;okay&amp;quot; in the devicetree files for the ppr or flpr cores you can find some examples:&lt;br /&gt;*h20_cpuppr*.dts*,*h20_cpuppr*.overlay, *h20_cpuflpr*.dts*,*h20_cpuflpr*.overlay&lt;/p&gt;
&lt;p&gt;Then you can find a list of examples of how to assign a peripheral to be used by the flpr and ppr core.&lt;/p&gt;
&lt;p&gt;To avoid that appcore also initiated these peripherals the appcore can use status = &amp;quot;reserved&amp;quot; for the same peripheral, for instance search for&amp;nbsp;&lt;span&gt;status = &amp;quot;reserved&amp;quot; in appcore devicetree files:&lt;br /&gt;*h20_cpuapp*.dts*,*h20_cpuapp*.overlay&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If the peripheral is used by the radio core, then the appcore should use&amp;nbsp;status = &amp;quot;disabled&amp;quot; for those peripherals the radio core use.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kenneth&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>