> On 27 Jul 2025, at 21:45, Antonio Borneo <borneo.anto...@gmail.com> wrote:
>
> Well, I often see developers using semihosting during development to
> simply get a console output before the HW UART drivers are ready, or
> on projects where there is no UART available.
in my opinion using a HW UART to output trace messages is not exactly an
elegant solution, better leave it via semihosting.
> This is one of the cases where exit() is not welcome.
in most of these cases the application is not structured as a standalone unit
test, i.e. it does not necessarily have a proper main(argc, argv), and even if
it has a simplified one, it does not actually return, therefore semihosting
EXIT is not called.
> So something similar to the command I proposed
> `arm semihosting_on_exit [halt|resume|exit]`
> should work for everyone.
can you define the behaviour of these 3 cases if all ports (gdb/tcl/telnet) are
disabled? (like in the use case I mentioned in the previous message)
Liviu
