nanoframework
RTM builds should have option to stay in bootloader mode if no application present
Description
Currently, with RTM mode CLR if we do not have application flashed or I assume if it is invalid (is there a checksum?) the MCU will enter a continuous reboot cycle. We prefer that it instead acts more like a Debug release and just stay in bootloader mode and stop. Then we can re-flash via USB and do not require J-Link. We also then see the same behavior Debug or RTM CLR, making internal development and support easier.
How to solve the problem
Provide RTM CLR build option to stay in bootloader mode if missing or corrupt application. Generally systems such as this will then have a flag that indicates "why" CLR boot was not possible, and this is optional and could be done as follow-on work. For example, I imagine there might be three reasons for no CLR boot: BL pin asserted, no application, or application checksum fail.
Describe alternatives you've considered
No response
Aditional context
No response
