stoj

Is 'attach to running process' supported on visual studio 2013 with a N2 running 4.3.1?

As per attached image, using the USB transport I receive the following error..

Invalid address 0 and range 40 Ram Start 20000000, Ram end 20020000

Is there a v4.3 version of mfdeploy that supports selecting the transport?  i.e. to allow the debugging transport to be changed from USB to serial.

I've been using the custom v4.1 version of mfdeploy ( set the transport to serial.  Is this a 'safe' solution?  i.e. will it cause any memory/config corruption issues?

Is serial port debugging supported using VS2013 on the N2 running v4.3.1?

As per attached image, it partially works.  The .net framework assembly versions are checked and my code is deployed, but VS hangs on the line.. "waiting for device to initalize..".

it looks like VS is having problems restarting the N2.  If I manually restart the N2 by shorting the 'RESET' pin to 'GND' a few times (often takes 3-4 attempts), then VS detects the CLR has restarted and debugging then starts to work over serial.

Has anyone else experienced the same problem?