S130 2.0.0-7 Alpha not enabling internaly used peripherals

RE: S130 2.0.0-7 Alpha not enabling internaly used peripherals

Adrian Eggenberger — Wed, 23 Dec 2015 13:26:38 GMT

The revision 1 is not important for me as we use only revision 2 and 3. I think the question is answered at this point. Thanks.

RE: S130 2.0.0-7 Alpha not enabling internaly used peripherals

Petter Myhre — Wed, 23 Dec 2015 10:53:52 GMT

You can use the SHUTDOWN task for revision 2 and 3. For revision 1, I'm not sure, if that is of interest let me know and I'll find out. Be aware that there is a PAN for using the SHUTDOWN task with PPI on revision 2. The SHUTDOWN task resets the peripheral and it will be in the lowest power mode. It will release the need for HFCLK and because of this startup time may be longer compared to starting the timer from the stopped state. The POWER register shouldn't be used, so I guess that is why it isn't checked or used by the SoftDevice.

RE: S130 2.0.0-7 Alpha not enabling internaly used peripherals

Adrian Eggenberger — Tue, 22 Dec 2015 08:22:55 GMT

You are right, the POWER register is not in the reference manual. So I'll remove the code to access the power register. The SHUTDOWN task is documented for the revision 3 chips, but in the reference manual 2.1 for the revision 2 chips it isn't. Can the SHUTDOWN-task be used on all chip revisions? What does the SHUTDOWN task exactly do? The power (read from the undocumented register) is still set to 1 after the SHUTDOWN task.

In my opinion the softdevice should anyway ensure that the peripherals it uses are powered when the softdevice gets activated (as it did in earlier versions). Especially since the POWER register is in the header file since very long time.

RE: S130 2.0.0-7 Alpha not enabling internaly used peripherals

Terje — Mon, 21 Dec 2015 15:02:44 GMT

The POWER register of NRF_TIMER0 is not documented and should not be written to by the application. I believe it's appearance in the header file is a mistake.

I guess you can use the SHUTDOWN task if you don't intend to use the timer yourself.

RE: S130 2.0.0-7 Alpha not enabling internaly used peripherals

Adrian Eggenberger — Mon, 21 Dec 2015 14:48:47 GMT

I forgot to mention, that I never tried the previous S130 v2 alpha release.

RE: S130 2.0.0-7 Alpha not enabling internaly used peripherals

Adrian Eggenberger — Mon, 21 Dec 2015 14:14:04 GMT

Our platform didn't change in this point since a long time. It was working with S130 v1, S110 v8 and some earlier as well. I assume the responsible code was accidently removed when nRF52 and nRF51 code were merged together. The nRF52 don't needs this activation as it handles peripheral power automatically.

RE: S130 2.0.0-7 Alpha not enabling internaly used peripherals

Petter Myhre — Mon, 21 Dec 2015 14:03:03 GMT

I have been able to reproduce this. Very strange. We will look into it. Can I ask you what SoftDevice version you updated from? If I have understood you correctly this has worked fine with a previous release?

RE: S130 2.0.0-7 Alpha not enabling internaly used peripherals

Adrian Eggenberger — Sat, 19 Dec 2015 15:56:25 GMT

Some more test showed that other peripherals used by the softdevice are not enabled either.