• State Verified Answer
  • Replies 9 replies
  • Subscribers 62 subscribers
  • Views 4346 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 121427
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Help with restarting, debugging and size-limitations for DFU procedure needed

Ray Breslin

Hello,

while I already managed to solve a couple of problems regarding a proper handling of the DFU procedure in my previous topic here, there are still 3 problems that remain where I could use some help...

  1. How can I trigger a 'hard-reset' within the Nordic SDK, that behaves like using the on-/off-switch on the nRF52832 dev-board? Apparently a mere 'soft-reset' - f.ex. after a watchdog-timeout - isnt enough to get a restart in application-mode, when successfully completing the DFU procedure!

  2. How can I enable the debugging for the bootloader_secure-example, when using a gcc-toolchain? Basically something like this here, but just for a direct handling on cmd-line-basis with gcc and SDK v12.2.0! Has anyone done that before?

  3. Apparently I can only complete the DFU procedure for a pkg-file, that just includes my application (f.ex. buttonless_dfu-example), but not for a pkg-file which includes the bootloader and the softdevice due to a 'REMOTE DFU DATA SIZE EXCEEDS LIMIT'-error, even though this file is smaller then the test-files given within the dfu_send_hex-example!

I would very much appreciate any help on those issues!

Kind regards

Parents
  • 0

    Q1: Sorry, I though you meant flashing the SoftDevice and bootloader and application test hex files. If you reset after that you will stay in bootloader mode. You are referring to the reset after an application OTA DFU has been performed right?

    Q3: I think I spotted the error: You are creating a bootloader image using the merged bootloader+settings file, created using the following command

    mergehex -m secure_dfu.hex secure_dfu_settings.hex -o secure_dfu_merged.hex

    The settings file should only be merged with the bootloader hex when you're flashing the SoftDevice, Bootloader and the application using a programmer. The settings file must be omitted when you create OTA DFU images.

Reply
  • 0

    Q1: Sorry, I though you meant flashing the SoftDevice and bootloader and application test hex files. If you reset after that you will stay in bootloader mode. You are referring to the reset after an application OTA DFU has been performed right?

    Q3: I think I spotted the error: You are creating a bootloader image using the merged bootloader+settings file, created using the following command

    mergehex -m secure_dfu.hex secure_dfu_settings.hex -o secure_dfu_merged.hex

    The settings file should only be merged with the bootloader hex when you're flashing the SoftDevice, Bootloader and the application using a programmer. The settings file must be omitted when you create OTA DFU images.

Children
Related