HI dialog
Firmware stop on GLOBAL_INT_START
how to find stop reason??
i change connection interval as below , Is connection interval effect my Firmware??
static const struct connection_param_configuration user_connection_param_conf = {
/// Connection interval minimum measured in ble double slots (1.25ms)
/// use the macro MS_TO_DOUBLESLOTS to convert from milliseconds (ms) to double slots
.intv_min = MS_TO_DOUBLESLOTS(50),
/// Connection interval maximum measured in ble double slots (1.25ms)
/// use the macro MS_TO_DOUBLESLOTS to convert from milliseconds (ms) to double slots
.intv_max = MS_TO_DOUBLESLOTS(70),
void default_app_on_get_dev_slv_pref_params(struct gap_slv_pref* slv_params)
{
slv_params - > con_intv_min = MS_TO_DOUBLESLOTS(50);
slv_params - > con_intv_max = MS_TO_DOUBLESLOTS(70);
slv_params->slave_latency = 0;
slv_params->conn_timeout = MS_TO_TIMERUNITS(1250);
}
Hi alex.jian,
Thanks for your question. Can you please indicate the SDK version and the project you are using in order to replicate your issue? Is it DA14580 or DA14585?
Does the Dialog device act as Peripheral or as a Central? According to BLE specifications, the connection interval is decided by the Master (Central). In case the device is acting as a Peripheral, what is the Central?
Additionally, is there any specific reason for using the default_app_on_get_dev_slv_pref_params(struct gap_slv_pref* slv_params). Where this function is called in your project?
Thanks, PM_Dialog
HI Dialog
i use DA14585
my project base on DA14585_DSPS_v_6.150.2 example
Dialog device is my Peripheral ,
Central is smartphone,
i want to set connection interval is 50-70ms when connect central ,so i modfiy those parameter
i don't call default_app_on_get_dev_slv_pref_params on my project
Hi alex.jian,
According to Bluetooth LE specifications, the connection interval is decided by the Master (Central Device). In your case, the Master is the mobile application. So, what is the application that you are running? Is it our DSPS mobile application or you have a custom mobile application? Have you done any other modification in the DSPS project?
A possible reason might be that you have increased the interval more than the watchdog timeout, so the device stucks in the WFI() waiting for an interrupt that never comes since the BLE event is far in time.
Additionally, keep in mind that an updated DSPS version is now released!
//www.wsdof.com/products/dialog-serial-port-service-dsps
It’s also compatible with the DA14531 TINY module!
//www.wsdof.com/products/bluetooth-module-da14531-smartbond-tiny
Thanks, PM_Dialog
Hi Dialog
May i modfiy watchdog timeout??
if i can modfiy watchdog timeout??
how to do that??
Hi alex.jian,
We have taken this offline from the forum. I have sent a message in your company email address (not in your registered email address).
Thanks, PM_Dialog