Attempting to setup Counter top value causes firmware to reboothttps://devzone.nordicsemi.com/f/nordic-q-a/112121/attempting-to-setup-counter-top-value-causes-firmware-to-rebootI&#39;m running NCSv2.6.0 on some custom hardware, with an nRF52832 IC fitted. I&#39;m trying to trigger an ADC measurement every ~ 300usec using a Counter, so need to set the Counter top value to trigger the callback function at the appropriate time. I haveen-USTelligent Community 13Fri, 14 Jun 2024 06:36:11 GMTRE: Attempting to setup Counter top value causes firmware to reboothttps://devzone.nordicsemi.com/thread/488794?ContentTypeID=1Fri, 14 Jun 2024 06:36:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bea43258-c19e-47dd-90ab-3d3b1d4bc5e2Mike Austin (LPI)<p>Hi Vidar,</p> <p>THANKYOU!!!!!&nbsp; Wow, I have been struggling with this issue on and off for weeks.&nbsp; Changing:</p> <div> <div><span>#define</span><span> </span><span>TIMER</span><span> </span><span>DT_NODELABEL</span><span>(timer0)</span></div> <div><span></span></div> <div><span>to</span></div> <div><span></span></div> <div> <div> <div><span>#define</span><span> </span><span>TIMER</span><span> </span><span>DT_NODELABEL</span><span>(timer1)</span></div> <div><span></span></div> <div><span>fixed the problem!!&nbsp; The other code, where things work, doesn&#39;t utilise BLE, hence why it wasn&#39;t an issue that presented itself.</span></div> <div><span></span></div> <div><span>I&#39;m off to celebrate with a beer (its 4.30pm here in Australia) :-)</span></div> <div><span></span></div> <div><span>Cheers/sk&aring;l,</span></div> <div><span>Mike</span></div> </div> </div> </div><div style="clear:both;"></div>RE: Attempting to setup Counter top value causes firmware to reboothttps://devzone.nordicsemi.com/thread/488793?ContentTypeID=1Fri, 14 Jun 2024 06:08:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:aa74e916-d268-489f-9e97-dfa117494d6cVidar Berg<p>Hi Mike,</p> <p><span style="font-family:inherit;">For debugging, you may try disabling the &#39;CONFIG_RESET_ON_FATAL_ERROR&#39; setting to see if the error handler is invoked. I also noticed that you are using TIMER instance 0. This instance is reserved for the Softdevice controller / MPSL and should not be used if you are using BLE. Do you experience the same issue if you switch to a different TIMER instance?</span></p> <p><span style="font-family:inherit;">Best regards,</span></p> <p>Vidar</p><div style="clear:both;"></div>