Having issues with G400D / TH

App deploying fine but issue with debugger. I don’t have this issue with FEZ Cobra III and G120TH

This is what I have in output window:

Looking for a device on transport ‘USB’
Found device port ‘USB’ with ID ‘e5482d3f-b502-48c2-9be8-31ece2666613’ for transport ‘Usb’
Starting device deployment…
Attempting to connect to device ‘USB:G400’ Iteration 0
Opening port \?\usb#vid_1b9f&pid_0102#0000000001#{d32d1d64-963d-463e-874a-8ec8c8082cbf}
Attaching debugger engine…
… debugger engine attached!
Querying device assemblies…
Found Assembly mscorlib 4.3.1.0


Adding pe file C:\Program Files (x86)\Microsoft .NET Gadgeteer\Core\Assemblies.NET Micro Framework 4.3\le\gadgeteer.pe to deployment bundle


Attempting deployment…
Incrementally deploying assemblies to device
Deploying assemblies for a total size of 407744 bytes
Assemblies successfully deployed to device.
Restarting interpreter…
Attaching to device…
Waiting for device to initialize…
The debugging target and the debugger engine failed to initialize because of unspecified device errors.
The debugger engine thread has terminated unexpectedly with error ‘Could not reconnect to the debugging target after rebooting it.’.


EDIT:
Installed VS2013 and reinstalled framework problem went away. Still strange why it worked for Cobra III and G120TH modules

In my experience, you can’t reliably debug the G400-based systems with VS2015. The problem seems to be in a change made to the debugging framework in VS2015. It times out too rapidly. It may be the case that it works fine if you install just the 4.3 sdk, but if you install the 4.4 sdk, It definitely does not work. Anyway, that’s my experience. I use VS2015 for virtually all my work (with appropriate patches to get the pre-Roslyn compiler), but for working with G400, I use VS2013 (the only officially supported config for any GHI board).

Yes, I know VS2015 is not supported, I completely switched to VS2013 for NETMF projects.

@ EvoMotors - ok - when you said ‘installed vs2013’ I wasn’t sure whether that was a re-install or that you were switching from 2015.