Getting problem to upload Bootloader HEX file through nRFgo Studio...

RE: Getting problem to upload Bootloader HEX file through nRFgo Studio...

Urvisha Andani — Tue, 25 Feb 2020 10:30:46 GMT

Thanks for support.

[quote userid="7571" url="~/f/nordic-q-a/56851/getting-problem-to-upload-bootloader-hex-file-through-nrfgo-studio/236142"]Try increasing the --application-version to 2. [/quote]

It's working now, after changing application version to create .zip file.

DFU is also working after combining softdevice, bootloader and application hex file.

RE: Getting problem to upload Bootloader HEX file through nRFgo Studio...

bjorn-spockeli — Tue, 25 Feb 2020 07:57:48 GMT

Try increasing the --application-version to 2.

RE: Getting problem to upload Bootloader HEX file through nRFgo Studio...

Urvisha Andani — Tue, 25 Feb 2020 04:39:52 GMT

Thank for support.

[quote userid="7571" url="~/f/nordic-q-a/56851/getting-problem-to-upload-bootloader-hex-file-through-nrfgo-studio/235933"]Can you post the nrfutil command you used to generate the .zip for the update in step 5?[/quote]

Yes, I use below command to create .zip file,

nrfutil pkg generate --hw-version 52 --application-version 1 --application ble_app_template_pca10040_s132.hex --sd-req 0xB7 --key-file private.key app_dfu_package.zip

RE: Getting problem to upload Bootloader HEX file through nRFgo Studio...

bjorn-spockeli — Mon, 24 Feb 2020 11:30:57 GMT

You are getting a firmware version error, so this means that either the application version, i.e. --application-version 1 or the bootloader version, i.e. --bootloader-version 1, is to low, see Acceptance rules for versions, copy pasted relevant section below:

Firmware version: If the image contains a bootloader, the image is accepted if the new firmware version is greater than (>) the existing version of the bootloader. If the image contains an application, the image is accepted if the new firmware version is greater than or equal to (>=) the existing version of the application. If the image contains a SoftDevice and no SoftDevice is already present, the fw_version is checked against the existing application's version to determine whether the update can overwrite it.

Can you post the nrfutil command you used to generate the .zip for the update in step 5?

RE: Getting problem to upload Bootloader HEX file through nRFgo Studio...

Urvisha Andani — Sat, 22 Feb 2020 05:54:03 GMT

Sorry for late reply.

[quote userid="7571" url="~/f/nordic-q-a/56851/getting-problem-to-upload-bootloader-hex-file-through-nrfgo-studio/230511"]Can you elaborate on the problems you are facing after changing the flash size of the application? Do you have any logs from nRF Connect when the upload of the zip fails?[/quote]

Yes, Show below attached images.

[quote userid="7571" url="~/f/nordic-q-a/56851/getting-problem-to-upload-bootloader-hex-file-through-nrfgo-studio/230511"]The mergehex commands look ok. Does the application start after you flash the sd_app_boot_setting_complete_52832.hex to the nRF52832?[/quote]

Yes, application start after flash sd_app_boot_seeting_complete_52832.hex, But in this I am getting problem to upload new dfu package.

I follow below step,

1) Erase chip and through nRF connect programmer I am upload sd_app_boot_seeting_complete_52832.hex file.

2) Connect device with nrf connect mobile application.

3) Enable notification of DFU and send request.

4)Device Start advertising of bootloader code.

5) Device connect with mobile application and i upload .zip file in thisI am getting problem and device disconnect with mobile.

So, Please give me solution for this.

RE: Getting problem to upload Bootloader HEX file through nRFgo Studio...

bjorn-spockeli — Thu, 23 Jan 2020 09:05:24 GMT

[quote user="Urvisha Andani"][/quote]

In this I am getting problem of upload .zip file using bootloader.

And also using older one FLASH size(0x5e000) I am getting same problem.

I am use merge HEX file of softdevice, bootloader bootloader setting page, application.

I use command mention in below document to merge HEX file,

Hi Urvisha,

Can you elaborate on the problems you are facing after changing the flash size of the application? Do you have any logs from nRF Connect when the upload of the zip fails?

The mergehex commands look ok. Does the application start after you flash the sd_app_boot_setting_complete_52832.hex to the nRF52832?

Best regards

Bjørn

RE: Getting problem to upload Bootloader HEX file through nRFgo Studio...

Urvisha Andani — Wed, 22 Jan 2020 12:52:37 GMT

[quote userid="7571" url="~/f/nordic-q-a/56851/getting-problem-to-upload-bootloader-hex-file-through-nrfgo-studio/230243"]nRFGo Studio is deprecated for the nRF52 Series and you need to use nRF Connect Programmer instead. [/quote]

Thanks for support.

I tried this and I upload successfully HEX file using nRF Connect Programmer.

[quote userid="7571" url="~/f/nordic-q-a/56851/getting-problem-to-upload-bootloader-hex-file-through-nrfgo-studio/230243"]The application is configured to use all the available flash on the nRF52832, i.e. FLASH_START+FLASH_SIZE = FLASH_PH_SIZE. In the bootloader RAM and Flash settings you see that the bootloader starts at 0x78000, hence you need to adjust the application FLASH_SIZE to 0x26000-0x78000 = 0x52000.[/quote]

I am changed FLASE size as you suggest.
In this I am getting problem of upload .zip file using bootloader.

And also using older one FLASH size(0x5e000) I am getting same problem.

I am use merge HEX file of softdevice, bootloader bootloader setting page, application.

I use command mention in below document to merge HEX file,

devzone.nordicsemi.com/.../DFU-FLOW.docx

RE: Getting problem to upload Bootloader HEX file through nRFgo Studio...

bjorn-spockeli — Wed, 22 Jan 2020 08:43:07 GMT

Hi Urvisha,

nRFGo Studio is deprecated for the nRF52 Series and you need to use nRF Connect Programmer instead.

The application is configured to use all the available flash on the nRF52832, i.e. FLASH_START+FLASH_SIZE = FLASH_PH_SIZE. In the bootloader RAM and Flash settings you see that the bootloader starts at 0x78000, hence you need to adjust the application FLASH_SIZE to 0x26000-0x78000 = 0x52000.

Best regards

Bjørn