Timer Prescaler - SDK Config

[Shreyas Shivalkar]

I am using nrf52832 with softdevice s132 v3.0.0, sdk 12.2.0 and FDS.

I am using sdk_config.h to configure various modules in my project.

Earlier config: Using Timer1, Timer2 with TIMER_DEFAULT_CONFIG_FREQUENCY = 4 Timer1 = controls main state machine Timer2 = controls LED behavior Then I changed the TIMER_DEFAULT_CONFIG_FREQUENCY = 1.

If I program the board with new configuration through JTAG, I can observe the changes in behavior but if I try via DFU, the changes are not reflected.

Any insights will be helpful. Thanks in advance.

[Bjørn Kvaale]

You will need to use Secure DFU to update this. There's a great blog post which explains the process well here.

[Shreyas Shivalkar]

I used 'bootloader_secure' example from the sdk12.20 \nRF5_SDK_12.2.0_f012efa\examples\dfu\bootloader_secure.

[Bjørn Kvaale]

Has the issue been fixed now? Or does it still not work?

[Shreyas Shivalkar]

I was using the Secure Bootloader Example from the beginning.

The issue occurs when the TIMER_DEFAULT_CONFIG_FREQUENCY value is update over the air via DFU. If I erase and reprogram the dev board with new value. It works just fine i.e the change in behavior is reflected.

The issue has not been resolved.

[Bjørn Kvaale]

Got some tips from a dfu expert at Nordic:

Option 1: Would you mind testing on a blank chip using only the softdevice & the bootloader? Then, try updating the new firmware. Finally, you can check if the DFU was successful or not (i.e. see step D4 in the Secure DFU blogpost).

Option 2: Using nrfjprog, you can type in this in a command prompt on windows: nrfjprog.exe --readcode . This command reads the hex file output. You can then read the output file using Notepad++ for example and compare the output before the DFU and after the DFU.

Most likely, the DFU was not successful & that is why your changes in TIMER_DEFAULT_CONFIG_FREQUENCY were not updated.