Hi all,
I just got my Advanced Development Kit in, and successfully spent a few hours emulating and testing a design I had worked on until I got it correct.
After exiting the program so I could commit my source files to version control, on each subsequent run I can no longer communicate / emulate / test the target device. Probing VDD and GND on the board, it doesn't seem to be powering up (stuck at 0V). I think I saw it pop up once or twice to 3.3V while unplugging / replugging in the USB cable but it never stuck around. I also no longer get the error message "Internal VDD and External VDD both disabled, etc. etc." which I got on the first runs.
I doubt the socket magically broke itself, and I tried a few different ICs... I have not tried restarting my machine yet. Is there some kind of software switch / manual cmdline flag I can use to get the dev kit "unstuck"? I see there is a VDD_EN line in the schematic for this board which seems to control how power is applied.
OK, I seemed to get it back by switching USB ports...but I noticed when I start Debug mode, I get the "device disconnected" sound from Windows and the white LED on the board turns off.
Test mode works sometimes, but emulation does not...and then vice versa. For lack of a better term, the board has now become "flaky".
Are you plugged into a USB hub? I was experiencing this same issue when the advanced development board was hooked up through a USB3.1 Hub. When I transferred the USB to a 3.1 port on the computer the issue went away.
Hi THere , i'll reach out to you on email and arrange for a replacement to be shipped out to you. BR JE_DIalog
Thanks for the super fast response! Replied to you in e-mail. Pending what we figure out may / may not be the root cause, happy to update this thread accordingly!
I don't think I've ever gotten a replacement this fast from any vendor — will give it a spin today. Thanks again for the amazing support John!
you're welcome ! good luck.