ble_dfus WITH ble_nus

RE: ble_dfus WITH ble_nus

Hung Bui — Tue, 03 May 2016 15:28:53 GMT

Hi Szymon,

Please create a new question and ask your question, you are using the "answer" section.

Please add more information about the issue you are having and what showed when you try to debug it.

RE: ble_dfus WITH ble_nus

Szymon-ek — Fri, 29 Apr 2016 14:40:49 GMT

I have the same problem.

Code below run first two services but last one (DFU) do not work

Printf return errors : 0, 0, 4

also i have no idea how to mark code as one piece, welcome help

<code=c>

static void services_init(void) { // YOUR_JOB: Add code to initialize the services used by the application. uint32_t err_code;

ble_nus_init_t nus_init;

memset(&nus_init, 0, sizeof(nus_init));

  nus_init.data_handler = nus_data_handler;

err_code = ble_nus_init(&m_nus, &nus_init);
	printf("Error: %d", err_code);

// APP_ERROR_CHECK(err_code);

// Initialize Device Information Service.

ble_dis_init_t dis_init;
	
	memset(&dis_init, 0, sizeof(dis_init));

ble_srv_ascii_to_utf8(&dis_init.manufact_name_str, (char *)MANUFACTURER_NAME);

err_code = ble_dis_init(&dis_init);
	printf("Error: %d", err_code);

// APP_ERROR_CHECK(err_code); #ifdef BLE_DFU_APP_SUPPORT /** @snippet [DFU BLE Service initialization] */ ble_dfu_init_t dfus_init;

// Initialize the Device Firmware Update Service.
memset(&dfus_init, 0, sizeof(dfus_init));

dfus_init.evt_handler   = dfu_app_on_dfu_evt;
dfus_init.error_handler = NULL;
dfus_init.evt_handler   = dfu_app_on_dfu_evt;
dfus_init.revision      = DFU_REVISION;

err_code = ble_dfu_init(&m_dfus, &dfus_init);
	printf("Error: %d", err_code);

// APP_ERROR_CHECK(err_code);

dfu_app_reset_prepare_set(reset_prepare);
dfu_app_dm_appl_instance_set(m_app_handle);
/** @snippet [DFU BLE Service initialization] */

#endif // BLE_DFU_APP_SUPPORT }

RE: ble_dfus WITH ble_nus

Hung Bui — Mon, 03 Aug 2015 11:59:24 GMT

@la-ble: Could you sum up what the issue you are having now? I'm kind of lost. Why do you want to do add DFU service when you don't flash the bootloader. How do you jump to the bootloader ? via a soft reset or a branching ?

If possible please zip your project and update the file here. Also please don't mark the answer as correct when it has not fixed your issue.

RE: ble_dfus WITH ble_nus

la-ble — Sun, 02 Aug 2015 23:51:24 GMT

@HungBui, Master Control Panel is a really useful tool, thank you. Have it on PC now with PCA10000. 0x000E appears to be the handle for UART RX (from PC to nRF51822). I've updated the OP with a screenshot of all the data I can capture. There seems to be a conflict for pathway used to kick the firmware back to the bootloader (reset). In another trial (sporatically working) the UART RX characteristic has value 0x0016 and the DFU ClientCharacteristicConfiguration has handle value 0x000E.

RE: ble_dfus WITH ble_nus

Hung Bui — Thu, 16 Jul 2015 08:04:42 GMT

@la-ble: I meant Master Control Panel tool on PC, you would need a nRF51 dongle/dk to use it. Which central device are you testing now ?

RE: ble_dfus WITH ble_nus

la-ble — Thu, 16 Jul 2015 05:15:10 GMT

@HungBui, I do not have an Android device. Is there any to proceed without one?

RE: ble_dfus WITH ble_nus

Hung Bui — Tue, 23 Jun 2015 13:45:51 GMT

The p_evt_write I mentioned is exactly the p_evt_write you used in "p_evt_write->handle == p_nus->tx_handles.value_handle 0x000E != 0x0016."

Could you check what characteristic is at handle 0x000E ? You can find the handle using the Master Control Panel tool we have on PC. Note that you should add the breakpoint only after the CCCD has been enabled. When enabling CCCDs we also use write commands, so you will also have the BLE_GATTS_EVT_WRITE event for those commands.

RE: ble_dfus WITH ble_nus

la-ble — Tue, 23 Jun 2015 05:41:17 GMT

Is it better practice to execute ble_dfu_on_ble_evt before anything else? I've tried both with no difference. If I breakpoint just after ble_dfu_on_ble_evt my .evt_handler and .data_handler are correctly hooked up to my callback functions. I'm not sure what you mean by p_evt_write. I'm running SD v8.0.0. and do NOT have a bootloader in place right now as I develop/debug. On line 73 of ble_nus.c, the check isn't succeeding which allows the callback to be executed: p_evt_write->handle == p_nus->tx_handles.value_handle 0x000E != 0x0016.

RE: ble_dfus WITH ble_nus

Hung Bui — Mon, 22 Jun 2015 11:34:33 GMT

@la-ble: It's pretty strange what you experienced. I can see in your code ble_nus_on_ble_evt() is called before ble_dfu_on_ble_evt().

Could you add a breakpoint in ble_nus_on_ble_evt() at BLE_GATTS_EVT_WRITE event to check if the write command is correctly executed? There will be 2 write event, first is the one to set CCCD (only happens once), after that will be the write command for the actual data, checkout the p_evt_write->handle when the event arrives.