I'm having the same issue. Flashed my N+2 to 4.22 and now anytime I run the app through the debugger, I get the 'target is not in an initialized state, rebooting" and that's it. The process no longer is running in the debugger.
I'm running VS2010.
NP2 reboots on deploy; never debugs/runs app
Started by
jmorrisosu
, Feb 24 2013 04:27 PM
23 replies to this topic
#22
EricO
-
- Members
-
- 17 posts
Member
- LocationLas Vegas
Posted 11 March 2013 - 10:47 PM
I was able to get past the 'target is not in an initialized state...." problem when using 4.2 and VS2010 by upgrading to VS2012 and using 4.3 of the MF and sdk.
#23
CaseSensitive
-
- Members
-
- 1 posts
New Member
Posted 12 May 2013 - 02:29 AM
I've been working to resolve the same problem when I realized that it only happened when using the USB 3 ports on my laptop.
The USB 2 ports work fine.
In both cases the 4.2.0 driver was loaded, but I couldn't debug using the USB 3 ports.
Dennis
#24
Chris Walker
-
- Moderators
-
- 7767 posts
Secret Labs Staff
- LocationNew York, NY
Posted 01 July 2013 - 11:02 PM
Hi Dennis,
Thank you,
Chris
Which board are you using (gen1 or gen2)? Which drivers are you using? We're working on upgrading the gen2 boards to use the WinUSB drivers--but we want to make sure that there are no USB 3.0 gremlins firstI've been working to resolve the same problem when I realized that it only happened when using the USB 3 ports on my laptop. The USB 2 ports work fine. In both cases the 4.2.0 driver was loaded, but I couldn't debug using the USB 3 ports.
Thank you,
Chris
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
