FEZ Cerberus - The debugging target is not in an initialized state; rebooting

I’ve a GHI Fez Cerberus and I’ve created my first Visual studio Gadgeteer project with Micro Framework .Net. Compilation and deploy are ok and I can ping it with MFDeploy (Pinging… TinyCLR).

Running project gets me this error:

“The debugging target is not in an initialized state; rebooting…”

Firmware updated following instructions in this post:

http://www.tinyclr.com/forum/topic?id=8938&page=1

resetted the board but nothing has changed!

@ danyolgiax - Welcome.

If you have tried all the usual suspects like different USB cables and ports then try plugging your Cerb into an external powered USB hub.
Some machines with USB 3 cause issues and plugging into a USB 2 hubs fixes this.
If your have VMWare installed try turning off the VMware USB Arbitration Service

[ul]USB port is 2.0
USB Cable has been changed
VMware USB Arbitration Service has been stopped[/ul]

Nothing ha s changed again!

I can add that in VS output panel I can read:

Error: a3000000

Waiting for debug commands…

The program ‘[2] Micro Framework application: Managed’ has exited with code 0 (0x0).

That looks like an project error.
Are you running a 4.2 project?
If you are can you humor me and remove the Gadgeteer reference and readd it and see if that fixes it.

a3000000 means there is a conflict between the firmware version of your project and the version on the device.

update your firmware.

Justin pointed me to the right direction!

I started a 4.2 project but Gadgeteer reference point at 4.1!!!

Removed 4.1 and added 4.2 did the trick!

Thanks!

@ danyolgiax - good stuff :slight_smile: