Question about SoftDevice behavior at first startup

RE: Question about SoftDevice behavior at first startup

kohiro — Wed, 19 Jul 2023 01:21:19 GMT

Thanks for the reply.

I found a simple bug in the application.

Thanks for the advice.

RE: Question about SoftDevice behavior at first startup

Vidar Berg — Mon, 17 Jul 2023 09:42:05 GMT

Using the "nrfjprog --readregs" command may help you figure out what state your device is in when it fails to establish communication with your other device. It will read out the CPU registers from a running device without resetting it.

RE: Question about SoftDevice behavior at first startup

kohiro — Mon, 17 Jul 2023 08:06:14 GMT

Thank you for sharing the documentation.

Yes, I too am beginning to think it is an application issue.

After startup, it appears to be working fine without resetting, but there may be a problem with the initialization process at startup, etc.

I would like to review the process a bit more.

Thank you very much.

RE: Question about SoftDevice behavior at first startup

Vidar Berg — Mon, 17 Jul 2023 07:16:09 GMT

Yes, the 'Master boot record and SoftDevice reset procedure' section of the Softdevice specification document explains the boot sequence. However, the issue you experience sounds more like an issue with the application. Do you have to reset the device to recover from this?

RE: Question about SoftDevice behavior at first startup

kohiro — Sun, 16 Jul 2023 23:35:15 GMT

Thank you for your reply.

I have not measured the specific time, but I assumed that the startup process is slow because it sometimes fails to communicate with external devices only at the first startup.

Is there any documentation somewhere that shows the startup process for soft devices?

Thanks.

RE: Question about SoftDevice behavior at first startup

Vidar Berg — Wed, 12 Jul 2023 10:07:15 GMT

Hello,

The startup sequence inside the Softdevice remains the same, regardless of whether it is the first boot or not. How much longer is the first boot compared to the second one?

Thanks,

Vidar