UART醒来后不起作用

嗨对话框，

感谢您的评论。
至于APP_ADV_DATA_UPDATE_TO,我改为1毫秒and my program is to UART receive interrupt after wake-up.
我通过示波器测量了定时，并且我检查了UART接收的定时在唤醒后至少超过10msec发生。
但是没有检测到UART接收中断，我想象UART接收中断本身将工作，因为它在几秒钟后被检测到。
So I'd know how many seconds is neede to enable UART receive interrupt.
当然，UART接收中断并在我的程序中发送正常工作。
So how should I do to enable UART receive interrupt after wake-up?

Thanks,
Diogenes.

嗨对话框，

Could I add some information about the current problem.
Firstly as for UART receive interrupt doesn't normally after weke-up and my program sometimes jumps to L.369 in rwble.c (ASSERT_WARNING(0);).

if（（development_debug）&&（use_power_optimizations））
{
slp_period_retated = slp_period;
//如果此断言命中，则LP ISR持续时间长于时间
//已通过LP_ISR_TIME_XTAL32_CYCLES和LP_ISR_TIME_USEC保留。
if（sleep_lp_cycles &&（sleep_lp_cycles assert_warning（0）;// l.369
}

But Receive interrupt itself wasn't caught and I must judge it's not handler's problem.
Then I doubted wake-up delay time at L.400 in arch_system.c ().

else // USE_POWER_OPTIMIZATIONS
{
delay = minime_sleep_duration;

// if XTAL_TRIMMING_TIME_USEC changes (i.e. gets larger) then this
// will make sure that the user gets notified to increase "delay" by 1 or more
// slots so there's enough time for XTAL to settle
＃if（（3125 +（minimue_sleep_duration + 625））<（lp_isr_time_usec + 1100））//1.1ms max上电时间// l.395
＃错误“最小睡眠持续时间太小，对于使用的16MHz水晶......”
＃ 万一
}
rwip_wakeup_delay_set(delay); // L.400

但考虑到L.395的约束，我理解将最终_sleep_duration更改为1slot。
然后我认为这是睡眠模式和我重写arch_set_deep_sleep（）的问题;to arch_set_extendend_sleep（）;在void user_app_adv_start（void）中，但结果是相同的。

Anyway now I'm at loss.
请告诉我有用的信息来解决它。

Thanks,
Diogenes.

嗨对话框，

我必须更多地添加有关当前情况的更多信息。
I noticed on debugging that mu program doesn't enter into if(arch_ble_ext_wakeup_get()) clause though I set EXT_SLEEP in user_config.h, user_app_adv_start() and user_app_connection() like folllowings.

// const static sleep_state_t app_default_sleep_mode = arch_deep_sleep_on;
const static sleep_state_t app_default_sleep_mode = arch_ext_sleep_on;

// ARCH_SET_DEEP_SLEEP（）;
ARCH_SET_EXTEDDE_SLEEP（）;

所以我评论了（Arch_ble_ext_wakeup_get（）），但没有发生UART接收中断。

// if(arch_ble_ext_wakeup_get())
{
ARCH_SET_SLEEP_MODE（app_default_sleep_mode）;
arch_ble_force_wakeup();
ARCH_BLE_EXT_WAKEUP_OFF（）;
app_easy_wakeup();
}

And next I inserted forcibly arch_force_active_mode() just after arch_ble_force_wakeup().
然后UART接收中断发生，但我怀疑如果程序真的进入睡眠模式。
At least on debug, the program enters into arch_goto_sleep(sleep_mode).
Could I think Extended Sleep is really entered even I inserted arch_force_active_mode() just after arch_ble_force_wakeup()?
Please tell me more information.

Thanks,
Diogenes.

嗨对话框，

Thank you for your reply.

>您想通过从UART接收数据来唤醒DA14580吗？

正如我已经解释了两倍的“否”，我只需要在Wakeup Int唤醒后接收中断。

> If you configure the APP_ADV_DATA_UPDATE_TO as 1msec

I think it's impossible to configure the APP_ADV_DATA_UPDATE_TO as 1msec, since the minimum quantum of APP_ADV_DATA_UPDATE_TO is 10msec.
我使用app_adv_data_update_to运行1（10msec间隔）和1000（10sec），但结果是相同的。
With both value UART receive interrupt after wake-up works normally.
我可以询问您是否有关它，将App_add_data_update_to配置为1（10磁形间隔）太短？

And I ask again about the question I wrote in previous post.
I repeat that I commented out if(arch_ble_ext_wakeup_get()) and inserted arch_force_active_mode() just after arch_ble_force_wakeup().
Could I think Extended Sleep is really entered even I inserted arch_force_active_mode() just after arch_ble_force_wakeup()?

// if(arch_ble_ext_wakeup_get())
{
ARCH_SET_SLEEP_MODE（app_default_sleep_mode）;
arch_ble_force_wakeup();
ARCH_BLE_EXT_WAKEUP_OFF（）;
app_easy_wakeup();
}

这只是我想在上一篇文章中提出的问题。

Thanks,
Diogenes.