Hello guys, since I’m having issues with the new firmware (See here ) http://www.tinyclr.com/forum/topic?id=8560
i was wondering if anyone knows WHERE To get the previous version of the firmware? the non QEF2 version…
i looked all over the resource page on the Mountaineer Site and couldn’t find it… tried to use the contact us page to ask the question and i was directed here so it sounds like GHI is owning the support on this board… at least i know i won’t be lost for long 
thanks.
On http://www.mountaineer.org/resources/ see the section “SDK and drivers”, the original QFE1 firmware is still there, and at the moment I’d recommend to stay with it until we have done some more tests:
Mountaineer USB Driver download:
http://www.mountaineer.org/app/download/6094039375/USB_Driver.zip?t=1340203422
Mountaineer Gadgeteer 4.2 SDK download:
http://www.mountaineer.org/app/download/6094040975/MountaineerGadgeteer42SDK.zip?t=1340959056
Here’s a new Web page with the Mountaineer firmware, USB driver, and firmware source code:
To go back to the previous version, do the following:
That’s the problem it doesn’t work…
MFDeploy can’t ping or erase the board even in bootloader mode … the only way i can access the board is through the STDFU tool…
any other suggestions…
Note that when i load the Cerberus tinyloader using the STDF tool the board becomes responsive through MFDeploy… i hope this helps narrow down the issue…
Any other suggestions!!!
thanks.
I think that’s why you can’t access it through MFDeploy. Either DFU mode or Bootloader mode, but not both at the same time.
Did you remove the connection on the socket 7?
You mean Socket 8 right?
when i say i can access it through STDFU tool, that’s not at the same time as MFDeploy, i know MFDeploy doesn’t see the Boards in DFU mode… and that STDFU doesn’t see the boards in Bootloader mode 
SO in short: if i start the Device Normal: MFDEPLOY sees the board but can’t ping…
If i start the Board in Boot-loader mode: Using the SW and Reset button… MFDeploy sees the board but can’t ping.
when those two fail i resort to the STDFU tool:
i plug the extender to Socket 8, jump pin 1 and 8. reset the board now I’m in DFU mode and i can see it in STDFU Protocol and i can re flash the firmware… 42QEF2 since that is the only one that comes in DFU package… so i’m STUCK with this one since i can’t deploy 42QEF1…
when that’s done i repeat the above steps and the same thing happens…
So what do i need :
i need a DFU package for QEF1 to try using the STDFU tool… since that’s the only way i can flash firmware…
thanks.
We have now put two archives on the Mountaineer Web site that contain also the .dfu files and the USB drivers:
http://www.mountaineer.org/resources/netmf-4-2-qfe1/
Does it work with these .dfu files?
Hi,
I just got around to testing this, the site you mentioned above DOES NOT Have any .dfu files… the zip file contain only the bin and hex files…
can you please provide a direct link to the download. i have mountaineer Eth board.
thank you.
Disregard the reply, i do see the DFU files… i must be going blind sorry about that…
OK i updated the board with the QEF1 DFU it went in without any issues…
but in WindowsXP 64bit MFDeploy can’t ping the board still get the same error
Pinging... Error: No response from device
But in a VM with Windows XP 32 bit i can ping the board fine…
so this is definitely an issue with the USB Driver on WidowsXP 64bit…
Are you guys able to test the Driver in a widowsXP 64bit.?
also may i suggest you update the Board Product page with the Compatibility issue with WindowsXp 64 bit until it is resolved…
Please let us know…
thank you.