OTA DFU hardware resources

RE: OTA DFU hardware resources

JohnBrown — Wed, 14 Oct 2015 07:16:26 GMT

Thanks, Stefan. I had looked at the soft device spec., but wasn't sure if the DFU code used any extra hardware resources. I tried it anyway, and it seems to work fine.

RE: OTA DFU hardware resources

Stefan Birnir Sverrisson — Tue, 13 Oct 2015 21:31:47 GMT

Hi JohnBrown

I dont think the bootloader uses any PPI channels or TIMER peripherals. There are only limitations of the softdevice that apply. The softdevice blocks TIMER0 but the other timers should be available. Take a look in the softdevice specification (SDS) for the softdevice you are using to find out what PPI channels are occupied by the softdevice. You should anyhow be free to use all TIMERs and PPI channels before enabling the softdevice.

RE: OTA DFU hardware resources

JohnBrown — Tue, 13 Oct 2015 13:14:48 GMT

Because I'm doing this prior to starting the soft device. Anyway, as I said above, I found the problem.

RE: OTA DFU hardware resources

Wojtek — Tue, 13 Oct 2015 12:36:08 GMT

Why don't you just use app_timer which is implemented on RTC? It is perfect for longer (i use it to generate events from 3ms up to few minutes) delays...

RE: OTA DFU hardware resources

JohnBrown — Tue, 13 Oct 2015 07:38:25 GMT

OK, answering part 1 of my question, I hadn't realised that only timer0 has the 32 bit capability.

Still like to know if I can use a timer and PPI to flash the LED for DFU, though.