I just got my first USB Mountaineer! It is so cute! So like a good newbe I started with the “Mountaineer Firmware and USB Driver Installation Guide for NETMF 4.2 QFE2”.
“Compared to QFE1, the QFE2 release allows you to use USB drivers that run in user mode and therefore cannot cause the infamous Blue Screens of Death. It also adds support for analog outputs, which was contributed by Oberon microsystems to the NETMF community.”
I decided that Blue Screens of Death are worth avoiding so QFE2 is an upgrade I need.
Following each step carefully gets me to step (4) Start the DfuSe Demonstration program. After I press the “UPGRADE” button the following happens:
[ol]Target 00: Upgrading - Erase Phase 100%
Target 00: Upgrading - Download Phase 100%
Target 00: Uploading 0% Error DfuSe Demo has stopped working: A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available (see attached image).
[/ol]
I tried on a second computer, fresh install following the “Mountaineer Firmware and USB Driver Installation Guide for NETMF 4.2 QFE2” exactly.
On first attempt I received a different error (see attached image). Second, third and fourth attempts result in the “DfuSe Demo has stopped working…” fault. The following is what I am getting in the Application Event Logs:
I have noticed a slight version difference in the documentation. The “Mountaineer Firmware and USB Driver Installation Guide for NETMF 4.2 QFE2” PDF in step (2) tells me to obtain v.3.0.2 but the link took me to a download of v3.0.3.
[ol]
POWER: I am powering my MountaineerUSB using the connected USB port and supplied USB Cable. While MFDeploy does not detect the board, the DFU Tester that I used to upgrade the Firmware does detect it; so I do not believe that I am fighting a power issue.
Visual Studio 2010 does not appear to detect the board.
Windows Device Manager does appear to detect the board (http://www.tinyclr.com/uploads/forum/img/6958_problem_large.png). Is that what you mean by Configuration Panel?[/ol]
The “Mountaineer_WinUSB_Driver” provided in the “Mountaineer Firmware and USB Driver 4.2 QFE2 (USB Mainboard)” is not signed. It was a actually pain to get it installed.
(2) Downloaded the “Mountaineer Firmware and USB Driver 4.2 QFE2 (USB Mainboard)”
(3) Updated the Firmware to QFE2
(4) Updated the USB Driver 4.2 QFE2
—> Mountaineer_WinUSB_Driver (THIS DRIVER IS NOT SIGNED)
—> MontaineerUSB.inf
—> WdfCoInstaller01009.dll
—> winusbcoinstaller2.dll
I’ll try removing the provided driver and find a Microsoft Driver as per your suggestion. I’ll post the result here.
Windows is a silly monkey that tell you it installed the Mountaineer USB Driver, but sometimes does not !
You must re-install the NETMF SDK 4.2 QFE2 after the Firmware and Driver installation in order to make MFDeploy goes right !
After a RESET, the mainboard enters a boot loader (TinyBooter), from there starts the common-language-runtime, which in turn interprets the application.
You can make the board stop in the boot loader and check whether MFDeploy then recognizes the board (visible at the USB list box, and then by its response to a Ping - click on the “Ping” button in MFDeploy). To stop in the boot loader, please hold down the SW button while pressing the RESET button on the mainboard. Now the blue LED should be blinking, and MFDeploy should be able to “see” the board. Otherwise something may be wrong with the boot loader or the hardware.
If MFDeploy now sees the board, erase the application (“Erase” button, “Deployment” check box). There may be a defective application in the Flash that crashes the system right after it starts.
