Changing REGOUT0 value to 3v3 in a DFU enabled software

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

Vidar Berg — Tue, 04 May 2021 13:38:06 GMT

Hi Onur,

Good to hear that you found the problem. Yes, it's important to disable the NRF_BL_DFU_ENTER_METHOD_BUTTON option when having a bootloader button.

Kind regards,

Vidar

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

OnurGules — Tue, 04 May 2021 13:35:55 GMT

Hi Vidar,

We were able to find out the issue. I somehow missed that dfu_enter_check() was returning true because of this code:

    if (NRF_BL_DFU_ENTER_METHOD_BUTTON &&
       (nrf_gpio_pin_read(NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN) == 0))
    {
        NRF_LOG_DEBUG("DFU mode requested via button.");
        return true;
    }

So, we were clearing NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN while setting REGOUT 0 to 3V3. We don't actually have any buttons on our board so commenting out this code solved our problem.

Thanks for your help.

Onur Gules.

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

Vidar Berg — Tue, 04 May 2021 13:03:49 GMT

Hi Onur,

Have you had any progress on this? As I mentioned in the other post, the board should not really reset unless the supply voltage dips below 2.5v. Do you know if the supply voltage is stable in your case?

Kind regards,

Vidar

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

OnurGules — Fri, 30 Apr 2021 12:47:10 GMT

Hi Vidar,

I tried:

nrfjprog --memwr 0x10001304 --val 3
nrfjprog --reset

The device is stuck in bootloader mode after reset.

Kind regards,

Onur.

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

Vidar Berg — Fri, 30 Apr 2021 12:02:59 GMT

Hi Onur,

Interesting, so it's likely not SW related then. I wonder if you may be running into the same problem as the forum user in the other post reported. Could try to lower the REG0 voltage to 3v0 or less to see if that works?

Kind regards,

Vidar

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

OnurGules — Fri, 30 Apr 2021 09:37:41 GMT

Hi Vidar,

I tried setting it directly with nrfjprog as you described. The device works fine before setting REGOUT0 to 5, and is stuck in bootloader after.

I also found this thread:

https://devzone.nordicsemi.com/f/nordic-q-a/73814/regout0-set-to-3-3v-fail-buttonless-dfu

Not sure how, but their problem was related to their hardware. I have one more board so I'll see if I can make that one work.

Kind regards,

Onur.

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

Vidar Berg — Fri, 30 Apr 2021 09:14:11 GMT

Hi Onur,

It's interesting that it works as soon as you revert the change. To verify it if the relagulator setting is indeed the culprit, maybe you can try to set it directly with nrfjprog?

e.g.

nrfjprog --memwr 0x10001304 --val 5

nrfjprog --reset

Another post with some similiar observations (still unresolved) https://devzone.nordicsemi.com/f/nordic-q-a/74471/ota-failing-when-gpio-high-voltage-mode-3-3-v

Kind regards,

Vidar

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

OnurGules — Fri, 30 Apr 2021 08:46:28 GMT

Hi Vidar,

I tried reverting the changes I made to flash_placement.xml, linker->memory segments and I also am not including uicr_config.h now in main.c. The device works normally now, although with incorrect voltage. So, it's probably the changes I made to uicr is messing up the bootloader.

I also debugged the bootloader project and dfu_enter_check() returns false as it should. You can find the debug logs I got below:

<debug> nrf_dfu_req_handler: Whole firmware image received. Postvalidating.
<debug> nrf_dfu_validation: Hash verification. start address: 0x27000, size: 0x20428
<debug> nrf_dfu_validation: Invalidating old application in bank 0.
<debug> nrf_dfu_settings: Writing settings...
<debug> nrf_dfu_settings: Erasing old settings at: 0x000FF000
<debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x000FF000, len=1 pages), queue usage: 1
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x000FF000, src=0x2000A6E4, len=896 bytes), queue usage: 2
<info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
<debug> nrf_dfu_settings: Writing settings...
<debug> nrf_dfu_settings: Erasing old settings at: 0x000FE000
<debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x000FE000, len=1 pages), queue usage: 3
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x000FE000, src=0x2000A364, len=896 bytes), queue usage: 4
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_flash: Flash erase success: addr=0x000FF000, pending 4
<debug> nrf_dfu_flash: Flash erase success: addr=0x000FE000, pending 2
<debug> nrf_dfu_flash: Flash write success: addr=0x000FE000, pending 1
<debug> nrf_dfu_req_handler: All flash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash ash

Edit: I debugged the bootloader by performing a DFU with the same app that normally works without DFU. I changed the debug logs from yesterday as I was debugging the bootloader incorrectly.

Kind Regards,

Onur Gules.

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

Vidar Berg — Thu, 29 Apr 2021 14:20:41 GMT

Hi Onur,

Thanks for testing. Is it possible that this may be unrelated to change you did to set the UICR regulator setting, or have you verified that it still works if you rever the change? Either way, I think you need to debug the bootloader project to find out why the bootloader will not start the application. First step may be to see if nrf_bootloader.c:dfu_enter_check() returns true instead of false which would make the bootloader fall back to DFU mode.

Kind regards,

Vidar

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

OnurGules — Thu, 29 Apr 2021 14:08:21 GMT

Hi Vidar,

Thanks for your answer. I tried flashing everything one by one with nrfjprog.

-Started with the bootloader first:

nrfjprog --program softdevice.hex --chiperase --verify

Parsing hex file.
Erasing user available code and UICR flash areas.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.

-Bootloader second:

nrfjprog --program bl.hex --sectorerase --verify
Parsing hex file.
Erasing page at address 0xF1000.
Erasing page at address 0xF2000.
Erasing page at address 0xF3000.
Erasing page at address 0xF4000.
Erasing page at address 0xF5000.
Erasing page at address 0xF6000.
Erasing page at address 0xF7000.
Erasing page at address 0xF8000.
Erasing page at address 0xF9000.
Erasing page at address 0xFA000.
Erasing page at address 0xFB000.
Erasing page at address 0xFC000.
WARNING: A UICR write operation has been requested but UICR has not been
WARNING: erased. Please verify that the result is correct.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.

-my app next:

nrfjprog --program app.hex --sectorerase --verify
Parsing hex file.
Erasing page at address 0x27000.
Erasing page at address 0x28000.
Erasing page at address 0x29000.
Erasing page at address 0x2A000.
Erasing page at address 0x2B000.
Erasing page at address 0x2C000.
Erasing page at address 0x2D000.
Erasing page at address 0x2E000.
Erasing page at address 0x2F000.
Erasing page at address 0x30000.
Erasing page at address 0x31000.
Erasing page at address 0x32000.
Erasing page at address 0x33000.
Erasing page at address 0x34000.
Erasing page at address 0x35000.
Erasing page at address 0x36000.
Erasing page at address 0x37000.
Erasing page at address 0x38000.
Erasing page at address 0x39000.
Erasing page at address 0x3A000.
Erasing page at address 0x3B000.
Erasing page at address 0x3C000.
Erasing page at address 0x3D000.
Erasing page at address 0x3E000.
Erasing page at address 0x3F000.
Erasing page at address 0x40000.
Erasing page at address 0x41000.
Erasing page at address 0x42000.
Erasing page at address 0x43000.
Erasing page at address 0x44000.
Erasing page at address 0x45000.
Erasing page at address 0x46000.
Erasing page at address 0x47000.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.

-And finally the settings:

nrfjprog --program settings.hex --sectorerase --verify
Parsing hex file.
Erasing page at address 0xFE000.
Erasing page at address 0xFF000.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.

I then reset the device with nrfjprog --reset, but the device is still stuck in bootloader.

Any thoughts?

Kind Regards,

Onur Gules

RE: Changing REGOUT0 value to 3v3 in a DFU enabled software

Vidar Berg — Thu, 29 Apr 2021 13:17:54 GMT

Hello,

It's not clear how data in the UICR could be impacting the settings page, it's not even in the same address range. As a test, and if you haven tried already, could you please try program the settings page after everything else has been programmed and see if it gives the same result? You can use the following command to just load the settings file: "nrfjprog --program settings.hex --sectorease"

Kind regards,

Vidar