This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Jumping from DFU to Application problem after buttonless dfu - Segger Embedded Studio - sdk10 - s110

Hi,

I have tho following configuration: SDK 10, S110 and I'm using Segger Embedded Studio, single banker dfu.

I am able to program DFU and buttonless DFU; However, when the bootloader jumps to the application the GPIO seems to freeze. When I perform the first transfer everything works fine and the application starts, but after the second application transfer (now using buttonless dfu) the application freezes at initialization time, if I reset the chip the firmware works. I am transferring the same application and it works when no application was programmed on the chip (the motor vibrates two times - working) after transfer the same firmware again the initialization freezes and the motor vibrates continuously until I reset the chip (After reset, everything works).

I don't know if the problem is on the SES configuration. The memory location seems to be right as it starts, but with a weird behavior.

Help me please....

Parents
  • Hi,

    1. Have you debugged your application? It sounds like your application asserts (and enters an endless while loop in app_error_handler() in app_error.c ) when exiting the bootloader and entering your application. 
    2. Do you have any sort of UART or RTT logging information printed to a serial terminal?
    3. Are you using unmodified examples from the SDK?
Reply
  • Hi,

    1. Have you debugged your application? It sounds like your application asserts (and enters an endless while loop in app_error_handler() in app_error.c ) when exiting the bootloader and entering your application. 
    2. Do you have any sort of UART or RTT logging information printed to a serial terminal?
    3. Are you using unmodified examples from the SDK?
Children
No Data
Related