Procede update to 5-10 help!!!

s2k_335i · 05-22-2011, 02:27 AM

Today i downloaded the 5-10 and try to do the update. During the update, it failed at 97%. I tried several time but it keep saying ECU is in boot mode, please update firmware. When I update the firmware, it either failed at 46% or 97%. I start the car but now the car will not start. I have tried this on both XP and Window 7.
How can I get the ECU out of boot mode?
I am going to remove the procede tomorrow morning.
In the mean time, any assistant would greatly appreciated.

NiVeDh · 05-22-2011, 02:42 AM

When I had an issue like this, it was due to my USB-to-serial cable. Try shielding it by wrapping some aluminum foil around it. That helped me a little bit. In the end, I had to go with a higher quality cable.

OpenFlash · 05-22-2011, 02:45 AM

Quote:

Originally Posted by s2k_335i

Today i downloaded the 5-10 and try to do the update. During the update, it failed at 97%. I tried several time but it keep saying ECU is in boot mode, please update firmware. When I update the firmware, it either failed at 46% or 97%. I start the car but now the car will not start. I have tried this on both XP and Window 7.
How can I get the ECU out of boot mode?
I am going to remove the procede tomorrow morning.
In the mean time, any assistant would greatly appreciated.

There is really no special trick here. It can help sometimes to plug your laptop into a wall since Vista tends to drop comms when running on batteries. If you are already doing that, it's most likely that you aren't using a usb/serial cable that is 100% compatible with your operating system. And don't bother trying to run with the Procede until you get a full update (100%).

Sparky66 · 05-22-2011, 04:33 AM

Get a better cable and if it's still saying "ECU is in boot mode", follow this: (courtesy of Vishnu )

Recovering a Procede from a failed firmware update attempt

There are a few key things to note:

* If the firmware has a failed write during an upgrade, it will abort. This will leave the Procede in a state where it does not have required firmware installed, and will render the Procede unable to run the engine as normal. I would not recommend starting the engine in this situation, as the DME will be running without access to many of the signals it normally sees.

* If this occurs, shutdown the Procede software, and turn the DME off for a minute to reset everything. Then turn on DME (start button until yellow dash lights), and start Procede software and go online. It should come up with a message saying the Procede is in boot mode. Perform a firmware upgrade in the normal fashion (select from comms menu the upgrade firmware option and select file and then start upgrade). When the upgrade is complete, it will state it is resetting the Procede, but will never come out of reset. This seems to be a by-product of the software being started with the Procede in boot mode. At this point, shut down DME again and shut down Procede software. Then restart DME and restart Procede software. Everything should be back to normal.

* If you do a firmware upgrade out of boot mode, there is not need to do another firmware upgrade. Simply check the firmware version from the comms menu option, and it should verify that the firmware version you loaded is indeed present. There is no need to upgrade again to the same version.

* None of the above will have any effect on the maps loaded. There is no need to reload maps if you already have the maps you wanted in. The maps are completely seperate to the firmware, and are not effected in any way by the firmware upgrade process. Of course if the new firmware requires new maps and you have not done this yet, then go ahead and do it.

* If the Procede software does not go online when you attempt to do so. Check for issues such as cable not connected, DME not on (yellows), Laptop has shut down USB driver due to hibernation etc. It seems that the serial driver used by the Procede has a limitted number of failed attempts to open a com port after which it will come up with a com port error error which can only be reset by shutting down the software and restarting it (and I have had it require a full laptop boot to recover). Note that this will not happen if you refrain from keeping on trying to go online without rectifying the problem.

* I have never had a Procede that could not be recovered in a minute or two from a failed firmware upgrade, however without knowing the above, a user may become confused by com port errors and lengthy periods of "resetting" etc. The Procede has been designed to be recoverable from power loss or communications loss mid firmware upgrade. It enters boot mode if the firmware upgrade fails for any reason, and can be recovered from boot mode using the method above without removing the Procede or anything else.

I doubt there is any issue with the fuel pump or anything else in the car above. I would just reset all codes and I bet they will not come back and are only a result of the engine being started while the Procede had no firmware installed."

s2k_335i · 05-22-2011, 04:09 PM

I went and got a new USB/serial from Radioshack. It's a success this time with the new USB adapter. I was able to update to the new map also. There another delima, i received the following codes:

3100 12544 boost-pressure control, deactivation
2F6C 12140 Exhaust fumeflap, input signal - No issue here
11602 Error??
10907 Error??
2A9A 10906 Camshaft sensor inlet, signal

Any help on addressing these errors? I made several updates and clear out the codes but it still come back. Should i remove the procede, my FMIC, Intake and take it back to the dealer?

OpenFlash · 05-22-2011, 04:16 PM

Quote:

Originally Posted by s2k_335i

I went and got a new USB/serial from Radioshack. It's a success this time with the new USB adapter. I was able to update to the new map also. There another delima, i received the following codes:

3100 12544 boost-pressure control, deactivation
2F6C 12140 Exhaust fumeflap, input signal - No issue here
11602 Error??
10907 Error??
2A9A 10906 Camshaft sensor inlet, signal

Any help on addressing these errors? I made several updates and clear out the codes but it still come back. Should i remove the procede, my FMIC, Intake and take it back to the dealer?

Cycle ignition on/off/on. Then try clearing codes. They should go away. If not, call us tomorrow during business hours and one of us can walk you through it step-by-step. There is nothing different about this update from all the others. Just a matter of doing it properly.

s2k_335i · 05-22-2011, 04:24 PM

Thanks Shiv. I'll give that a try. Didn't have much issue with all the V4 and the V5 11-25 firmware/maps. For some reason, my brand new USB/serial that i bought Last year failed on me. Just some luck that I have this week. I cannot wait for the new Meth kit and my DP.

**335i** · 05-22-2011, 04:27 PM

Quote:

Originally Posted by shiv@vishnu

Cycle ignition on/off/on. Then try clearing codes. They should go away. If not, call us tomorrow during business hours and one of us can walk you through it step-by-step. There is nothing different about this update from all the others. Just a matter of doing it properly.

i remember also some codes but when u do this Cycle ignition on/off/on they go away

05-22-2011, 02:27 AM	#1
s2k_335i This is it!! 18 Rep 672 Posts Drives: FBO 335i without meth Join Date: Jul 2010 Location: Land of Freedom iTrader: (1)	Procede update to 5-10 help!!! Today i downloaded the 5-10 and try to do the update. During the update, it failed at 97%. I tried several time but it keep saying ECU is in boot mode, please update firmware. When I update the firmware, it either failed at 46% or 97%. I start the car but now the car will not start. I have tried this on both XP and Window 7. How can I get the ECU out of boot mode? I am going to remove the procede tomorrow morning. In the mean time, any assistant would greatly appreciated.
	Appreciate 0 Tweet Quote

05-22-2011, 02:42 AM	#2
NiVeDh Major General 426 Rep 8,003 Posts Drives: '08 E90 335i, '99 E36 M3 Join Date: Apr 2009 Location: Houston, TX & Atlanta, GA iTrader: (132) Garage List 2008 BMW 335i Sedan [8.66]	When I had an issue like this, it was due to my USB-to-serial cable. Try shielding it by wrapping some aluminum foil around it. That helped me a little bit. In the end, I had to go with a higher quality cable.
	Appreciate 0 Quote

05-22-2011, 04:33 AM	#4
Sparky66 Major 60 Rep 1,230 Posts Drives: 335 E92 Coupe. Jet Black. Join Date: Feb 2007 Location: Sydney, Australia iTrader: (0)	Get a better cable and if it's still saying "ECU is in boot mode", follow this: (courtesy of Vishnu ) Recovering a Procede from a failed firmware update attempt There are a few key things to note: * If the firmware has a failed write during an upgrade, it will abort. This will leave the Procede in a state where it does not have required firmware installed, and will render the Procede unable to run the engine as normal. I would not recommend starting the engine in this situation, as the DME will be running without access to many of the signals it normally sees. * If this occurs, shutdown the Procede software, and turn the DME off for a minute to reset everything. Then turn on DME (start button until yellow dash lights), and start Procede software and go online. It should come up with a message saying the Procede is in boot mode. Perform a firmware upgrade in the normal fashion (select from comms menu the upgrade firmware option and select file and then start upgrade). When the upgrade is complete, it will state it is resetting the Procede, but will never come out of reset. This seems to be a by-product of the software being started with the Procede in boot mode. At this point, shut down DME again and shut down Procede software. Then restart DME and restart Procede software. Everything should be back to normal. * If you do a firmware upgrade out of boot mode, there is not need to do another firmware upgrade. Simply check the firmware version from the comms menu option, and it should verify that the firmware version you loaded is indeed present. There is no need to upgrade again to the same version. * None of the above will have any effect on the maps loaded. There is no need to reload maps if you already have the maps you wanted in. The maps are completely seperate to the firmware, and are not effected in any way by the firmware upgrade process. Of course if the new firmware requires new maps and you have not done this yet, then go ahead and do it. * If the Procede software does not go online when you attempt to do so. Check for issues such as cable not connected, DME not on (yellows), Laptop has shut down USB driver due to hibernation etc. It seems that the serial driver used by the Procede has a limitted number of failed attempts to open a com port after which it will come up with a com port error error which can only be reset by shutting down the software and restarting it (and I have had it require a full laptop boot to recover). Note that this will not happen if you refrain from keeping on trying to go online without rectifying the problem. * I have never had a Procede that could not be recovered in a minute or two from a failed firmware upgrade, however without knowing the above, a user may become confused by com port errors and lengthy periods of "resetting" etc. The Procede has been designed to be recoverable from power loss or communications loss mid firmware upgrade. It enters boot mode if the firmware upgrade fails for any reason, and can be recovered from boot mode using the method above without removing the Procede or anything else. I doubt there is any issue with the fuel pump or anything else in the car above. I would just reset all codes and I bet they will not come back and are only a result of the engine being started while the Procede had no firmware installed." __________________ Sticky is an Idiot
	Appreciate 0 Quote

05-22-2011, 04:09 PM	#5
s2k_335i This is it!! 18 Rep 672 Posts Drives: FBO 335i without meth Join Date: Jul 2010 Location: Land of Freedom iTrader: (1)	I went and got a new USB/serial from Radioshack. It's a success this time with the new USB adapter. I was able to update to the new map also. There another delima, i received the following codes: 3100 12544 boost-pressure control, deactivation 2F6C 12140 Exhaust fumeflap, input signal - No issue here 11602 Error?? 10907 Error?? 2A9A 10906 Camshaft sensor inlet, signal Any help on addressing these errors? I made several updates and clear out the codes but it still come back. Should i remove the procede, my FMIC, Intake and take it back to the dealer?
	Appreciate 0 Quote

05-22-2011, 04:24 PM	#7
s2k_335i This is it!! 18 Rep 672 Posts Drives: FBO 335i without meth Join Date: Jul 2010 Location: Land of Freedom iTrader: (1)	Thanks Shiv. I'll give that a try. Didn't have much issue with all the V4 and the V5 11-25 firmware/maps. For some reason, my brand new USB/serial that i bought Last year failed on me. Just some luck that I have this week. I cannot wait for the new Meth kit and my DP.
	Appreciate 0 Quote