13 replies to this topic

[georgejh]

Hi Chris, I have now tried 5 times going through the full procedure of uninstalling .NET MF 4.1, installing 4.2, SDK, wiping off Netduino Plus, installing Tiny Bootloader, uploading the firmware, etc. All that goes fine. Then trouble begins. Cannot deploy any program. VS simply hangs on deploying. I have tried all known methods from forum of handling this situation - no success at all Any ideas? I'm using it from VMware Windows 7 vm with VS2010 Ultimate. Never had any such issues.

[Chris Walker]

Hi georgejh,

I have now tried 5 times going through the full procedure of uninstalling .NET MF 4.1, installing 4.2, SDK, wiping off Netduino Plus, installing Tiny Bootloader, uploading the firmware, etc.
All that goes fine.

Then trouble begins. Cannot deploy any program. VS simply hangs on deploying. I have tried all known methods from forum of handling this situation - no success at all

Any ideas?

I'm using it from VMware Windows 7 vm with VS2010 Ultimate. Never had any such issues.

After you flashed your Netduino Plus, did you disconnect and reconnect it from your PC? Can you ping it from MFDeploy?

In Visual Studio, when you go to your Project Properties, .NET Micro Framework tab...do you see the device under the "USB" transport? If so, please switch to Serial and then back to USB to make sure that the selection is saved.

If you can give us more info on what you're experiencing, we can help diagnose the situation.

Sorry that you're having troubles; let's see what we can do to get you up and running.

Chris

P.S. We haven't tested the WinUSB drivers with virtual machines yet. If there is an incompatibility between the WinUSB drivers when used in VMs, we can walk you through switching back to the old MFUSB (SpotUSB) drivers.

[georgejh]

The answer of all questions is: yes. There is a new development on the case. I've left the deployment in this "hanged" state and had my dinner. Coming back, approx 15 minutes later, I have found the deployment done! So it seems it takes ages to deploy but at least it finishes at some point. I'll do more experiments to observe the behaviour and will post an update info later today or tomorrow. Cheers

[georgejh]

Hi Chris, Must be VM related issue, have no speed problems when deploying within host environment.

[nakchak]

Hi Georgejh How have you set up the USB pass through to your VM? I have had issues in the past with VM's (HyperV, VMware, VirtualBox etc.) and usb sharing when i have inadvertently tried to use USB sockets that are actually hub connections, i.e. case mounted USB sockets tend to be integrated usb hub ports on the mother board, whilst the USB sockets on the back of the Mother board tend to be controller ports (this is also the reason my phone charges quicker from sockets on my mobo, than on my case...) Nak.

[GregR]

I currently run Windows 7 Ultimate 64-bit under VMWare Fusion on a Mac with Visual Studio 2010 Ultimate. I have not had any major issues with deploying apps. Every now and then it will hang and I cancel the deployment, unplug/replug the Netduino Plus and then everything goes fine. I will also add that my Netduino Plus is connected via a USB hub to my Mac. Greg

[AxelG]

I use Windows 7 Ultimate hosted on a local VM through VMWare Player as my dev environment and had the same issue until I re-flashed my Netduino BIOS. There was an issue with the earlier version of SAM-BA 2.11 that had a problem with slow deployments that may be related to this. Using the new 2.12 version of SAM-BA and flashing the latest 4.2 firmware solved the problem for me. (I do, however, still get BSOD if I hit the reset button on the ND during deployment)

[Chris Walker]

Hi AxelG,

(I do, however, still get BSOD if I hit the reset button on the ND during deployment)

Are you getting a BSOD inside the VM or on the actual computer?

Could you check something for me really quickly?
1. Open up Device Manager. Under USB, you'll see Netduino.
2. Right-click, select Properties.
3. Switch to the Details tab
4. Pull down the properties drop-down, select "Service"

What value do you see there?

Also, what are the VID/PID of your Netduino (from the same Details tab)?

Chris

[AxelG]

The BSOD is in the VM. My host is fine. The Service reads "WinUsb" and the Hardware ID is "USB\VID_22B1&PID_1001&REV_0100"

[georgejh]

Here some update on the issue and on few of the suggestions: 1. I'm using a laptop, so no USB on the back of the motherboard. 2. The host is Windows 7 x64 where the guest VM (using latest VMware player) is Windows 7 x86 3. I used, few times, 2.12 version of SAM-BA to update the firmware 4. I'm not getting any BSOD on neither Guest neither Host machines 5. Netduino Plus is detected fine both by Visual Studio 2010 Ultimate and MFDeploy. 6. In VM, Device manager info for the USB device states - Netduino and the Service is WinUsb. 7. The technique of re-plugging the Netduino on hags is not helping at all. I have no any other issues apart of the speed of the deployment, which eventually, after approx 10 minutes, goes fine. Once deployment is done Netduino works fine. I've used that exact same host and guest with 4.1.0.6 without any trouble. Just for info and possibly not related with the problem, my Netduino Plus is rev A. PS I've noticed that quite often Netduino (re)boots quite slow. I mean after switching it on, it takes ages to get to the point of executing the deployed application.

[georgejh]

Hey, I've discovered what's the source of the problem - it was the fact that I had a 2GB microSD card plugged into Netduino. Once removed, all works perfect. Now investigating what's wrong with the card or the problem is within the new Netduino Plus firmware. PS You want believe this! The SD card contained a Windows ready boost file. Once I deleted it all works fine! I wonder how possibly this file could be related to the problem? I will reformat the SD just in case and try again. PS 2 Reformatting the SD card doesn't change anything (all works fine) so I would suggest something been messed up because of the existanse of the ready boost file.

[nakchak]

that makes some sense afaik windows ready boost uses a special filesystem I.e. Not fat so your nd was probably struggling with the non standard filesystem partition on the card Nak.

[Chris Walker]

georgejh -- excellent detective work. The SD card driver does expect a standard FAT file system if a card is inserted...so mounting hangups when the formatting is abnormal does make sense. For those running VMs... If you are having troubles with WinUSB drivers for any reason and prefer the MFUSB (SpotUSB) drivers, you can manually switch.

[georgejh]

Oh, the card was formatted with FAT32, there were other files on it. Ready boost was just hidden file on it. No idea or any memory when or why I've created it but certainly all was working fine with the old firmware. Well, anyway, this particular problem is solved. I do not see need to change to MFUSB as all is fine and also have feeling it works faster, but thanks for the link - will have it in mind if things go bad again. Cheers