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

uart is not work after bootloader/dfu enabled

Hi,

I am using sdk15.3 for a project, the uart works fine when programmed without bootloader, but just after add bootloader, the uart is not worked now, also the rtt log is disappeared,(it is ok without bootloader) for it can't use jlink to debug the program, I dont know what is happening?

brian

Parents
  • Hello,

    Have you tried debugging your application with the bootloader? What IDE do you use? Since you haven't mentioned any, I'll show you how to do this in SES, since it is quite commonly used:

    Click "Target" -> "Attach Debugger" from the toolbar menu. This will just attach the debugger, without uploading any new firmware based on your project. Even if you have generated the dfu image or bootloader settings from the hex file generated from this project, the IDE will not use this exact hex file to debug, so if you start a debug session the normal way from your IDE, it will corrupt the CRC value of the application, causing the bootloader to not accept the application that is programmed, and it will remain in DFU mode.

    Do you get any indications on whether the nRF is in DFU mode or in the application when the issue occurs? If you try to attach the debugger as I described above, and put a breakpoint close to the top of your main() function, is it hit?

    What HW are you using? DK or custom PCB?

    What IDE do you use?

Reply
  • Hello,

    Have you tried debugging your application with the bootloader? What IDE do you use? Since you haven't mentioned any, I'll show you how to do this in SES, since it is quite commonly used:

    Click "Target" -> "Attach Debugger" from the toolbar menu. This will just attach the debugger, without uploading any new firmware based on your project. Even if you have generated the dfu image or bootloader settings from the hex file generated from this project, the IDE will not use this exact hex file to debug, so if you start a debug session the normal way from your IDE, it will corrupt the CRC value of the application, causing the bootloader to not accept the application that is programmed, and it will remain in DFU mode.

    Do you get any indications on whether the nRF is in DFU mode or in the application when the issue occurs? If you try to attach the debugger as I described above, and put a breakpoint close to the top of your main() function, is it hit?

    What HW are you using? DK or custom PCB?

    What IDE do you use?

Children
No Data
Related