<?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>Permanantly disable Bluetooth and NFC modules</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/122716/permanantly-disable-bluetooth-and-nfc-modules</link><description>We are developing a product that will have a wireless and wired option, based on the NRF52840 
 The strategy is to release the wired option first, followed by the wireless option six months later, after FCC certification. 
 
 We need to permanently disable</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 04 Jul 2025 12:16:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/122716/permanantly-disable-bluetooth-and-nfc-modules" /><item><title>RE: Permanantly disable Bluetooth and NFC modules</title><link>https://devzone.nordicsemi.com/thread/541449?ContentTypeID=1</link><pubDate>Fri, 04 Jul 2025 12:16:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2b0962a-5b41-4673-be10-0650862aa099</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;If you use one of our DFU solutions that require signature validation, only the holder of the private key will be able to sign and distribute updates for these devices. As a result, RADIO or NFC functionality will not be enabled unless you distribute a firmware update that explicitly enables it. Will that work?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>