Frequent "'Could not reconnect to the debugging target after rebooting it."

I’m getting the following about 20% of the time I attempt to deploy an application to the BrainPad (newer, small version) running TinyCLR 0.5.0, running the application under the debugger (with no breakpoints set).

Assemblies deployed. There are 122,184 bytes left in the deployment area.
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.’.

When I start to deploy, the BrainPad is happily running the previous version of the application (i.e., it’s not hung). And it stops running as usual when the deployment happens.

If I attempt to deploy again, it fails the same way (same sequence of messages in the Output window). If I press reset on the BrainPad, the next deployment (usually) will work.

Any thoughts on what might be causing this behavior, and how I could avoid it?


If you use Ctrl+F5 to deploy without debugging, can you deploy every time?

Correct. When I deploy without debugging, I never run into this issue.

There enough time to look into this before 0.6 but I think you should give it a try anyway to see if anything gotten better. It should be out this week.

Thanks. Will do.