Flashing custom nRF52 (Bootloader, SoftDevice, Application)

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Fri, 17 Jan 2020 11:36:47 GMT

It's hard for me to say, I have not experienced this difference when testing with the original bootloader and buttonless implementation. Did you see this with the original buttonless template app as well?

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Fri, 17 Jan 2020 11:28:50 GMT

OK, thank you.

And what about the time difference when carrying out DFU with nRFToolbox?

Best regards,

Dani

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Fri, 17 Jan 2020 10:06:39 GMT

Hi Dani,

The 15.2 bootloader does not support this option. If you need to disable CRC checking you can change the nrf_bootloader.c::crc_on_valid_app_required() function so it always returns false.

Best regards,

Vidar

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Tue, 14 Jan 2020 14:42:25 GMT

Hi again,

I'm using SDK_15_2: when I try to set NO_VALIDATION (in order to allow me debugging the application), I get the following message:

How can I debug my app with DFU, then?

Best regards,

Dani.

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Tue, 14 Jan 2020 12:15:01 GMT

I have some more info: I have taken again the Smartphone and I have used nRFToolbox instead of nRFConnect, and DFU is also working. When selecting DFU, I select my device and then the zip file. Then, I push 'Upload', and file uploading starts after a few seconds (around 30"). During this seconds, the messages shown at the bottom are the following ones:

- Starting DFU --> Starting Bootloader --> Connecting --> Starting DFU --> File Uploading (upload percentage is shown).

So, what I have such differences depending on the tool I use to carry out DFU process?

All the best,

Dani.

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Tue, 14 Jan 2020 09:45:15 GMT

I get same results with function as in the following picture...

I was not in debugging mode: I will try it....

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Tue, 14 Jan 2020 08:55:51 GMT

Please comment out the code used to disable the Softdevice and stop the app timer. Also, do you have debug logging enabled in your app to see if the shutdown handler gets called right away?

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Tue, 14 Jan 2020 08:31:17 GMT

I have this function as depiced in the following picture:

And the result in what regards time is the same...

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Tue, 14 Jan 2020 06:57:01 GMT

[quote user="dtarrago"]In fact, according the code I have specified above, this function was already returning true[/quote]

When is the m_ready_for_reset flag set?

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Mon, 13 Jan 2020 14:45:13 GMT

The same: around 1 minute. In fact, according the code I have specified above, this function was already returning true.

Furthermore: In my application (when connected) a characteristic sends notifications once every 250ms. With nRF connect (Desktop), if this notifications are enabled, DFU initializing time is practically halved. If notifications are not enabled, time for DFU initialization is around 1m

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Mon, 13 Jan 2020 13:12:00 GMT

Try to change the app_shutdown_handler() implementation so it always return true on NRF_PWR_MGMT_EVT_PREPARE_DFU, then try again with nRF connect for desktop and see if it still takes a minute to get into DFU mode.

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Mon, 13 Jan 2020 13:00:25 GMT

Some more information: When I'm using nRF Connect desktop application, it seems that Bootloader do not enter until this 1-minute wait: once DFU is started application continues working normally (nRFConnect, says 'Initializing' -DFU) during this 1-minute. After that time, application is updated succesfully.

On the other hand, when I use Android application, it seems the Bootloader enters just after DFU button is pushed (application is not working): but then, application remains in 'Connecting...' for about 1-minute. After that time, application seems to be updated and it starts running again (Reset is carried out).

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Mon, 13 Jan 2020 09:47:55 GMT

Hi Vidar,

I have implemented DFU in the same way the 'Buttonless_dfu' is implement. My doubt is related to the 'app_shutdown_handler'. Shoult I have to modify it? Now it is in the following way:

static bool app_shutdown_handler(nrf_pwr_mgmt_evt_t event)
{
    switch (event)
    {
        case NRF_PWR_MGMT_EVT_PREPARE_DFU:
            NRF_LOG_INFO("Power management wants to reset to DFU mode.");
            // YOUR_JOB: Get ready to reset into DFU mode
            //
            // If you aren't finished with any ongoing tasks, return "false" to
            // signal to the system that reset is impossible at this stage.
            //
            // Here is an example using a variable to delay resetting the device.
            //
            // if (!m_ready_for_reset)
            // {
            //      return false;
            // }
            // else
            //{
            //
            //    // Device ready to enter
            //    uint32_t err_code;
            //    err_code = sd_softdevice_disable();
            //    APP_ERROR_CHECK(err_code);
            //    err_code = app_timer_stop_all();
            //    APP_ERROR_CHECK(err_code);
            //}
            break;

        default:
            // YOUR_JOB: Implement any of the other events available from the power management module:
            //      -NRF_PWR_MGMT_EVT_PREPARE_SYSOFF
            //      -NRF_PWR_MGMT_EVT_PREPARE_WAKEUP
            //      -NRF_PWR_MGMT_EVT_PREPARE_RESET
            return true;
    }

    NRF_LOG_INFO("Power management allowed to reset to DFU mode.");
    return true;
}

Apart of this, for DFU I have APP_ADV_INTERVAL set to 80 and APP_ADV_DURATION to 200 (same values as in my application).And in my application, advertising is done every 10s. Should this values cause any problem?

Best regards,

Dani.

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Mon, 13 Jan 2020 08:05:25 GMT

Hi Dani,

It should only take a few seconds to pre-validate the update and get started on the transfer. Maybe the buttonless implementation is not transferring execution to the bootloader right away and thus delaying the transfer start? Or do you see the same if you start DFU when the device is already in bootloader DFU mode?

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Fri, 10 Jan 2020 13:06:42 GMT

Hi Vidar,

I have succeeded in implementing Buttonless DFU into my prototype and it is working with nRF connect by Nordic: I have created the zip file containing my application and I was able to update the application via DFU using this tool.

The problem is that it takes more than one minute with DFU in 'initializing' state --> please look at the first screenshot showing this situation. After this minute, it starts transferring the file, and once the file is completely transferred, my device is reseted and new application starts working. So,

- Why is it taking such a long time initializing?

- Is it related to application size (zip file size is 131KB)?

When DFU procedure is working, what does it mean? Is it refering to BLE transfer or to the new application transfer inside device memory?

Best regards,

Dani.

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Fri, 20 Dec 2019 14:42:08 GMT

[quote userid="3586" url="~/f/nordic-q-a/38767/flashing-custom-nrf52-bootloader-softdevice-application/226054"]I have already found this: I had to create the bootloader setting.[/quote]

I'm referring to bootloader settings page that I assume you've created with nrfutil. Nrfutil has an option (as shown in screenshot) to disable boot validation of the app.

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Fri, 20 Dec 2019 14:34:39 GMT

Hi Vidar,

And what about the settings page that is needed to be modified for debugging?

Where is it? Which settings page are you referring to?

Best regards,

Dani

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Thu, 19 Dec 2019 14:39:55 GMT

Hi Dani,

I was referring to the bootloader settings page. The NRF_DFU_APP_DATA_AREA_SIZE flag is only used by the bootloader.

Best regards,

Vidar

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Thu, 19 Dec 2019 10:33:08 GMT

Hi Vidar,

Thank you again for your answers.

Which settings page are you referring to in your last answer?

Should the 'NRF_DFU_APP_DATA_AREA_SIZE ' parameter also be modified in the 'nrf_dfu_types.h' file when including this file (DFU service) into the application?

I'm working with Keil...

Best regards,

Dani.

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Thu, 19 Dec 2019 07:40:03 GMT

Hi Dani,

Yes, the settings page is needed to tell the bootloader that you have a valid application, it will fall back to DFU mode otherwise. As for debugging the app, you can do that after you've loaded the settings page. Just make sure to disable boot validation option in the settings page to allow the bootloader to boot the app even if it has been modified.

[quote user="dtarrago"]What about preserved data? Have I to consider extra settings when bootloader is present[/quote]

FDS automatically detects the presence of the bootloader and places the data below the bootloader instead of placing it at the end of flash, see Memory layout. Also, the NRF_DFU_APP_DATA_AREA_SIZE flag inside the bootloader must correspond to the number of FDS pages allocated by the app to ensure app data is preserved data through DFU. The default is usually 3 pages.

Best regards,

Vidar

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Wed, 18 Dec 2019 09:19:56 GMT

Hi again,

I have already found this: I had to create the bootloader setting.

Now, the application starts working but, when it has to start advertising, it seems to be hung!!!! do you know which can be the reason?

So,

- How can I debug my application when bootloader is present?

- What about preserved data? Have I to consider extra settings when bootloader is present?

Best regards,

Dani.

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Wed, 18 Dec 2019 08:25:30 GMT

Good morning,

I have suceeded in programming both softdevice and application with J-Flash tool by Segger and ARM flasher. It is perfectly working-

Now, I want to also include bootloader in order to have BLE-DFU implemented. I have created private_key following steps detailed in DFU_Step_by_step. I have merged bootloader, softdevice and application with J-Flash tool but device is not working. I suppose that it is a problem related with addresses. Is there any explanation showing which addresses to consider for all of this three parts in what regards the nRF52840 device?

Furthermore, is it required to create the zip file using this?:

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

I suppose this is only required when carrying out a BLE-DFU operation, right?

Apart of this: in my application I have some preserved data: I have set FDS_VIRTUAL_PAGES to 5 and preserved data is working without Bootloader. Do I have to consider something new with this preserved data when including bootloader? Is re-adressing carried out automatically?

All the best,

Dani

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Tue, 17 Dec 2019 12:45:32 GMT

You can flash everything at once regardless of what programmer you use, but you may want to merge the hex files first to speed up the process a bit. See Merging files with mergehex

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Dani — Tue, 17 Dec 2019 12:21:41 GMT

Thank you so much for your answer.

It will perfect to flash everything at once the first time, but later on, I will need the device to be updated via BLE (just the application).

Will the Segger ARM Flasher also work to flash everything?

Best regards,

Dani

RE: Flashing custom nRF52 (Bootloader, SoftDevice, Application)

Vidar Berg — Tue, 17 Dec 2019 12:05:44 GMT

Hi Dani, here's an updated link to the documentation I was referring to earlier: Production programming and testing.

[quote user="dtarrago"]Do I always need the Segger J-Link to flash bootloader? Are there any other options?[/quote]

The ICs are shipped blank from our factory, but some third-party modules may come pre-programmed with a bootlaoder.

[quote user="dtarrago"]Can the bootloader be flashed using the USB port?[/quote]

Unfortunately, no. The USB can only be enabled and controlled by FW running on the chip.

[quote user="dtarrago"]And in what regards SoftDevice, and Application: once I have the bootloader flashed, can they be flashed via BLE the first time (with DFU, of course)?[/quote]

You could just flash the MBR and bootloader and program the Softdevice and application afterward. But wouldn't it be better to flash everything at once? It will certainly be faster.

[quote user="dtarrago"]Which method do you recommend to flash Bootloader, SoftDevice, Application for mass production?[/quote]

I would say to program everything through the debug interface in one step if possible and not DFU. But it depends. Maybe you want the final FW to be uploaded after the product is enclosed, etc.

Best regards,

Vidar