Dec 13, 2020
01:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 13, 2020
01:29 AM
Error creating session
The debug instrument IO could not be initialized.
The GDI debug instrument provided the following error message.
An internal error occurred in the debug instrument (gdi2mcdtc.dll).
The debug instrument IO could not be initialized.
The GDI debug instrument provided the following error message.
An internal error occurred in the debug instrument (gdi2mcdtc.dll).
- Tags:
- IFX
- mini wiggler
- tc264
3 Replies
Dec 16, 2020
03:59 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 16, 2020
03:59 AM
Hi,
this message is typically shown when there is a problem in the communication with the hardware.
You can try to connect to the board using he "MCD Basic Client", which is a software provided by the DAS installation:
- Start Menu -> MCD Basic Client
- If the board is correctly connected and recognized, the "MCD Core Select" window should show you all available cores in the device, for example:
- Select a core and check you can control it (for example pressing "Stop" and "Run". It should switch from state "Running" to state "Debug")
If you are not able to perform this operations, the problem must be searched in the connection with the hardware.
The following can be checked:
- Try different USB ports, preferably ports which do not share the USB bus with other hardware like headsets, mouse, keyboards, etc, to exclude a conflict with the latter
- If possible, try with different boards to see if the problem affects them all.
- Check the USB cable and the usb connector
- Try with a shorter cable
- Try to power the board with external power supply
If you are able to connect and control the board with "MCD Basic Client", but the error still persists when trying to launch a debug configuration, please let us know.
Kind regards
this message is typically shown when there is a problem in the communication with the hardware.
You can try to connect to the board using he "MCD Basic Client", which is a software provided by the DAS installation:
- Start Menu -> MCD Basic Client
- If the board is correctly connected and recognized, the "MCD Core Select" window should show you all available cores in the device, for example:
- Select a core and check you can control it (for example pressing "Stop" and "Run". It should switch from state "Running" to state "Debug")
If you are not able to perform this operations, the problem must be searched in the connection with the hardware.
The following can be checked:
- Try different USB ports, preferably ports which do not share the USB bus with other hardware like headsets, mouse, keyboards, etc, to exclude a conflict with the latter
- If possible, try with different boards to see if the problem affects them all.
- Check the USB cable and the usb connector
- Try with a shorter cable
- Try to power the board with external power supply
If you are able to connect and control the board with "MCD Basic Client", but the error still persists when trying to launch a debug configuration, please let us know.
Kind regards
Dec 16, 2020
10:54 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 16, 2020
10:54 PM
Why is the DAS driver software often unresponsive?"DAS Errors DASHPAS"
Dec 16, 2020
10:58 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dec 16, 2020
10:58 PM
enrico.bragante wrote:According to what you said, it is wrong to use MCD Basic Client to connect "Could not start Server".
Hi,
this message is typically shown when there is a problem in the communication with the hardware.
You can try to connect to the board using he "MCD Basic Client", which is a software provided by the DAS installation:
- Start Menu -> MCD Basic Client
- If the board is correctly connected and recognized, the "MCD Core Select" window should show you all available cores in the device, for example:
- Select a core and check you can control it (for example pressing "Stop" and "Run". It should switch from state "Running" to state "Debug")
If you are not able to perform this operations, the problem must be searched in the connection with the hardware.
The following can be checked:
- Try different USB ports, preferably ports which do not share the USB bus with other hardware like headsets, mouse, keyboards, etc, to exclude a conflict with the latter
- If possible, try with different boards to see if the problem affects them all.
- Check the USB cable and the usb connector
- Try with a shorter cable
- Try to power the board with external power supply
If you are able to connect and control the board with "MCD Basic Client", but the error still persists when trying to launch a debug configuration, please let us know.
Kind regards