Environment:
sdk: NCS 2.7.0,
tool: vscode nrf connect
board: my self board (same with official hardware reference: nRF52832-CIAA Reference Layout 1_0, nrf52832_ciaa_2-layer.PrjPCB ), just a mini system with only chip nrf52832, without dc-dc.
config: official nrf52dk/nrf52832, no overlay file, system build
Bug description: I create a my self project from vscode nrf connect with copy the blinky sample mode. The project can work in debug mode. I can control the led blink. But do not work in flash mode.
Question:
1: what's kind of reason could be? such as the bootloader or soft device firmware do not programming into flash. or programming into flash space incorrect? Or other reason cause to..
2: How can i confirm that whether it is bootloader or soft device issue?
3: I do not understand the composition of build output file (zephyr.efl), whether just programming this one file to flash is enough in any case (for nrf52832 single core chip)?
zephyr.elf = soft device + bootloader + application (blinky) ?
is soft device option, just for BLE case ?
is bootloader necessary for any case ?
could only program application to someone flash address, can work ? i guess if only programming application (for blinky) to some RAM address is ok.
where can i got the bootloader and soft device files?
a, These file will generate each time i build the blinky project?
b, bootloader build from the MCUBOOT project?
c, how to get the soft device files adapt to my board and chip in NCS + vscode nrf connect environment?