Blinky w/ JLink Unable to Find Bootable Image

[zachwork]

I recently got my Segger JLink Ultra+ working with the nRF tool suite but after programming my Thingy:53 dev board once it no longer boots correctly. Prior to using the JLink I was using the DFU programming over USB without issue but the need for real time debugging pushed me to the JLink approach.

Currently I've gone back to the blinky application under the Zephyr samples in the SDK folder. I'm using SDK v.2.4.0 and am able to build the blinky application for the thingy53_nrf5340_cpuapp_ns without issue. The problem comes after I flash or debug.

The code bootloader code apears to hit this section and fail:

    if (FIH_NOT_EQ(fih_rc, FIH_SUCCESS)) {
        BOOT_LOG_ERR("Unable to find bootable image");

        mcuboot_status_change(MCUBOOT_STATUS_NO_BOOTABLE_IMAGE_FOUND);

#ifdef CONFIG_BOOT_SERIAL_NO_APPLICATION
        /* No bootable image and configuration set to remain in serial
         * recovery mode
         */
        boot_serial_enter();
#endif

        FIH_PANIC;
    }

The above code is from the file "C:\ncs\v2.4.0\bootloader\mcuboot\boot\zephyr\main.c"

When the system hits this conditional fih_rc = 357913941

From stepping through the code it looks like the "context_boot_go" panics because the boot_swap_type somehow ends up being BOOT_SWAP_TYPE_PANIC. This seems to occur in the file "C:\ncs\v2.4.0\bootloader\mcuboot\boot\bootutil\src\loader.c" around line 2234

What could be causing the bootloader to not find the blinky image? Is there something I need to erase or clear or reprogram? I'm stuck and this is really stalling out progress on my project.

[Menon]

Hello,

 I tried to reproduce your issue by trying two samples, basic blinky and a BLE (zephyr beacon) sample from the nRF connect SDK V2.4.0. For me it's working fine. I flashed both the samples using a JTAG cable and nRF5340dk as an external debugger.

 Peter.J  I am not sure whether the issue you are seeing is similar to this because you are working with a custom nRF52840 device and a custom Application. I recommend you to share the error logs for getting better idea on the issue. But please follow your thread as it is independent to each other.

Kind Regards,

Abhijith

[zachwork]

I tried flashing the "peripheral LBS" example code from the nRF SDK v2.4.0 from the precomipled binaries and I still get the same error. I even switched to a brand new nRF5340DK as my external programmer.

I'm not sure why you aren't seeing this issue. I've been able to recreate the problem across both Windows and Mac OS host systems using multiple Thingy53 dev boards and a variety of external programmers both a seggar JLink Ultra and nRF5340DK. I've tried programming via VSCode with the nRF Extension, the nRF Connect Programmer and the command line tools. All result in the same behavior.

Do you have any suggestions for further debug or log information I could collect that would help root cause this issue?