MCUXpresso IDE: Debug Probe Selection Dialog (Probe Discovery)

Document created by Robin_Shen Employee on Sep 28, 2017Last modified by Robin_Shen Employee on Sep 28, 2017
Version 2Show Document
  • View in full screen mode

This tip will show you how to re-trigger a full probe discovery.  The feature is very useful for the customer who may use multiple debug probes.



The first time you debug a project, MCUXpresso IDE will perform a probe discovery operation and display the discovered Debug Probes for selection. This will show all Supported Probes that are attached to your computer. (Here you can see the default P&E Micro OpenSDA of FRDM-KL25Z board was found.)


For any future debug sessions, the stored probe selection will be automatically used to match the project being debugged with the previously used debug probe. This greatly simplifies the case where multiple debug probes are being used.


However, if a debug operation is performed and the previously remembered debug probe cannot be found, then a debug probe discovery operation will be performed from within the same family e.g. MCUXpresso IDE LinkServer, P&E Micro or SEGGER J-Link. (Here you can see there are two Probe search options: Search for PEMicroDBB97E74 again and Search for other attached PE Micro probes.)


But if you want to use a different debug probe(for example: debug FRDM-KL25Z board with SEGGER JLink), click thisblue debug icon will meet problem. Supported Probes dialog only show P&E Micro probes, it will not search other family of debug probes e.g. MCUXpresso IDE LinkServer or SEGGER J-Link.


Once a launch configuration file has been created, it will be used for the projects future debug operations. If you wish to use the project with a different debug probe, then simply delete the existing launch configuration and allow a new one to be automatically used on the next debug operation.


Now click blue debug icon re-trigger a full probe discovery, and it show all Supported Probes that are attached to your computer again.