SD+BL+APP dfu only update SD+APP successfully

RE: SD+BL+APP dfu only update SD+APP successfully

Einar Thorsrud — Wed, 19 Jan 2022 14:11:07 GMT

Hi,

[quote user="_maibi"]something special for this is that I customized init packet added some parameters (models, etc..).[/quote]

That is very relevant. Which exact changes did you do?

[quote user="_maibi"]I'll reply it when I get back to work tomorrow.[/quote]

Please do. And again, include all details of all steps. Without it, I have no way of understanding what could be happening.

RE: SD+BL+APP dfu only update SD+APP successfully

_maibi — Wed, 19 Jan 2022 13:58:13 GMT

[quote userid="7377" url="~/f/nordic-q-a/83767/sd-bl-app-dfu-only-update-sd-app-successfully/348512#348512"]How you build both bootloader variants[/quote]

The old one build 15.X.X SDK and I updated my library to 17.0.2 SDK and then, build it.

[quote userid="7377" url="~/f/nordic-q-a/83767/sd-bl-app-dfu-only-update-sd-app-successfully/348512#348512"]how you generate the DFU images[/quote]

The generation of package is easy to me. I have deployed many times of application only packages. but, sd+bl+app full package is first time. That being said, It isn't hard to me.

something special for this is that I customized init packet added some parameters (models, etc..).

[quote userid="7377" url="~/f/nordic-q-a/83767/sd-bl-app-dfu-only-update-sd-app-successfully/348512#348512"]how you flash, and how you do the DFU?[/quote]

In factory for production, Our company have used I-DAP tool and S/W supplied by I-DAP syst.

In development, I have used nrf-connect programmer. I have wrote and read flash dump using it.

And, I have used i-phone to dfu.

[quote userid="7377" url="~/f/nordic-q-a/83767/sd-bl-app-dfu-only-update-sd-app-successfully/348512#348512"]Include all logs, also from the DFU master.[/quote]

I'll reply it when I get back to work tomorrow.

RE: SD+BL+APP dfu only update SD+APP successfully

Einar Thorsrud — Wed, 19 Jan 2022 13:18:43 GMT

I see. The problem is that I am not able to understand how this happens from only a high level description of what you are doing. Please explain every step in full detail? How you build both bootloader variants, how you generate the DFU images, how you flash, and how you do the DFU? Please copy past all commands you make, and the resulting output. Include all logs, also from the DFU master.

RE: SD+BL+APP dfu only update SD+APP successfully

_maibi — Wed, 19 Jan 2022 12:04:21 GMT

Sorry for my poor english skills.

1. start dfu SD+BL+APP through ble.

-> result: The dfu progress looks fine. (no error) but, only bootloader wasn't updated.

-> prove: I changed advertisement name in new bootloader. and I erase application area in flash. so, the device run in bootloader. but the advertisement name is still old. i double checked by comparing old bootloader and updated bootloader device flash data.

2. after 1, start dfu BL only through ble.

-> result: nothing change. no errors. but doesn't updated.

RE: SD+BL+APP dfu only update SD+APP successfully

Einar Thorsrud — Wed, 19 Jan 2022 07:56:16 GMT

I am having problems understanding exactly what you have done. Can you explain in detail, step by step? Also indicate what you see as a result for each step (for instance, if the DFU master indicates that the bootloader update was successful or not, as it really should be updated if you did not see an error).

RE: SD+BL+APP dfu only update SD+APP successfully

_maibi — Wed, 19 Jan 2022 01:38:30 GMT

I have updated a package (bootloader only) with increased bootloader version.

It looks fine. but still not working. I deleted application sector and forcedly go to bootloader. I check advertisement name. but still old version name.

I double checked flash dump to read back flash by nrf-connect programmer. and compare old bootloader hex file. It isn't updated.

What I start for handling this issue?

RE: SD+BL+APP dfu only update SD+APP successfully

_maibi — Tue, 18 Jan 2022 11:31:46 GMT

Hi, Einar Thorsrud.

[quote userid="7377" url="~/f/nordic-q-a/83767/sd-bl-app-dfu-only-update-sd-app-successfully/348222#348222"]If you update to a new SoftDevice version, a bootloader update is also enforced. This is don so in order to avoid bricking devices in the filed. Specifically, if you upgrade to SoftDevice which is not compatible with the old bootloader, this would render the device non-upgradable in the future, and is why this is prevented.[/quote]

Yeah, I know this. so, It is blocked to generate sd+app dfu package.

However, I'm not asking for it, it's happening right now.

It is very strange behavior. I came up with an idea that the device which is failed to update sd+bl+app will be updated for only bootloader dfu package.

I'll try it tomorrow and let you know.

RE: SD+BL+APP dfu only update SD+APP successfully

Einar Thorsrud — Tue, 18 Jan 2022 09:58:33 GMT

Hi,

SoftDevice updates without a simultaneous bootloader update is only supported if the SoftDevice has the same major version. If you update to a new SoftDevice version, a bootloader update is also enforced. This is don so in order to avoid bricking devices in the filed. Specifically, if you upgrade to SoftDevice which is not compatible with the old bootloader, this would render the device non-upgradable in the future, and is why this is prevented. This check is done by the bootloader, so you will not see this when programming with a debugger. I suspect you will see issues if you try to do a update via DFU again afterwards though, as you have an incompatible bootloader and SoftDevice.