Damon

Hi Damon,

If you device is showing up as a GPS Camera Detect (serial port), you need to force Windows to use the Atmel driver (in \Program Files\ATMEL Corporation\sam-ba_2.11\drv) instead.

Chris

This post provided the solution to my issue. I was using the older 2.10 (and 2.9) software pointed to in the wiki. I noticed in your post you were using 2.11. I registered, downloaded, replaced the driver and now have a fuctional Netduino w/4.2 mf on it. Thanks for all the help and a great product. I told my son the other day this device is engineering geek heaven. I also took the liberty of updating the wiki page but have left it in draft for so someone can verify if they are in agreement with the changes.

I would like to suggest an admin move this thread. I did not start it in the right place I don't think.

Hey!
I had some problems with this process as well. I even tried in linux without any luck.
What solved it for me was uninstalling the netduino drivers completely (actually removing them) and followed these steps: http://wiki.netduino...y-Netduino.ashx
windows automatically detected the netduino as a com port. the drivers they talk about on the wiki (in case it doesnt work) don't work however... windows 7 x64 tells me they're not compatible.
but yeah... I wonder why atmel doesn't bother making 64bit drivers...

I powered the n+ from usb for all of this.

I have tried removing the driver. Windows 7 Installs a new one from the update site each time I reinsert the device.

I have used both SAM-BA non CDC from AT91-ISP v1.13 and SAM-BA-CDC from sam-ba_2.9_cdc_xp_vista package.

This has also been tried on my work windows 7 pc and tested in XP mode (mapping the port to the virtual one of xp mode)

I have also tried this from an xp machine fresh install. The xp machine recognized the usb board as an amtel devel board. I went in and manually set it to a usb to serial emulator that was part of the same driver.

All of these tests result in the application loading and asking for port and cpu. I select them and the first window closes but I never see the second (main) window. The application is running in background. Sometimes it is consuming significant cpu but most times not.

I am at a loss since I have tried two boards, few oses and three pc's.

I would love to send a board to someone and ensure they can get the board flashed so I know it is a pc issue on my side. I would also appreciate any more feedback as to what to try.

I ordered another board concerned that I had 'bricked' this one. I followed the same procedure and achieved the same result (Please do not bring up the insanity definition). I am going to my clean xp installation and trying again. Any insight from anyone would be helpful.

I was upgrading to 4.2 and particulary following these instructions:
http://wiki.netduino....ashx?HL=sam,ba I cannot get any of the sam-ba programs to load correctly. It looks like I get driver loaded on the 2 windows 7 machines I have tried. I also have 'changed' the installed driver on an xp machine to a virtual com driver. However on all of these machines ,when I try to load sam-ba (tried both the vista and xp versions) asks for port and processor (which I set appropriately) and the application goes away. It is still loaded in memory but no ui every appears. My question is, is there a way to hack it back to like or is it a brick? The usb response makes me believe I should be able to fix it.

Thanks,
Damon

I was upgrading to 4.2 and particulary following these instructions: http://wiki.netduino....ashx?HL=sam,ba I cannot get any of the sam-ba programs to load correctly. It looks like I get driver loaded on the 2 windows 7 machines I have tried. I also have 'changed' the installed driver on an xp machine to a virtual com driver. However on all of these machines ,when I try to load sam-ba (tried both the vista and xp versions) asks for port and processor (which I set appropriately) and the application goes away. It is still loaded in memory but no ui every appears. My question is, is there a way to hack it back to like or is it a brick? The usb response makes me believe I should be able to fix it. Thanks, Damon