forked from qt-creator/qt-creator
... instead of device page. Reason is that a path to the peripheral description file comes from the inside of the provider for some providers (e.g. for the UVSC provider at parsing the selected "Software Device Pack" file). This complicates a code for assigning of the selected peripheral description file path to the device configuration page. So, it is makes sense to make it possible to choose a peripheral description file from the debug server provider page. In this case we will pass a path to the selected peripheral description file via the runnable's extra data variable. Tested with STM32 NUCLEO-F767ZI board on Windows. Change-Id: Iec4d738dd236449969fd669e7fbe58da3a660938 Reviewed-by: hjk <hjk@qt.io>