<?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>Resets from unknown reason</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/114984/resets-from-unknown-reason</link><description>I have used the nRF52832 on a few dozen projects, usually at 3.3V etc. On this project I have it at 1.8V, which may be related, but spec is 1.7V min, and the 1.8V supply is solid. Even assured by adding 1F cap across Vcc, and checked on a scope - no glitches</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 25 Sep 2024 01:17:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/114984/resets-from-unknown-reason" /><item><title>RE: Resets from unknown reason</title><link>https://devzone.nordicsemi.com/thread/503648?ContentTypeID=1</link><pubDate>Wed, 25 Sep 2024 01:17:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81432215-43f0-4c69-b992-616c0ff79ad0</guid><dc:creator>SteveHx</dc:creator><description>&lt;p&gt;Thank you for the very quick response. The PWM data is definitely in RAM, being updated fairly often. I&amp;#39;m guessing it must also be 32-bit aligned, so that will be my next line of attack.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Resets from unknown reason</title><link>https://devzone.nordicsemi.com/thread/503645?ContentTypeID=1</link><pubDate>Tue, 24 Sep 2024 23:57:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b025a84-17e8-4c36-a095-089e94fc99a9</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;Unofficial, but in case a quick response helps: the memory location may be incompatible which can cause a CPU lock-up:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;static nrf_pwm_values_individual_t PWM_DigitTable[] = {0, 1, 2, 3};
   // This works:
   pNRF_PWM-&amp;gt;SEQ[0].PTR = (uint32_t)PWM_DigitTable;

static const nrf_pwm_values_individual_t PWM_DigitTable[] = {0, 1, 2, 3};
   // This generates a hard fault or cpu lockup:
   pNRF_PWM-&amp;gt;SEQ[0].PTR = (uint32_t)PWM_DigitTable;
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;PWM data must&amp;nbsp;reside in RAM not FLASH.&lt;/p&gt;
&lt;p&gt;The &amp;quot;soft reset&amp;quot; is a software reset, perhaps caused by the PWM error but also issued, for example, when setting modes in &lt;em&gt;SystemInit()&lt;/em&gt;:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;// Generate a soft reset
NVIC_SystemReset();&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>