Bootloader problem (code = 3)

RE: Bootloader problem (code = 3)

Bjørn Kvaale — Tue, 03 Apr 2018 07:29:07 GMT

Great! Good to hear that you figured it out! Good luck with further development.

RE: Bootloader problem (code = 3)

d.altmann — Thu, 29 Mar 2018 17:45:20 GMT

Hi Bjorn,

I have recompile the bootloader source code with Release part (with private/public key, etc....) and I have update my "nRFUtils".

I follows your tutorials to compile the different source code and I works good (I use the new Gcc (Version 7-2017) to compile all without error.

Now, All work fine.

Thank to your helps.

We can close this post.

Best regards,

Damien

RE: Bootloader problem (code = 3)

Bjørn Kvaale — Wed, 07 Mar 2018 15:11:36 GMT

Hi Damien,

Regarding the custom board file, it might be useful to check this link (see this case too). In addition, this infocenter document could be helpful.

Regarding the RC source, the NRF_SDH_CLOCK_LF_SRC 0 is the only change you need to make. So this step is correct if you want to use the internal Low Frequency RC oscillator.

When you say that the nrf52832 component does not have an external clock, you are referring to the 32 kHz low frequency clock, right? Because the Laird module has a 32 MHz high frequency external crystal oscillator according to the datasheet.

Could be a good idea to update to nrfUtil v 3.5.0, although I have gotten this to work with 3.4.0 too.

Like you mention, it could also be a good idea to use the release version of the bootloader project with the private key. I have a feeling this might be related to the board file maybe, as this example works fine with the nrf52dk when following the secure dfu blog post. You can use the same nrfutil command as given in the blog post.

Hope that helps! Kind Regards,

Bjørn Kvaale

RE: Bootloader problem (code = 3)

d.altmann — Wed, 07 Mar 2018 06:07:31 GMT

Hi Bjorn,

In bootloader project, I have made a custom_Board file:

#define NRF_CLOCK_LFCLKSRC      {.source       = NRF_CLOCK_LF_SRC_RC,      \
                                 .rc_ctiv      = 16,                          \
                                 .rc_temp_ctiv = 2,                          \
                                 .accuracy     =  NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM}

Into the sdk_config.h, I enable the RC source:

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

--> I have to enable another part for active the RC source ??

- Ok, I try to follow this blog.

- The nrfUtil version is the 3.4.0.

--> Can I shall be update it ?

- I try your command but the nRFutil have a error because it missing the hw-version and the sd-req. I add this 2 parameters.

My new command line is:

nrfutil pkg generate --debug-mode --application application.hex app_dfu_package.zip --hw-version 52 --sd-req 0x9D

I have try with this new file app_dfu_package.zip but the result is the same. The error (code = 3) appears.

Perhaps, I try to compile the bootloader project with release version (no debug version) with a private key...

Thank you,

Best regards,

Damien

RE: Bootloader problem (code = 3)

Bjørn Kvaale — Tue, 06 Mar 2018 10:08:53 GMT

Hi Damien,

Did you remember to change the clock to internal RC for both the nrf52 chip & the softdevice? Also, did you follow the testing link provided here? In addition, this blog post might be useful. It is based on the same testing procedure.

Which version of nrfutil are you running (you can check this by running the command: nrfutil version)?

I believe if you are not using the secure private key, you might need to run this command instead:

nrfutil pkg generate --debug-mode --application application.hex app_dfu_package.zip

This will skip version information (hardware version, softdevice firmware ID & application version) & generate an unsigned debug package (see link).

I would then perform the DFU like you have done using nrf connect for android only uploading the zip file created (i.e. app_dfu_package.zip). Hope that helps!