https://devzone.nordicsemi.com/f/nordic-q-a/25565/timer2-hardfaultHi, I&#39;m developing an application for the nRF52832 using mbed and the S132 SoftDevice. Since it appears that the SoftDevice requires exclusive use of Timer0 and mbed uses Timer1 to run the RTOS, I am trying to use Timer2 to more precisely drive the sampleen-USTelligent Community 13Thu, 05 Oct 2017 11:11:10 GMThttps://devzone.nordicsemi.com/thread/100784?ContentTypeID=1Thu, 05 Oct 2017 11:11:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d68f45e7-f6db-4a42-92c1-31a97a0a1e6aJ&#248;rgen Holmefjord<p>Hi,</p> <p>The weak handlers defined in the startup files are dummy handlers. You need to implement the handler and register it using <code>NVIC_SetVector()</code>, like show in the <a href="https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_NORDIC/TARGET_NRF5/serial_api.c#L260">serial_api.c implementation</a>.</p> <p>How are you using the TIMER peripheral? And how did you setup SAADC?</p> <p>Best regards,</p> <p>Jørgen</p><div style="clear:both;"></div>