I've encountered an error that means i can't run on-target debugging. After (successfully) deploying my program to the nd3 wifi the device reboots 11 times then the debugger terminates, the nd3 then runs the program successfully. As a work around i tried 'attach to process' in Visual Studio but although it displays debug messages in the output window breakpoints in active threads never get 'hit' (appear disabled).
i have tried different usb ports, even cables etc but cant find a solution. Some other posts described 'cyclic rebooting' and similar issues e.g. by kerk-akker, Feb 24 2016 10:49 PM but those suggestions wont resolve this.
Watching the board leds i see that after the deployment of assemblies completes the board doesn't seem able to initialise the network (at lease im guessing that is a possible scenario). The network led lights orange for a few seconds and goes off, then the blue led illuminates for a few seconds then that cycle repeats 6 times before the debugger exits. Then the board loads the program and network immediately becomes active (network led shows green).
i have tried both setting dynamic and static IP, but it has no effect on the outcome. i am using the 'wait for network availability' code presented at http://forums.netdui...ork-connection/ The test program is a bare bones program - just runs the wait for network then prints 'thread alive' message and sends a network message to a REST endpoint in a loop with a sleep.as mentioned the program works as expected but cant run the debugger.
Any comments appreciated.
Is there any way to identify the 'unspecified device errors' (as shown in the output - below). Are there any time-outs of other parameters to experiment with with debugger / target boot loader, or log view?
below is the output up to the first target reboot
....... [deployment description text (no errors)]
- GarthSella likes this