Custom board will not boot without Jlink debugger attached

[jrhaws]

I have been tracking this problem in this private ticket as well ((Missing Ticket)) since I thought the issues were related. I figured I should split it out since it appears that they may not be related after all.

I'm having issues getting my custom board with an NRF52832 to boot on power up. I can only get it to boot properly if I attach my Jlink debugger. I have searched high and low for answers to this problem to no avail. I've looked at all the following tickets:

 Zephyr project on a custom board wont' start up after removing debugger 

 nRF52832 application won't start without RTT console 

 Interesting Issue with board configuration - application wont start unless "kickstarted" by RTT or debugger. 

And even a few more that I can't find the links for again.

I've verified that my HFXO is good and my LFXO also looks good. I've also included the MCUboot bootloader, and it still will not start on boot. Only when I select "Attach debugger to Target" in VS Code does it decide it wants to start the application.

My same application and project configuration runs just fine on the NRF52 DK with an NRF52832, so I hesitate to think it is just a configuration thing.

What am I missing?

Thanks!

Jon

[Simonr]

Hi

As far as we can tell, the partitions seem to be set correctly, but the MCUBoot partition is set to a different size than in our standard. I will forward this case to one of my colleagues more experienced with the MCUBoot than me, as I'll need to get a second opinion on what could cause this. Thank you for your patience! 

Best regards,

Simon