<?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>Using an unbonded pin in the device tree</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126241/using-an-unbonded-pin-in-the-device-tree</link><description>Background: 
 My project is using the nrf54L15 with the 48 pin package. I&amp;#39;m using vscode with v3.2.0. The QFN48 package has the following pins bonded from the silicon to the exterior of the package: 
 P0.00 - P0.04 
 P1.00 - P1.14 
 P2.00 - P2.10 
 I</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 06 Jan 2026 01:19:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126241/using-an-unbonded-pin-in-the-device-tree" /><item><title>RE: Using an unbonded pin in the device tree</title><link>https://devzone.nordicsemi.com/thread/557969?ContentTypeID=1</link><pubDate>Tue, 06 Jan 2026 01:19:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15a0f359-f911-481d-acf3-fb33a0aad8d7</guid><dc:creator>pixelstand</dc:creator><description>&lt;p&gt;Thank you, Kenneth-&lt;/p&gt;
&lt;p&gt;I will assume that the pins are not used for any internal purpose.&amp;nbsp; As long as i can select P1.15 and P1.16 in the device tree, i will use these as dummy connections in the above specified manner.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I did manage to free up 2 other pins in my solution as a backup plan. I will start out using P1.15 and P1.16 as described above for our EVT run and switch to the freed pins if needed.&lt;/p&gt;
&lt;p&gt;-Peter&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using an unbonded pin in the device tree</title><link>https://devzone.nordicsemi.com/thread/557654?ContentTypeID=1</link><pubDate>Mon, 29 Dec 2025 11:01:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc8a1a9a-2e2e-4b03-95d8-adfe576308d8</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;If you configure a pin out of physical range, &lt;span&gt;PSEL&lt;/span&gt; points to a non‑existing pad. It’s treated as a legal configuration that map to “no effective pin”. There’s no hardware check on this violation. Validation is only done on the &lt;span&gt;SW&lt;/span&gt; side such as SDK pinmaps, devicetre..&amp;nbsp;Basically, no direct risk of damaging the chip just from selecting a non‑existing pad via PSEL.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using an unbonded pin in the device tree</title><link>https://devzone.nordicsemi.com/thread/557501?ContentTypeID=1</link><pubDate>Mon, 22 Dec 2025 08:33:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c4fd84b5-2f51-4701-84b6-5879fe9e7315</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;A very interesting observation, I will need to ask internally, due to many key personnel are on holiday next two week, we may need to wait until the start of January before we will get a reply back.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>