Make Build/Debug cyle with MCUXpresso more predictable.

[RobertK66]

This is somehow related to #7 but to put it more general:

The MCUXpressos debug cycle depends on a lot of settings and configuration for the used debug probe and sets up the link-server, detection and configuration of the CMSIS-DAP probe, the gnu gdb process and manages somehow to load the built image file to the target and start it with a set break point in main() ......

Working with earlier versions and now with my version of MCUXpresso IDE v11.1.1 [Build 3241] [2020-03-02] I repeatably experience following scenario:

The Terminate-Build-Debug button from quickstart menu works without problem (or doing everything with manual extra steps also works...) but after flash was loaded and main() break point reached - the following Run does not find all HW-Configs of the target chip (LPC1769 in my case) set up as expected. This is especially annoying when playing around with some basic configuration options (e.g. changing and assigning timer match registers and irq settings) because you can never be sure which (hw/gpio?-)configuration you really see while debugging!

The only consistent workaround to avoid such confusions I found until now is to manually RESET or power cycle the target board, which is both not very user friendly during development.

Any findings on that issue and settings to try out appreciated ....

[RobertK66]

Remark: This issues are much better handeled by a Segger Probe, but I did not use this one as long as the Dev-Boards or LPC2 Link2 probe....