Param Error code in DSPS device code

Hi asalhuv,

I suppose that在执行更改时发生此事件advertising string.广告字符串经过有效性切ck when its time to be transmitted over the air, perhaps the string that you are feeding to the 580 isn't a valid one (a strange flag or something like that) that would cause your device not to advertise. Or perhaps you are issuing and advertising command without canceling the previous one.

Thanks MT_dialog

Hi asalhuv,

是的，在无效的数据字符串中，您应该得到一个gap_err_adv_data_invalid。是的，首先取消广告过程，然后获取Gap_err_Canceled消息。

Thanks MT_dialog

Hi asalhuv,

You mean what is the message that the kernel sends when the advertising starts ? After you send the GAPM_START_ADVERTISE_CMD you dont get any message from the kernel, the operation is going to continue (unless is a directed advertising) until you stop advertising (response with a GAPM_CMP_EVT) or you receive a connection request (GAPC_CONNECTION_rEQ_IND). Please have a look at the RW_BLE_GAP_IS.pdf for more information.

Thansk MT_dialog

Hi asalhuv,

更改广告字符串的程序是正确的：

1) Start advertise - issue a GAPM_START_ADVERTISE_CMD and continue advertising until you decide to stop

2）停止宣传 - 发出GAPM_CANCEL_CMD

3）接收广告已停止的GAPM_CMP_EVT

4) Change the advertising string and start advertising once more.

我想你在取消广告时得到GapM_CMP_EVT_Handler（），而不是Gap_err_Canceled，你得到了Gap_err_command_disallow。尝试连接智能代码段工具并检查您的设备是否肯定是在重新启动广告不起作用时肯定的（没有RX，TX活动），您可以在发生此事件时检查设备的状态。我试图修改DSP项目以获得GAP_ERR_COMMAND_DISALLED，当我连接到设备时，我似乎正在收到此错误，我尝试开始通告，但一旦我断开连接，设备就可以再次通告。

Thanks MT_dialog

Hi asalhuv,

Considering your first post i thought that your problem was that you were getting GAP_ERR_COMMAND_DISALLOWED when you trying to re-advertise instead of GAPM_CANCEL_CMD and your device just stoppped advertising. You can use the arch_last_rwble_evt_get() in order to get the last BLE event that your device went through. Please check the beacon reference design in the app_asynch_trm() function in the app_sleep.h file. It uses this function to count the advertising events.

Thanks MT_dialog

Hi asalhuv,

The points that you mention shouldn't affect the advertising procedure of the 580, it shouldn't just stop advertising. Can you please issue advertise stop, advertise start and modify the string by using a timer and not send a command through the external MCU in order to isolate the problem. Perhaps the MCU affects somehow your system and causes to hault BLE activity somehow. Also if you check if there is BLE activity by tracking the BLE_EVT_END as the beacon snippet does and when there is no activity to issue a start advertise command, is the command executed or you have to reset the stack in order for your device to start advertise?

Thanks MT_dialog

Hi asalhuv,

When the advertising occurs the function should return the states in the following order TX/RX/TX/RX/TX/RX/BLE_END_EVT (this is the cycle of an advertising event - it will return the other states as well since its awakening but you are not interested in that, CSNT_EVT and SLP etc) so every successfull advertising event should end with BLE_END_EVT. In my previous post i mentioned that you can track the full cycle of the advertising procedure by keeping the last and the current BLE event. If the state of your device doens't change to the above states and doesn't complete the above cycle you will be able to know that your device isn't advertising. By tracking only TX is only advertising in one channel and not a full advertise operation, you can track that as well if you want to.

Thanks MT_dialog

Hi asalhuv,

When you say you dont use an external oscillator you mean, you dont use any external oscilator, not even the XTAL16 ? The XTAL16 is mandatory for the 580 as the datasheet indicates you can omit only the XTAL32 external oscillator when you are in buck mode, in boost mode the XTAL32 is mandatory as well. Sorry for not noticing your indication in post 11 earlier.

Thanks MT_dialog