<?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>Programmatically disabling PINRESET - nRF52832, nRF5 SDK, SD112</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127021/programmatically-disabling-pinreset---nrf52832-nrf5-sdk-sd112</link><description>Hello, 
 
 In a legacy (nRF5SDK) application, we notice a parasitic&amp;#39; pin resets reported by the system (RESREASON). 
 As the device does not have an accessible reset pin, we assume that these resets are induced by some parasitic EMC noise. So we decided</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 14 Feb 2026 23:47:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127021/programmatically-disabling-pinreset---nrf52832-nrf5-sdk-sd112" /><item><title>RE: Programmatically disabling PINRESET - nRF52832, nRF5 SDK, SD112</title><link>https://devzone.nordicsemi.com/thread/561176?ContentTypeID=1</link><pubDate>Sat, 14 Feb 2026 23:47:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2af375e-562a-4ebb-b00a-9664298a1a2c</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;Not sure if this helps, but it would be usual to make the reversion of the PINRESET in the App conditional on the version of the Bootloader; in other words the main App only turns off the pin reset (which requires a reset to load the new UICR) once the new bootloader has been installed and is invoking the main App. This requires that the new main App query the version of the bootloader.&lt;/p&gt;
&lt;p&gt;Edit: I forgot to mention that it may be possible to simply enable the pull-up on pin 21 to reduce EMC susceptibility. This works (may work) as the schematic in the data sheet is incorrect; the pull-up applies to the pin regardless of what mode the pin is in.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programmatically disabling PINRESET - nRF52832, nRF5 SDK, SD112</title><link>https://devzone.nordicsemi.com/thread/561175?ContentTypeID=1</link><pubDate>Sat, 14 Feb 2026 22:14:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:22a6d209-4624-4ce0-b431-4de924dd33c3</guid><dc:creator>eyalasko</dc:creator><description>&lt;p&gt;So it appears that the problem lies in the bootloader of the older version.&lt;br /&gt;&lt;br /&gt;Since it was build with&amp;nbsp;CONFIG_GPIO_AS_PINRESET, it enables PINRESET and then transfers control to the app that tries to disable it and then reset, hence creating a boot loop.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I would appreciate a clear instruction as how to OTA update a merged Bootloader+App file.&lt;/p&gt;
&lt;p&gt;If this is not possible in one step, please guide how to do it in two steps.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I tried to rebuild the bootloader without the flag and generated a DFU zip file which I managed to DFU fine, then I&amp;#39;m trying to DFU the app, the device resets...&lt;/p&gt;
&lt;p&gt;Please advise&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>