How to upload OTA again after successful first Buttonless OTA upload?

RE: How to upload OTA again after successful first Buttonless OTA upload?

Bjørn Kvaale — Wed, 22 Aug 2018 08:29:47 GMT

Hi Alex,

Sorry for the delayed response. Have you tried changing the application version to 1 instead of 0? If you already have the application installed on your device, the bootloader most likely has stored the application version as 0. The application version should be greater than the previously stored value, as can be read in Hung Bui's blog post here:

"--application-version: By default the start number for application version is 0. To be able to update new application, the application version should equal or greater than the one the bootloader stored. This case I use 1. Read more about version rule."

Unfortunately, I do not have a 51 dev kit with me at the moment, but I will test your code tomorrow.

Kind Regards,

Bjørn

RE: How to upload OTA again after successful first Buttonless OTA upload?

alex kim — Wed, 15 Aug 2018 12:21:57 GMT

Hi, Bjorn

I was late to develop a product based on multilink for a month

I changed the address according to your advice and the device search is done.

However, device names and services appear as unknown.

I have attached the file. The used program used a previously uploaded zip file.

nrfutil pkg generate --hw-version 51 --sd-req 0x87 --application-version 0 --application app.hex --key-file private.key app_dfu_package.zip

In the DfuTarg state, the program is normally downloaded dfu_package.zip.

I do not know what's wrong.

I'm more confused in my head

Best regards,

Alex

RE: How to upload OTA again after successful first Buttonless OTA upload?

Bjørn Kvaale — Fri, 03 Aug 2018 11:42:59 GMT

Hi Alex,

Sorry for the delayed response. I ran your example & started a uart log, where I saw this message at the top:

SDH:DEBUG:sd_ble_enable: RAM start at 0x20001ff8
SDH:WARNING:sd_ble_enable: RAM start should be adjusted to 0x20001fe8
SDH:WARNING:RAM size should be adjusted to 0x6018

As soon as I changed the IRAM1 Start & Size, the device advertised like it should:

This custom service tutorial summarizes why the RAM needs to be increased: "Now, adding a vendor-specific UUID to the BLE stack results in the RAM requirement of the SoftDevice increasing, which we need to take into account."

Hope that helps! Have a nice day!

RE: How to upload OTA again after successful first Buttonless OTA upload?

alex kim — Mon, 30 Jul 2018 12:15:47 GMT

Hi, Bjorn

Sorry for the late reply.
I use a keil IDE.
I attached zip file.

Best regards

Alex
devzone.nordicsemi.com/.../uart_5F00_buttonless_5F00_dfu.zip

RE: How to upload OTA again after successful first Buttonless OTA upload?

Bjørn Kvaale — Thu, 26 Jul 2018 12:35:56 GMT

Would you mind zipping up your whole project so I can test it?

RE: How to upload OTA again after successful first Buttonless OTA upload?

alex kim — Mon, 23 Jul 2018 07:40:52 GMT

Thank you for your kind advice.
But I have not yet solved the buttonless dfu.
According to your advice I merged the ble_app_nus with the buttonless_dfu application
In the DfuTarg state, the program is normally downloaded.
If I set #define TEST 0 in main.c, 'Buttonless dfu' appears in scan using nRFConnect.
However, if I set #define TEST 1 in main.c and scan using nRFConnect, nothing is scanned.

Other modifications can be found in softdevice_handler.c:

p_ble_enable_params-> common_enable_params.vs_uuid_count = 2; //orig 1

I attach main.c and nrfLog.
regards,

devzone.nordicsemi.com/.../Log-2018_2D00_07_2D00_23-160816.txt devzone.nordicsemi.com/.../70678.main.c

RE: How to upload OTA again after successful first Buttonless OTA upload?

Bjørn Kvaale — Tue, 10 Jul 2018 14:13:10 GMT

Take a look at this devzone case.

RE: How to upload OTA again after successful first Buttonless OTA upload?

Bjørn Kvaale — Fri, 06 Jul 2018 12:24:33 GMT

This is because the modified program (ble_app_hrs) does not include the DFU service. What you can do is merge the ble_app_hrs with the buttonless_dfu application (e.g. using the buttonless dfu example as the base example). That way, you should get the functionality of the hrs example (or whatever other app you want to use), while still being able to write to the bootloader settings page (see Section "Buttonless DFU" in link for more info). These links should also be helpful: link 1, link 2.

RE: How to upload OTA again after successful first Buttonless OTA upload?

alex kim — Thu, 05 Jul 2018 07:44:32 GMT

Did you first do a regular DFU

=> yes, build bootloader_secure

run nrfutil settings

mregehex bootloader_secure, settings file

download pca10028

the buttonless application did not advertise as Nordic_Buttonless, right?

=> no, advertise as Nordic_Buttonless

download my application program via nRF toolbox in smartphone

now you want to do a new DFU via the smartphone?

= > no, i want to do a modified application program via smartphone

How do I re-download a modified program via smartphone using buttonless while the application(ex: ble_app_hrs) is running?

If I run scan from dfu in nRFTool Box, Nordic Buttonless will not appear

RE: How to upload OTA again after successful first Buttonless OTA upload?

Bjørn Kvaale — Wed, 04 Jul 2018 13:59:47 GMT

Hi Alex,

I am slightly confused. Did you follow the testing procedure provided here?

Did you first do a regular DFU where you updated the application to Nordic buttonless & now you want to do a new DFU via the smartphone? Once you finished the first DFU, the buttonless application did not advertise as Nordic_Buttonless, right?