Thanks for the quick updates, but that firmware has a bin, hex files no DFU so my guess this will require a different Process… looks similar to GHI… will GHI EMX updater work ?
thanks.
and remember i can’t use MFDeploy since it recognizes the board but can’t ping it or do anything to it…
This is definitely a driver issue, because i noticed that the win USB driver doesn’t install in WindowsXP 64 at all… only the old driver that keeps getting installed. even if i reference the path and i know this because when i deleted the old usb driver folder it kept complaining about Mountaineer.sys file even when i pointed it to win usb Driver, and the only way for me to get back to the old Firmware is by having the DFU file since the only application that would talk to my board is the STFU… MFDeploy is always a no go as it locks up the driver as soon as i try to use it. and the only way out is by rebooting the system,
Can you please prepare a DFU file for the old firmware? thank you,
You have to check the box to delete all files when you are uninstalling old driver and preferably use different USB port when installingthe new one.
XP doesn’t have that but it does uninstall correctly, i even did it the old school way thought SAFE MODE… the thing is when i plug it back it prompts for the driver and i point it to the the driver, i put the correct path to the winUSB Driver and yet it still looks for the older one, which simply means the winusb driver is not compatible with WindowsXP 64… at least that’s what i think…
hopefully we’ll get more answers tomorrow when Cuno returns to the office.
“a7e70ea2” is used as “friendly name” in all NETMF USB configurations. It may originally have had something to do with Sideshow. Today it is probably just a historic artifact.
In case you can see the board in MFDeploy (“Mountaineer Xxx_a7e70ea2”) but not ping (“No response from device”), try the following. It could be that something went wrong with the deployment, this could prevent TinyCLR from working properly. The previous deployment must be deleted (flash sector erase).
- Connect the board and open MFDeploy, select “USB”
- Press “SW” on the board and keep it pressed, press and release “Reset” and finally release "SW. The device must be now in bootloader mode. When pinging, you should now get: “TinyBooter Bootloader build info: Copyright Oberon microsystems, Inc.”
- Click “Erase” and select “Deployment”, Erase
- Reset the board
Note 1: erasing the deployment would also work without going in Bootloader mode (as long as ping works, of course… )
Note 2: if it still doesn’t work, try to reload the firmware as well, as explained here (QFE1); http://www.tinyclr.com/forum/topic?id=8565&page=1#msg85076
@ Jay Jay: I’ll start a new topic about the XP problem… There must be a driver problem there
I did quite a few bad experiences with VM (VMWare)… A virtual USB port never works as well as a “real” one. I’d really advise against using one.
Maybe it could work better with WinUSB than with the previous driver though…
@ Corentin: tried the reset trick above and MFDeploy still couldn’t ping and just for the heck of it i tried cerberus tinybooter yeterday night and that one loaded and i was able to ping the board from MFDeploy, not sure if that helps you narrow down the issue…
as for the VM i didn’t try the mountaineer with that… this was for the Spider… the Mountaineer is being developed on a WindowsXp 64 machine…
i will try to flash the old firmware and report back…
thanks for the help…
@ Jay Jay - Did you find your charger and go to the dark side?
yes i did and it is blown the reason why it was out of sight 
i will go out and buy one soon hopefully sometimes today…
I have a Win7 and VS2010 Ultimate image if you want to give that a try first…
Thanks Justin,
But i think i narrowed it down to a USB Driver issue with WindowsXP 64 bit…for the lock up and WindowsXP 32 not being able to deploy the new firmware…
and couldn’t get it to deploy in WindowsXp 32bit, it does ping but looks very weird in MFDeploy take a look at the imagine below:
“Trying to write to bootstrap region”…
Try only with “ER_FLASH” and “ER_CONFIG”. Does it work better?
Mine looked then same, weird Oberon’s mixed in with Chinese in MFDeploy…(Win7 x64)
here is what i get when i do that… still no go…
Please test the drivers in WindowsXP as it seems an issue somehwere…
thanks for your help.
Same signature fail on the Bee…
yep after i clicked ok… i can ping the device and MFDeploy talks to it fine… this is on WIndowsXP 32bit…
when i move the device to WindowXP 64 the same issue is still there no ping from MFDeploy…
here is the image from WindowsXP 32 bit:
Is the 32bit a clean install and the 64bit uninstall reinstall?