So I attempted my update to V3 tonight...I launched Xmap V3.0.2, started the V2 to V3 wizard, got the thing in boot mode, ans way about 10 seconds into the reprogram when an error window popped up about a error in the program, prgramming failed, or something...I can't quiet remember what the window said. Soooo.....I turn the ignition off, take it out of boot mode, turn the ignition back on....and the LED on the Xede does not go on. Hmmmm....I check some connections, try again, nada. No blinking orange light when the ignition is on, no solid green when the car is running....nothing.
So did this thing fry out during the update? What can I do about this?

 

try doing the update again.

 

no dice....no light, no connection. Nothing happens.

 

i had problems with my updating too..

put it back in boot mode and try again. try using the Update Firmware thing inside XMap as well as Xupdate.

The sequence of when to turn car ON and to START car also seemed to make a difference. just keep trying, you might just get it to work by accident.

 

My XEDE was very finicky when the firmware was updated. It liked it when you turned the car off/on quickly when in boot mode. It didn't like it when you did it slowly.

 

I'll give it another whirl tommorrow. Thanks for the input!!

 

I doubt it's fried Just do the update again and it should work.

shiv

 

Are you trying your update with Xupdate

 

Ok, I'm going forth with the programming right now. It took a few flicks of the ignition to get it going....and you're right, it was only after I flicked it off/on real quick did the reset window disappear, and it began programming.
Does it ever hang up during the process? The estimated time says 22 seconds, but I'm going on 5 minutes now, and the Program Status window stills says "Programming"?

 

If something like that were to happen...What kind of warranty do our Xede's carry?

 

A good question. Does the the Xede hardware carry a longterm vishnu warranty?

I would expect that either vishnu or chiptorque would want to look at it if there really was a hardware failure. This isn't consumer grade electronics. Where a PC componant might fail after a couple of thousand of hours, I expect my Xede to last much longer. Isn't the circuitry sourced from a company that uses it for tractor duty?

Back to the original question. As shiv said, it's not easy to fry the Xede using vishnu update directions. You can get the Xede firmware in an unworking state, but fry the hardware...not likely. I mean, I wrote logging software mostly by sending the Xede random bits and seeing what came back. My unit has spent tens of hours justing sending and receiving random junk -- in both normal operation and boot mode. That same unit is still running like the day I recieved it.

d

 

Well, I keep getting the same error...then after I click out of it, I get a messag saying my comm port is unavailibe, even though it's the one I always use & has always worked.

 

You are doing the little on-off-start dance (the START is important), right.?

d

 

Well, there is another error that pops up as Im starting the upgrade process..a window pops up and says "cant communicate with Xede" (note that the comm port error window does NOT appear before this, like it would if the comm port I chose was in use by something else.)Anyways, I am just bypassing it, opening the flash burn utility, and the burn does indeed start, but I wind up with that error message I posted above every time.

 

Is your car running while doing the update? I got the same error as you with just the ignition on and the car off.

This link my be helpful to you:

https://www.evolutionm.net/forums/sh...rmware+problem