DFU bootloader resets

RE: DFU bootloader resets

gaminn — Fri, 08 Feb 2019 22:07:28 GMT

I discovered the problem. I migrated your original GCC makefile to VisualGDB project and it seems some ASMFLAGS or CFLAGS or LDFLAGS were missing (even though bootloader's project basis is my app project which runs without any issue). Because I copied all these from your original makefile to my VisualGDB's makefile and it works now. I will now try figure out the specific flag that caused the problem. Thanks you.

RE: DFU bootloader resets

Hung Bui — Fri, 08 Feb 2019 15:50:21 GMT

Please try to have minimum modification and to test to update with one of our example application.

We need to find which assertion was thrown so please move the bootloader and enable debug mode. (and test with unmodified bootloader as well)

RE: DFU bootloader resets

gaminn — Fri, 08 Feb 2019 15:42:54 GMT

devzone.nordicsemi.com/.../7026.Bootloader.zip Here you can find my bootlaoder hex, elf, map and also application package that I'm trying to upload to my nrf52832 (MDBT42 module).

RE: DFU bootloader resets

gaminn — Fri, 08 Feb 2019 14:55:38 GMT

I use still the same image (my first post).

RE: DFU bootloader resets

gaminn — Fri, 08 Feb 2019 14:31:38 GMT

I use the bootloader on my custom board. Is that a problem? I defined BOARD_CUSTOM macro and in main.c I commented some lines that turn on/off leds. I also use internal RC oscillator ( defined in sdk_config.c) because my board doesn't have crystal.

RE: DFU bootloader resets

gaminn — Fri, 08 Feb 2019 14:27:48 GMT

I did that and defined preprocessor macro DEBUG. Nothing changed. Still the stack is corrupted.

RE: DFU bootloader resets

Hung Bui — Fri, 08 Feb 2019 13:55:26 GMT

Please move the bootloader down in the flash to give more space. Or you can use the debug variant of the bootloader to test.
Make sure you erased the flash completely before testing.

Which image did you use ? I have a step by step guide here that could be useful.

RE: DFU bootloader resets

gaminn — Fri, 08 Feb 2019 10:50:21 GMT

Hi, I deleted all modifications to bootloader. The same happens now - app_error_fault_handler is called with id = 0x1001, pc = 0x78f30, info = 0x40000000 . The call stack is 0x00024008, then app_error_fault_handler. I can't set optimization to 0 as bootloader then doesn't fit into FLASH (without modifying linker script).

RE: DFU bootloader resets

Hung Bui — Fri, 08 Feb 2019 10:10:41 GMT

Hi,

Please test again without any modification of the bootloader.

The pc location of 0x71EEE suggest that it's the issue inside the bootloader. Could you add DEBUG to the preprocessor symbol in project setting and set the optimization level to 0 ? This would make it stay in a loop when assert (fault) happens, and you should be able to see the line of code that's causing the issue. There is a debug guide here.

RE: DFU bootloader resets

gaminn — Thu, 07 Feb 2019 17:51:09 GMT

OK. I tried to perform DFU without the buttonless application. I modified the bootloader a little to support logging (the bootloader starts at 0x70000). I get this log output:

<info> app: Inside main
0> <info> app: No firmware to activate.
0> <info> nrf_bootloader_wdt: WDT is not enabled
0> <info> app: Entering DFU mode.
0> <info> nrf_dfu_validation: Signature required. Checking signature.
0> <info> nrf_dfu_validation: Calculating init packet hash (init packet len: 68)
0> <info> nrf_dfu_validation: Verify signature
0> <info> nrf_dfu_validation: Image verified
0> <error> app: Received a fault! id: 0x00001001, pc: 0x00071EEE, info: 0x40000000

Not sure whether the fault isn't caused by my bootloader upgrade to support logging. But the symptoms are same as previously - bootloader resets itself during update.

RE: DFU bootloader resets

Hung Bui — Mon, 04 Feb 2019 13:35:05 GMT

Hi,

Have you tested the bootloader to do DFU without using the buttonless application ?

Could you test the bootloader debug variant so we can have some more logging information from the bootloader ?

Have you made any modification to the bootloader ?

From your log, it doesn't seem the image has been transferred fully. Looks more like there was an issue when the init packet being transferred.