Hello support,

I am considering using external interrupt input of DA 14585 to asynchronously return (from exteded sleep) using external MPU.
I am referring to the document (Training_04_Sleep mode configurations and power measurement_0.pdf). (Page 9)

SDK :6.0.8.509.
The external MPU and DA 14585 are connected using SPI I/F.

I have two questions.

Q1. During exteded sleep
Behavior is different between Keil-uVision debugging operation and actual operation.
First I set to "exteded sleep" when DA 14585 is not communicating, and set action from restore DA 14585 from Sleep state by using port interrupt.

I would like to communicate with SPI immediately after returning. ,
In uVision and J-LINK debugging environment, it works without problems.
Next, if I write this program to the external SPI flash and let it operate standalone, it will stop working. (It will not return.)
Looking at the current value, it looks like DA14585 has recovered. However, SPI communication with external microcomputer seems not to be done.
Are there any differences in the operation between the debugging environment (Keil - uVision and J - LINK) and the real environment (using flash)?
(For example, in the debugging environment, the power supply of the RAM is not actually turned off.)

(2) Bluetooth communication in progress
If I do a return operation using port interrupts in the same way during Bluetooth communication,
The function lld_sleep_compensate_func (in rwble.c) is called,
Then it stops with ASSERT_WARNING (0) on the last line.
This phenomenon occurs in both the debugging environment (uVision and J-LINK) and the real environment (using flash).
Is it that the period of sleep has been too short? Or do you have something to think about?
Could you please advise me for workaround.

In addition to the above information, if necessary items, please request to us.

regards,

Jun-ichi