DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

RE: DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

carloscoelho — Fri, 08 Jan 2021 08:29:12 GMT

This ticket for me is closed, thank you.

RE: DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

ovrebekk — Tue, 29 Dec 2020 12:36:37 GMT

I am glad to hear you got it working. The best of luck with your project 🙂

Best regards
Torbjørn

RE: DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

carloscoelho — Tue, 22 Dec 2020 15:15:41 GMT

Hi Torbjon,

Thank you for the informations, I was able to load the application with this procedure.

I will open a new ticket with DFU questions,

Best regards

RE: DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

ovrebekk — Tue, 22 Dec 2020 10:19:56 GMT

[quote user="carloscoelho"]I changed the ble_uuid_t definition, I used the same UUID_TYPE and after that I did not have more errors:[/quote]

This might build and run OK, but the problem with this method is that you will advertise the wrong NUS service UUID.

The BLE_UUID_NUS_SERVICE has to go together with the NUS_SERVICE_UUID_TYPE, otherwise the UUID will not be correct.

I would recommend either removing the BLE_UUID_DEVICE_INFORMATION_SERVICE from the list, or add the UUID's to the scan response packet and not the advertise packet.

[quote user="carloscoelho"]I loaded dfu/secure_bootloader and ble_peripheral\ble_app_buttonless_dfu, I noticed that the aplication goes to BootLoader during the start and I'm not able to run ble_app_buttonless_dfu.[/quote]

Yes, this is a common issue if you don't use the bootloader to load the application, but load everything using nrfjprog or SES.

Please refer to this article for some pointers on how to handle this.

Also, if you have more detailed questions on DFU I recommend opening a new ticket, since I have limited experience with this ;)

Best regards
Torbjørn

RE: DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

carloscoelho — Mon, 21 Dec 2020 13:54:02 GMT

Hi Torbjon,

I changed the ble_uuid_t definition, I used the same UUID_TYPE and after that I did not have more errors:

static ble_uuid_t m_adv_uuids[] = { {BLE_UUID_NUS_SERVICE, BLE_UUID_TYPE_BLE }, {BLE_UUID_DEVICE_INFORMATION_SERVICE, BLE_UUID_TYPE_BLE}};

I loaded dfu/secure_bootloader and ble_peripheral\ble_app_buttonless_dfu, I noticed that the aplication goes to BootLoader during the start and I'm not able to run ble_app_buttonless_dfu.

I had to create the ZIP file with ble_app_buttonless_dfu an send thru nRF connect aplication.

Is there a way to set up the boot enviroment to run ble_app_buttonless_dfu after uploading it?

Thanks in advance,

RE: DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

ovrebekk — Mon, 21 Dec 2020 12:40:28 GMT

Hi Carlos

1) After calling ble_advertising_init you can access the raw data for the advertise packet and the scan response packet through the m_advertising struct.

The code snippet below shows how you can output this to the log:

err_code = ble_advertising_init(&m_advertising, &init);
APP_ERROR_CHECK(err_code);

uint32_t adv_len, sr_len;
adv_len = m_advertising.adv_data.adv_data.len;
sr_len = m_advertising.adv_data.scan_rsp_data.len;
NRF_LOG_INFO("adv_len: %i, sr_len: %i", adv_len, sr_len);

2) You mean you want a guide on how to create your own UUID?

This is actually as easy as creating a random one, using a UUID generator such as this one.

Because of the huge number of possible 128-bit numbers there is no need to register your UUID anywhere.

Best regards
Torbjørn

RE: DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

carloscoelho — Mon, 21 Dec 2020 08:31:08 GMT

Hi Torbjon,

Thank you fo your prompt reply

1) How can I check how much packet I'm using before I add DFU service?

2) I do copy paste the examples with UUID setup, I do not know what would be the correct UUID setup, do you have a DOC that explains that,

Best regards,

Carlos

RE: DFU SERVICE ERROR WHILE ACTIVATING BLE UART SERVICE

ovrebekk — Fri, 18 Dec 2020 11:01:33 GMT

Most likely you are running out of room in the advertise packet, since it is limited to 31 bytes in total. Adding a 16-bit UUID requires an additional 4 bytes (2 for the header and 2 for the UUID).

Can you check how much of the packet you are using before you add the DFU service UUID?

As a side note, if you are planning to use the NUS service for a product it is recommended to change the UUID, otherwise you have no way of differentiating your product from all the devices running the standard NUS example.

Best regards
Torbjørn