hi i have problem!how to slow down the speed of bootloader receiving the app update.zip.
SDK 15.2.0 ,s112 ,securebootloader example ,nRF52810
hi i have problem!how to slow down the speed of bootloader receiving the app update.zip.
SDK 15.2.0 ,s112 ,securebootloader example ,nRF52810
Hi,
Could you explain why you want to slow down the speed?
Hi. I use the nRF Toobox with HUAWEI Mobilephone to update my app.zip.I had a problem that update failed when using the SDK13 ,S132, nRF52832 before.when I slow down the speed that uddate successful,but in SDK 15.2.0 ,s112 ,securebootloader example ,nRF52810 i could not find the parameter as follows!
/***********************/ //SDK13 ,S132, nRF52832 ble_opt_t op; memset(&op,0,sizeof(op)); op.common_opt.conn_bw.conn_bw.conn_bw_rx=BLE_CONN_BW_MID; op.common_opt.conn_bw.conn_bw.conn_bw_tx=BLE_CONN_BW_MID; op.common_opt.conn_bw.role = BLE_GAP_ROLE_PERIPH; err_code=sd_ble_opt_set(BLE_COMMON_OPT_CONN_BW,&op); if (err_code != NRF_SUCCESS) { NRF_LOG_ERROR("Bandwith option error", err_code); } else { NRF_LOG_INFO("Bandwith option ok\r\n"); }
nRF52810 i could not find the parameter as follows
Yes, the BLE bandwidth configuration and application packet concept has been changed. Previously, the application could specify a bandwidth setting, which would result in a given queue size and a correpsonding given radio time allocated. Now the queue sizes and the allocated radio time have been separated. The application can now configure:Event length, Write without response queue size, Handle Value Notification queue size.
The ble_enable_params_t::common_enable_params.p_conn_bw_counts parameter of the sd_ble_enable() SV call is replaced by the sd_ble_cfg_set() SV call with cfg_id parameter set to BLE_CONN_CFG_GAP.
To configure this so it corresponds to BLE_CONN_BW_MID, you should set the NRF_SDH_BLE_GAP_EVENT_LENGTH parameter in sdk_config.h to BLE_GAP_EVENT_LENGTH_DEFAULT
// <o> NRF_SDH_BLE_GAP_EVENT_LENGTH - GAP event length. // <i> The time set aside for this connection on every connection interval in 1.25 ms units. #ifndef NRF_SDH_BLE_GAP_EVENT_LENGTH #define NRF_SDH_BLE_GAP_EVENT_LENGTH BLE_GAP_EVENT_LENGTH_DEFAULT #endif
nRF52810 i could not find the parameter as follows
Yes, the BLE bandwidth configuration and application packet concept has been changed. Previously, the application could specify a bandwidth setting, which would result in a given queue size and a correpsonding given radio time allocated. Now the queue sizes and the allocated radio time have been separated. The application can now configure:Event length, Write without response queue size, Handle Value Notification queue size.
The ble_enable_params_t::common_enable_params.p_conn_bw_counts parameter of the sd_ble_enable() SV call is replaced by the sd_ble_cfg_set() SV call with cfg_id parameter set to BLE_CONN_CFG_GAP.
To configure this so it corresponds to BLE_CONN_BW_MID, you should set the NRF_SDH_BLE_GAP_EVENT_LENGTH parameter in sdk_config.h to BLE_GAP_EVENT_LENGTH_DEFAULT
// <o> NRF_SDH_BLE_GAP_EVENT_LENGTH - GAP event length. // <i> The time set aside for this connection on every connection interval in 1.25 ms units. #ifndef NRF_SDH_BLE_GAP_EVENT_LENGTH #define NRF_SDH_BLE_GAP_EVENT_LENGTH BLE_GAP_EVENT_LENGTH_DEFAULT #endif