睡眠后使用wkup中断唤醒，但是导致类似 reset 的结果，请问如何判断 | Dialog Semiconductor customer support

3 posts / 0 new

Last post

Tue, 2016-08-23 07:58

sprhawk

Offline

Last seen:3 years 1 month ago

加入ed:2016-03-03 17:25

睡眠后使用wkup中断唤醒，但是导致类似 reset 的结果，请问如何判断

SDK5。0。3

开启 extended_sleep， #undef DEVELOPOMENT_DEBUG，
睡眠后关闭蓝牙功能arch_ble_ext_wakeup_on()
使用外部中断触发唤醒，会发生类似重置的操作，原因是我保存的变量

user_app_on_db_init_complete()又被执行了,而我保存的变量

static uint8_t var[LEN] __attribute__((section("retention_mem_area0"),zero_init));

被重置了

因为开启睡眠之后带了 JLink 会卡在一个 DBG_IS_UP 的 while 循环，我想知道这可能是什么原因导致，有什么方法可以来判断？

Device:

DA14583

Tue, 2016-08-23 10:59

Jelphi

Offline

Last seen:5 months 3 weeks ago

加入ed:2015-09-10 12:07

Deep sleep or extended sleep

Deep sleep or extended sleep conflicts with the J-Link debugger. You have to stop the debugger for the device to start advertising. You can also disable (undefine) both sleep modes in the da14580_config.h file of each project, this will allow you to also use the debugger."

Tue, 2016-08-23 13:12

(Reply to #2) #3

sprhawk

Offline

Last seen:3 years 1 month ago

加入ed:2016-03-03 17:25

Extended Sleep (I'm using

Extended Sleep (I'm using DA14583)

I know it, I didn't start with JLink, I start with Booter in the SmartSnippets to program the program into the device, and Power Profiler.

I think it is supposed to not stop running the program. I want to test the current during the sleep mode, so I don't disable the sleep mode.

But it is still running improperly