Hello,
I followed the following guide for creating a modified Blinky example app that boots from the mcuboot. I attempted to flash both the merged.hex and zephyr.elf to a custom board with the nrf5340 processor.
The sample should just toggle the following pins high (P0.20, P0.23, P0.24) every second to test an LED and some test points on the custom board.
The program compiles and appears to flash to my board when using the following methods:
Using 3rd Party J-Link Programmer:
Programmer: J-Link EDU Mini
Software: J-Flash Lite
Output using West Flash :
-- west flash: rebuilding
[0/4] Performing build step for 'mcuboot_subimage'
ninja: no work to do.
-- west flash: using runner nrfjprog
Using board 1050041106
-- runners.nrfjprog: Flashing file: C:\ncs\v1.8.0\zephyr\samples\basic\blinky\build\zephyr\merged.hex
Parsing image file.
Applying system reset.
Verified OK.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050041106 flashed successfully.
nrf5340DK board Modified for Debug out (soldering SB47 Pad) Flashed Using SES Debug Console:
- Program builds and I am able to flash the device through debug but again nothing is appearing when probing the oscillator with my logic analyzer.
- The debugger does not enter the main program, it hangs in cpu idle unable to detect the clock.
None of the pins are being driven high when attempting to measure them with a logic analyzer, and when I attempt to prob the oscillator, I dont see a clock pulse. This to me indicates that the bootloader is being flashed onto the board but there is perhaps an issue in software. Maybe I am missing something that was not in the guide?
Attached is a copy of the mcuboot + blinky program I developed.
Any help would be appreciated.
Thanks,
Matt
