Bootloader hangs after sending filesize

[KingKarl237]

I have a problem with the new SDK11 Bootloader. With SDK 0.9.2. everything worked fine, but with SDK11 not. The strangest thing is that if i use the precompiled hex file in /dfu/bootloader/hex it works. Compiling the program without any change it did not work. What i'm doing is connecting to the bootloader and sending 0x0104 (Start DFU) ,Till now no problem. Next step is sending the filesize of the new Application. After that the bootloader hangs. Debugging the bootloader shows that i goes to start_data_process() in dfu_transport_ble.c. This function starts with:

  uint32_t err_code;

    dfu_start_packet_t  start_packet  = {.dfu_update_mode = m_update_mode};
    dfu_update_packet_t update_packet =
    {
        .packet_type         = START_PACKET,
        .params.start_packet = &start_packet
    };

After that he s gone. If i stop, Dissassembly shows SEV all the time.

Please can you help me? What is the difference between the precompiled and the source-files?

[bjorn-spockeli]

I am assuming that you're not using our apps, but initiating DFU manually by writting to the DFU characteristics. Are you debugging the bootloader with optimatization level 0, as described in this post?

[KingKarl237]

I have build a own program for initiating DFU and it worked good with SDK0.9.2 . But with the new Bootloader i have also tried it with the Master Control Panel App for Android. Same behaviour here. I haven't done something at the debugging options. I will take a look at this.

[KingKarl237]

I have noticed now, that it worked on the Development-Kit. So there is a problem with my board ( which didn't happened with SDK0.9.2)

[FormerMember]

@KingKarl237 Please let us know what the problem was if you solve this.

[bjorn-spockeli]

So DFU with the Bootloader from SDK v11.0.0 worked properly on your nRF52 DK, but not on your custom board?