WKUPCT回调函数

我修改了回调follow, but still doesn't seem to work. Tracing with Jlink, I can see it go into the callback function, but it doesn't advertise the new UUID:

void tilt_wakeup_cb(void) { if (GetBits16(SYS_STAT_REG, PER_IS_DOWN)) { // Return GPIO functionality from external wakeup GPIO if (DEVELOPMENT_DEBUG) GPIO_reservations(); periph_init(); } if (arch_ble_ext_wakeup_get()) { arch_set_sleep_mode(ARCH_SLEEP_OFF); //disable the sleep mode arch_ble_force_wakeup(); //force the BLE to wake up arch_ble_ext_wakeup_off(); //disable the external wake up (if you have set the arch_ble_ext_wakeup_on() function before going to permanent sleep) //LED } tilt_wkup_flag = 1; user_advertise_operation(); wkupct_enable_irq(0x003F0000,0x003F0000,1,0); // Enable interrupt for P2_0 to P2_5 }

好的，所以不应该有任何problem in calling user_advertise_operation(); inside the callback right? The radio and everything should be on and it should advertise when set up the way I have it?

只是确保我没有违反一些规则，从GPIO中断唤醒后我们无法宣传。

谢谢，

当没有发生GPIO中断并且设备在定时间隔上唤醒时，在手机上的灯架扫描应用上看到所有广告活动。

当GPIO中断确实发生时，踩到代码时，似乎代码会做它应该是什么，但我从未在扫描仪应用中看到正确的值......

Somehow I don't think the data is being advertised in this scenario. The app_easy_gap_non_connectable_advertise_start() is used for both scenario. For the GPIO interrupt case I changed the cmd->intv_min and cmd->intv_max to 0. or leave those two blank, no luck either way.

Here is the code.

发现有点信息。
我删除了对user_advertise_operation（）的调用;在tilt_wakeup_cb（）中，现在看到扫描仪应用程序中的预期更改。问题是它稍后最终记录了大约5-10个广告间隔。（我在5秒钟内设置广告间隔，我在GPIO被拉低后在大约55秒内收到更改的数据包）。

这似乎表明，在将实际事件放在队列中之前需要刷新的广告数据的缓冲区？这似乎是对吗？

You mentioned I should stop the advertising, update the advertising string and then restart the advertising. Am I interpreting this correctly if I do the following?

app_easy_gap_advertise_stop（）;
user_advertise_operation（）;

The code for user_advertise_operation(); is the default Dialog one:

void user_advertise_operation（void）
{
struct gapm_start_advertise_cmd * cmd;
current_advertising_string = next_advertising_string;
current_advertising_mode = next_advertising_mode;
if（current_advertising_mode == non_connectable_mode）
{
//获取指向BLE数据包的指针
cmd = app_easy_gap_non_connectable_advertise_get_active（）;

user_adv_restarted = true;
cmd-> info.host.adv_data_len = user_load_beacon_config（cmd）;

//开始为非可连接外设进行广告。
if（app_connected == ke_state_get（task_app））
{
//不要在连接状态广告不可连接的广告
}
别的
{
if（user_flash_beacon_config_loaded）
{
cmd->intv_min = MS_TO_BLESLOTS(user_beacon_config.adv_int);
cmd->intv_max = MS_TO_BLESLOTS(user_beacon_config.adv_int);
}

app_easy_gap_non_connectable_advertise_start();

}
}
否则if（current_advertising_mode ==未向连接_mode）
{
//获取指向BLE数据包的指针
cmd = app_easy_gap_undirected_advertise_get_active();

user_adv_restarted = true;
cmd-> info.host.adv_data_len = user_load_beacon_config（cmd）;

if (current_advertising_string == SUOTA_ADVERTISING_STRING)
{
update_advertising_data（user_advertise_suota，user_advertise_suota_len）;
user_update_adv_string（cmd，（void *）dynamic_adv_string，suota_advertising_string，user_advertise_suota_len）;
}
//启动广告以获得未确定的外设。
app_easy_gap_undircated_advertise_start（）;
}

}

关于我想做的事情的背景，请告诉我是否有可能。

当GPIO2_0变为低电平时，我想用uuid结尾发出一个广告，以0.手机应用程序将记录它收到广告的时间。当另一个GPIO变低时，让我们说GPIO2_1，我想用uuid结尾发出一个广告。手机将记录它收到的时间并计算两个广告之间的时间差。时间差对我正在尝试与数据进行操作至关重要。这是实现这一目标的可靠方法吗？或者是否有一些类型的限制，不允许我完成这一目标？

Thanks again for your continued support.