Access IoT dongle sensor data while in advertising mode

Hi MT_Dialog,

We've set up our interrupt that gets triggered when the dongle moves. This part works. Instead of executing the default operation of user_adv_start, we want to run another similar but different function.

The reason is that we set the user_adv_start function to start advertising with a flag of 0x00 which gets called on program initialization since "not moved" should be our initial state.

However, the interrupt signifies that motion has occurred and we want to start advertising but with a flag of 0x01. We created a separate function called restart_adv and called this from within our interrupt handler as seen below. However, even though this function is getting called (we verified this in the debugger), the dongle restarts advertising with 0x00 even though we are passing in 0x01 as an argument to our start advertising function.

The relevant code is included below.

谢谢，
杰里米

// in user_platform.c
void wkup_intr_non_connected_cb( void ) // this function successfully gets called when the dongle moves
{
restart_adv();
}

// in user_wrbl.c
void user_adv_start( void ) { // this is what is called on program initialization, advertise with 0x00
user_easy_gap_undirected_advertise_start( FAST_ADV_INTERVAL, 0x00);
}

void restart_adv( void ) { // this is what we want to be called from the interrupt handler, should advertise with 0x01
user_easy_gap_undirected_advertise_start( FAST_ADV_INTERVAL, 0x01);
}

//启动广告的功能，我们为我们要宣传的用户数据添加了额外参数
static void user_easy_gap_undirected_advertise_start(uint16_t adv_intv, uint8_t user_data)
{
struct gapm_start_advertise_cmd* cmd;
timer_hnd app_adv_data_update_timer_used = app_easy_timer(1000, adv_data_update_timer_cb);

cmd = app_easy_gap_undirected_advertise_get_active();
cmd->intv_max = adv_intv;
cmd->intv_min = adv_intv;
user_add_adv_info(cmd->info.host.scan_rsp_data, 10 );
user_add_accel_info(cmd->info.host.scan_rsp_data, user_data); // modifies the byte we are using for advertising data

app_easy_gap_undirected_advertise_start();

// We are now connectable
ke_state_set(TASK_APP, APP_CONNECTABLE);
}

uint8_t user_add_accel_info( uint8_t *padv, uint8_t user_data){
padv[7] = user_data;
return 0;
}

Hi MT_Dialog,

We figured out what our problem is. Thanks!

杰里米