DFU update fails with message "INVALID OBJECT"

RE: DFU update fails with message "INVALID OBJECT"

Georg — Thu, 22 Apr 2021 13:01:16 GMT

Hello Edvin,

I will keep the problem with mergehex in mind. But up to now everything is ok for me. The ticket can be closed. Thank you!

Best regards,

Georg

RE: DFU update fails with message "INVALID OBJECT"

Edvin — Thu, 22 Apr 2021 11:58:32 GMT

Ok, glad to hear that.

Then what you are seeing is probably the mergehex bug that struggles with paddings on .hex files generated from IAR.

I suggest you either use the .hex files separately, or experiment on older versions of mergehex (part of nRF Command Line Tools), until a new version with a fix is released.

I will be out of office from tomorrow, so if you encounter any other issues related to this, please open a new ticket for a faster response.

Best regards,

Edvin

RE: DFU update fails with message "INVALID OBJECT"

Georg — Thu, 22 Apr 2021 11:47:33 GMT

Hallo Edvin,

thank you for your reply.

when programming the hex-files separately either with nrfjprog or with nrfconnect/programmer it works as expected.

Thank you for your help.

Best Regard

Georg

RE: DFU update fails with message "INVALID OBJECT"

Edvin — Thu, 22 Apr 2021 09:37:16 GMT

Hello Georg,

If you program the bl_settings.hex, and the device advertises as "DfuTarg", it means that the application is rejected by the bootloader, and the device is in DFU mode.

1: Can you try to not merge the .hex files, but program them separately using "nrfjprog --program ...", or nRF Connect -> Programmer. The reason I ask you to test this is that I have seen some compatibility issues with mergehex and .hex files generated from IAR.

By separately, I don't mean that you need to program them one at a time, but program each file instead of the merged file:

2: Are you sure that the bootloader settings are generated using the exact same application as the one you programmed? Please note that if you recompile, you need to generate the bootloader settings again.

As a last resort, try to run the attached script from the location SDK\examples\dfu\secure_bootloader\pca10100_s140_ble\armgcc.

devzone.nordicsemi.com/.../1200.test.bat

Best regards,

Edvin

RE: DFU update fails with message "INVALID OBJECT"

Georg — Wed, 21 Apr 2021 14:02:06 GMT

Hallo again,

in the meantime I found a solution, thanks to your help. 😊

The problem was: that I had worked with the wrong SD/pca combination for the nrf52833.

correct combination: s140 / pca10100

wrong combination: s132 / pca10140

First of all I created an IAR "buttonless_dfu_pca10100_s140-nerf52833 " project.

Unfortunately the SDK16.0.0. does not provide such an example project.

For the bootloader I am using the secure_bootloader_ble_s140_pca10100 project.

Now it works fine.

But there is now a new strange behaviour:😒

1. Programming the "complete" hex-file (APP + BL + SD + BL-setting) into the nrf52833

2. When scanning I expect to see the App - "Nordic_Buttonless" but I see the bootloader - "DfuTarg"

3. Updating the firmware with nRF Toolbox/DFU App The message "Application has been successfully transfered" appears instead of "INALVID OBJECT" 😊

4. When scanning I see the App "Nordic_Buttonless" (as expected)

It seems that there is something wrong with the bootloader settings in the "complete" hex -file.

After executing an DFU update the bootloader settings seems to be corrected.

When debugging into the "buttonless_dfu" APP (after step 1.), the

bootloader_addr = 0xFFFFFFFF!

uint32_t nrf_dfu_svci_vector_table_set(void)
{
    uint32_t err_code;
    uint32_t bootloader_addr = BOOTLOADER_ADDRESS;

    if (bootloader_addr != 0xFFFFFFFF)
    {
        NRF_LOG_INFO("Setting vector table to bootloader: 0x%08x", bootloader_addr);
        err_code = sd_softdevice_vector_table_base_set(bootloader_addr);
        if (err_code != NRF_SUCCESS)
        {
            NRF_LOG_ERROR("Failed running sd_softdevice_vector_table_base_set");
            return err_code;
        }

        return NRF_SUCCESS;
    }

Commands to build the complete.hex and the app.zip

1. generate bootloader settings:

nrfutil settings generate --family NRF52 --application ble_app_buttonless_dfu_pca10100_s140.hex --application-version 1 --bootloader-version 0 --bl-settings-version 2 bootloader_setting.hex

2. merge application, bootloader, softdevice and bootloader-settings

mergehex --merge bootloader_setting.hex secure_bootloader_ble_s140_pca10100.hex s140_nrf52_7.0.1_softdevice.hex --output bl.hex
mergehex --merge bl.hex ble_app_buttonless_dfu_pca10100_s140.hex --output complete.hex

3. generate the zip file
nrfutil pkg generate --hw-version 52 --application-version 1 --application ble_app_buttonless_dfu_pca10100_s140.hex --sd-req 0xCA --key-file private.key app.zip

Any Ideas ?

Thank you !

Best Regards

Georg

RE: DFU update fails with message "INVALID OBJECT"

Edvin — Tue, 20 Apr 2021 14:45:05 GMT

Perhaps it doesn't like that you are using the same application-version as you already have. Try generating a new one with --application-version 2, and see if that helps. But I think by default, it should accept same version (application-version). However, it is worth a shot.

[quote user="dschordsch"]I am using a nrf52832 porject together with nrf52833 chip, could this be the problem ?[/quote]

I suggest you try using an nRF52833 project. Did you try the pca10100_s140_ble instead of pca10040_s132_ble? Actually, I didn't know until now that you were using the nRF52833.

Also, make sure that you use the bootloader.hex file that you have compiled, and not any of the precompiled bootloader .hex files from the SDK.

In addition, the s132 is not certified with the nRF52833. And I am not sure it will work. Try using either the s140 or s113 projects from the SDK16\examples\dfu\secure_bootloader\pca10100_s1xx_ble.

Can you please test the armgcc project files? I have not used IAR before, and I am not sure there are any issues with these. I am not saying you need to use it in the end, but since you already have make installed (you should have since you have built the micro-ecc libraries), just call "make" from a command line in the folder SDK\examples\dfu\secure_bootloader\pca10100_s140_ble\armgcc, and use the .hex file generated in the _build folder from that location.

Best regards,

Edvin

RE: DFU update fails with message "INVALID OBJECT"

Georg — Tue, 20 Apr 2021 14:21:25 GMT

Hallo Edvin

Thank you for you reply.

As I described at point 3: I copied dfu_public_key.c to the BL project before building the BL (secure_bootloader_ble_s132_pca10040.hex) .

I changed only dfu_public_key.c in the example BL project.

What is the reason for the "invalid object" message ?

Is there something wrong with the keys or signature ?

I looked in the BL map file and I see that the oberon lib is used. Is this correct or is uECC-lib the right one ?

I am using a nrf52832 porject together with nrf52833 chip, could this be the problem ?

I tried a lot of things but I still suck 😢.

Regards

Georg

RE: DFU update fails with message "INVALID OBJECT"

Edvin — Tue, 20 Apr 2021 12:40:43 GMT

Hello,

[quote user="dschordsch"]Sorry I don't understand your answer, because I built the zip-file out of the application (ble_app_buttonless_dfu_pca10040_s132.hex) and not from he "complete" hex-file (my_ble_app_buttonless_dfu_without_bonds_s132_with_setting_page.hex) which was made of (APP + BL + SD + BL-setting ).[/quote]

Sorry. That is correct. I thought you used the merged image.

Please ensure that your bootloader is using a dfu_public_key.c that is generated with the private.key that you are using to sign your image.

If you are still stuck. Have you done any (!) changes to the bootloader project other than changing the dfu_public_key.c?

RE: DFU update fails with message "INVALID OBJECT"

Georg — Tue, 20 Apr 2021 07:24:45 GMT

Hello Edvin,

thank you for your fast answer.

I intend only to update the application.

Sorry I don't understand your answer, because I built the zip-file out of the application (ble_app_buttonless_dfu_pca10040_s132.hex) and not from he "complete" hex-file (my_ble_app_buttonless_dfu_without_bonds_s132_with_setting_page.hex) which was made of (APP + BL + SD + BL-setting ).

The "complete" hex-file (my_ble_app_buttonless_dfu_without_bonds_s132_with_setting_page.hex) is the file for the production. The customer updates the product by using ble_app_buttonless_dfu_without_bonds_s132.zip

I have already read the tutorial that you are mentioned.

APP = ble_app_buttonless_dfu_pca10040_s132.hex

BL = secure_bootloader_ble_s132_pca10040.hex

BL-SETTINGS = bootloader_setting.hex

SD = s132_nrf52_7.0.1.hex

APP + BL + SD + BL-Settings = my_ble_app_buttonless_dfu_without_bonds_s132_with_setting_page.hex

Do you have any ideas what could be the problem ?

Regards

Georg

RE: DFU update fails with message "INVALID OBJECT"

Edvin — Mon, 19 Apr 2021 14:27:49 GMT

Hello,

I see that you are using your merged .hex file (app, sd and bootlaoder) to generate your dfu image, but your pkg doesn't contain information that it contains the sd and bl.

Do you intend to update all these? Note that you can update the application only. If you just replace the "my_ble_app_buttonless_dfu_without_bonds_s132" with the "ble_app_buttonless_dfu_pca10040_s132" in your "nrfutil pkg generate ..." command, I think it should be fine.

If you intentionally want to update the BL and SD as well, you need to keep these separated (don't merge them), and then use the "--sd-id <version>" for the new softdevice, and --softdevice <path to softdevice>, and the same for the bootloader: --bootloader <bootloader .hex> and --bl-version <bootloader version>.

If you are new to DFU, I suggest you gp through this tutorial:

https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader

BR,

Edvin