will wkupct callback function interrupt user_custs1_xxx_wr_ind_handler

Hi, PM_Dialog;

Thanks for your quick response.

1.我确实使用SPI Flash驱动程序访问内部闪存。当写入控制点特性时，我可以将一些数据保存到闪存。这项工作很好。我的代码看起来像：

void user_custs1_ctrl_wr_ind_handler（...）{

GPIO_ConfigurePin(FLASH_CS_PORT, FLASH_CS_PIN, OUTPUT, PID_SPI_EN, true);
gpio_configurepin（flash_clk_port，flash_clk_pin，输出，pid_spi_clk，false）;
gpio_configurepin（flash_do_port，flash_do_pin，输出，pid_spi_do，false）;
gpio_configurepin（flash_di_port，flash_di_pin，输入，pid_spi_di，false）;

spi_init（＆spi_flash_cs_pad，spi_mode_8bit，spi_rool_master，spi_clk_dle_pol_low，spi_pha_mode_0，spi_mint_disable，spi_xtal_div_8）;

spi_flash_init(SPI_FLASH_SIZE, SPI_FLASH_PAGE);

// point A

spi_flash_block_erase（configaddress，sector_erase）;

spi_flash_write_data (&configData[0], ConfigAddress, sizeof(configData));

...

}

2.当它的缓冲区已满时，我有一个G-Sensor，它会产生脉冲（DA14583的外部中断）。发生此事件时，我使用WKUP回调函数从G-Sensor的缓冲区VIS界面读出所有数据。这也很好。但是，我注意到错误发生在此WKUP回调函数中的错误。似乎我在WKUP回调函数时做了太多的作品，导致某种超时！这就是为什么我正在使用app_easy_timer（）来安排WKUP回调函数的一枪App_easy_timer_cb（）。通过这种方式，WKUP回调函数只是进行计时器计划工作，因此它不再导致timerout了。并且真实的工作留给了App_easy_timer_cb（）函数。这个策略为我工作，但如果不是批判，请纠正我！

So, the app_easy_timer_cb() look like:

void app_easy_timer_cb（void）{

spi_init（＆spi_gsensor_cs_pad，spi_mode_8bit，spi_rool_master，spi_clk_idle_pol_low，spi_pha_mode_0，spi_mint_disable，spi_xtal_div_8）;

... // read G-Sensor data from SPI interface

}

3. The problem come from both Flash and G-Sensor are using SPI interface, and DA14583 had just one spi controller! when I access Flash, I must make sure

GPIO_ConfigurePin(FLASH_CS_PORT, FLASH_CS_PIN, OUTPUT, PID_SPI_EN, true);
gpio_configurepin（flash_clk_port，flash_clk_pin，输出，pid_spi_clk，false）;
gpio_configurepin（flash_do_port，flash_do_pin，输出，pid_spi_do，false）;
gpio_configurepin（flash_di_port，flash_di_pin，输入，pid_spi_di，false）;

spi_init（＆spi_flash_cs_pad，spi_mode_8bit，spi_rool_master，spi_clk_dle_pol_low，spi_pha_mode_0，spi_mint_disable，spi_xtal_div_8）;

spi_flash_init(SPI_FLASH_SIZE, SPI_FLASH_PAGE);

had executed before below fucntion was called.

spi_flash_write_data (&configData[0], ConfigAddress, sizeof(configData));

以同样的方式，当我读取G-Sensor的数据时，我必须确保

GPIO_ConfigurePin(GSensor_CS_PORT, GSensor_CS_PIN, OUTPUT, PID_SPI_EN, true);
GPIO_ConfigurePin(GSensor_CLK_PORT, GSensor_CLK_PIN, OUTPUT, PID_SPI_CLK, false);
gpio_configurepin（gsensor_do_port，gsensor_do_pin，输出，pid_spi_do，false）;
GPIO_ConfigurePin(GSensor_DI_PORT, GSensor_DI_PIN, INPUT, PID_SPI_DI, false);

spi_init（＆spi_gsensor_cs_pad，spi_mode_8bit，spi_rool_master，spi_clk_idle_pol_low，spi_pha_mode_0，spi_mint_disable，spi_xtal_div_8）;

had executed.

Since G-Sensor alway generate data continuously, it will causing WKUP callback to be called periodically. (In my case, app_easy_timer_cb() will also be called periodically)

What if when the Control Point characteristic is written, and the G-Sensor's buffer full at the same time?

I want to know if the following will happen?

------------------------------------------------------------------

The user_custs1_ctrl_wr_ind_handler() execute first.

Inside this handler function,

GPIO_ConfigurePin(...) was call, then spi_init() was call next, then spi_flash_init() was call.

Then before spi_flash_block_erase(...) function was call (point A), The app_easy_timer_cb() was trigger.

因此，user_custs1_ctrl_wr_ind_handler（）停止（暂停）在Point A中执行。并开始Expection App_easy_timer_cb（）函数。

After app_easy_timer_cb() execute, user_custs1_ctrl_wr_ind_handler() resume execution from point A.

-------------------------------------------------------------------

If this happen, it will make flash write fail.

Or the SDK will execute app_easy_timer_cb() after user_custs1_ctrl_wr_ind_handler() had finished execution?

谢谢。

Hi, PM_Dialog;

很高兴知道你正在研究我的问题。我期待着你的回复。

Thanks a lot.