Pages: [1] 2
Author Topic: Help Flashing a Unitronic ECU  (Read 14847 times)
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« on: June 01, 2014, 03:55:56 PM »

My question relates specifically to Checksums.  Does the bin file contain the checksum or does it have to be written separately?  This is a ME7.5 ECU so ME7Sum won't work to write.  I'm not editing the EEPROM or using the program that the MTX plugin works for so I don't seem to have a lot of options to write my own checksum.  So if I write the bin file with NefMoto and check the checksum is correct with ME7Check will that be enough to return to stock?  In otiher words, if the bin contains the checksum then the check should return OK if it was written alright, but if the bin does NOT contain it's own checksum then the checksum for the old Uni software will remain and will NOT be correct for the stock flash regardless if the flashing is completed successfuly.

I have a bin file for my ECU (8E0909518AF), I have a dumb cable (VCDS cable too) and made a bench cable just in case.

Thanks!
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #1 on: June 01, 2014, 04:36:16 PM »

There are checksums in the Flash (1024kb file) and in the eeprom (512byte file).

If you flash the stock file, and the checksums are good, that's all you need to do.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #2 on: June 02, 2014, 08:26:52 PM »

So flashing the bin seemed to work but my ECU won't start the car and won't communicate via standard obd2 Sad

I did attempt to start the car after the flash was successful which was probably a mistake.  Now the start position cranks the engine endlessly and when in the ON position you hear the radiator fans kick in to full blast.

I made a bench flash cable for this very scenario however I'm having no luck getting my ME7.5 into boot mode.  I have read that shorting positive and ground before starting the standard boot mode procedure has allowed some to communicate in boot mode however the details of this are vague.

Help?
Logged
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #3 on: June 03, 2014, 05:35:50 PM »

Alright I have tried many combinations of steps to get this ECU connected in boot mode with no success.  I read through the Infineon datasheets found the RSTIN pin (140) that is low for a reset.  from reading this is required to then set P0L.4 low (pin 104) to enter bootmode.  I double checked my bench cable and all is well there.  I have tried Rosstech HEX + CAN in dumb mode and my FT232BL based dumb cable.  I am using NefMoto 1.9.3.2.

I seem to be able to tell when I enable boot mode on the ECU since my power supply will let me know the draw. When I pull the RSTIN pin low I get a 150mA draw and if I leave the P0L.4 pin low before disconnecting it next I am left with a 160mA draw.  If I power on the ECU with no pins pulled low then my draw is 180mA.

So i'm considering that i'm not using the right cable however I have read others running into this same issue (Nottingham, Professor) and they tried multiple cables and applications.  I do see almost the full 12v applied voltage on the K-Line (ECU side) however which made me suspect my bench cable was wired incorrectly however there is no continuity between the k-line and the +12v lines..

if anyone out there knows of any other 'reset' tricks for this ECU (I have tried just shorting 140 to 139 Vss digital ground to achieve the same results I have had jumping 140 to the ground rail for chassis ground) I would really appreciate it, expecting 3 days of rain in the next couple days so without a car I'll be making it to work on the motorcycle  Cry  I certainly understood the risk that initial flashing had the potential to go wrong and that's why I was prepared with my bench cable however I never expected just getting to boot mode would be this complex  Huh
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #4 on: June 03, 2014, 05:38:21 PM »

I stopped reading once i saw you were trying to use nefmoto.

NEFMOTO DOES NOT DO BOOTMODE. The menu is there, but it is not functional. You must use galletto.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #5 on: June 03, 2014, 09:03:52 PM »

Ughhhhhh thanks... I feel like I've read that before but my head has been in a million places I just thought, "Oh bootmode! Wonderful, now I won't need to edit my cable and figure out another program, one less complication."

Try again tomorrow...
Logged
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #6 on: June 04, 2014, 03:15:35 PM »

Alright my 'dumb' cable with the FT232BL chip does not seem to want to be programed (doesn't have a serial number and can't write one?) So I read my VCDS cable (legit) as s/n RT000001 (suspicious?) and wrote that to Galletto. 

I keep getting BOOTMODE INACTIVE

Tried everything I have before, can't tell if I"m having trouble communicating or if the problem is getting into bootmode  Huh
Logged
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #7 on: June 04, 2014, 04:06:58 PM »

yaaaaaahoooooo!  PROGRESS!!!!

I read someone recommended to write to the 95040

pvl, 2nd post @ http://nefariousmotorsports.com/forum/index.php?topic=889.0

So I tried several things to read the eeprom with me7_95040 http://nefariousmotorsports.com/forum/index.php/topic,1168.0title,.html and my ross-tech cable wouldn't work because I couldn't get the drivers right but I was able to read using my dumb cable via BOOTMODE!!!  Grin  happy days

not sure how I'm going to flash the 29f800dd though since galletto doesn't like my dumb cable and I'm not 100% understanding what to do with my Ross-Tech VCDS cable (Hex+Can)

now I'll be looking for a virigin eeprom to flash

Code:
Ver: 1.31
Com Port: 4
Baud Rate: 10400
Opening COM4 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P4.7
Configuring SPI Interface ... OK
Checking EEPROM status ... 0x00F0 ... OK
Reading EEPROM ... OK
Printing to screen

Offset  0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F
   0   20 20 20 20 20 5A FF 08  19 31 31 31 30 30 32 5A
  10   05 01 02 00 0D 8C 00 00  00 00 69 C1 00 A5 8F FD
  20   05 01 02 00 0D 8C 00 00  00 00 69 C1 00 A5 8E FD
  30   04 01 1C 17 85 D9 B4 B2  E0 EB 49 00 01 00 EC FA
  40   04 01 1C 17 85 D9 B4 B2  E0 EB 49 00 01 00 EB FA
  50   07 02 58 02 A4 01 FB FF  30 04 03 0F 07 00 AC FC
  60   81 04 B3 0D 63 0E 00 00  87 03 01 00 00 00 B9 FD
  70   05 04 33 34 35 30 31 05  00 00 3D 41 00 32 3E FE
  80   05 04 33 34 35 30 31 05  00 00 3D 41 00 32 3E FE
  90   00 80 80 80 80 00 00 80  00 80 80 FF 78 00 00 FB
  A0   00 80 80 80 80 00 00 80  00 80 80 FF 78 00 00 FB
  B0   05 07 00 00 20 57 41 55  4C 43 01 00 00 00 4C FE
  C0   05 07 00 00 20 57 41 55  4C 43 01 00 00 00 4C FE
  D0   36 38 45 33 33 41 32 32  34 35 34 34 41 01 22 FD
  E0   36 38 45 33 33 41 32 32  34 35 34 34 41 01 22 FD
  F0   55 5A 36 5A 30 42 30 33  31 34 30 37 30 01 E0 FC
 100   55 5A 36 5A 30 42 30 33  31 34 30 37 30 01 E0 FC
 110   00 00 64 49 8F 09 00 00  00 00 00 00 00 00 11 11
 120   00 00 58 58 58 58 58 58  58 58 58 58 58 58 CE FB
 130   01 01 00 00 00 00 00 00  00 00 00 00 00 00 EB FF
 140   01 01 38 45 30 39 30 39  30 31 38 41 20 00 A1 FD
 150   01 07 01 22 64 01 34 2F  02 FF 51 80 7B 62 49 FC
 160   FF FF FF 30 34 00 00 00  00 00 00 00 00 00 89 FC
 170   00 00 01 22 64 01 34 2F  02 22 6C 00 17 20 37 FE
 180   08 6D 00 00 00 00 00 00  00 00 00 00 00 00 73 FF
 190   00 00 00 00 00 00 00 00  00 00 00 00 00 00 E7 FF
 1A0   00 00 00 00 00 00 00 00  00 00 00 00 00 00 E6 FF
 1B0   00 00 00 00 00 00 00 00  00 00 00 00 00 00 E5 FF
 1C0   00 00 38 45 30 39 30 39  35 31 38 41 46 20 50 FD
 1D0   30 30 30 33 00 00 00 00  00 00 00 00 00 00 20 FF
 1E0   01 02 4E 45 46 4D 54 4F  80 03 03 01 00 00 8F FD
 1F0   01 02 4E 45 46 4D 54 4F  80 03 03 01 00 00 8F FD

Closing COM4
Logged
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #8 on: June 04, 2014, 04:40:26 PM »

So I found a virgin 95040 image here http://nefariousmotorsports.com/forum/index.php?topic=3318.0 thanks ddillinger

and successfully flashed that...
Code:
C:\Users\Asus\Desktop\me7_95040_v1.31>me7_95040 --bootmode -wp4 95040.bin
Ver: 1.31
Com Port: 4
Baud Rate: 10400
Opening COM4 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P4.7
Configuring SPI Interface ... OK
Checking EEPROM status ... 0x00F0 ... OK
Writing EEPROM ................................ OK
Verifying EEPROM write ... OK
Closing COM4

I apologize in advance for blowing up my own thread, I hope this helps someone down the road and it's also helping me organize my own thoughts and progress.
Logged
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #9 on: June 04, 2014, 05:34:46 PM »

So I can't get Galletto to work right now.  I have been able to connect in bootmode with the dumb cable (FT232BL same as FT232BM) and Me7_95040 but Galletto does not seem to want to work with my dumb cable (can't program a serial number to it, it doesn't have one) and I can't get the HEX+CAN to work either.  Galletto returns "No interface found" or "Boot Mode Inactive" so I guess I'll have to purchase a different cable.  I have a commander 3.6 cable too but I doubt that'd work.  I'm starting to amass quite the collection of these cables and I'm guessing near everyone on this forum also has a sizeable collection of their own  Undecided
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #10 on: June 04, 2014, 05:53:05 PM »

So I can't get Galletto to work right now.  I have been able to connect in bootmode with the dumb cable (FT232BL same as FT232BM) and Me7_95040 but Galletto does not seem to want to work with my dumb cable (can't program a serial number to it, it doesn't have one) and I can't get the HEX+CAN to work either.  Galletto returns "No interface found" or "Boot Mode Inactive" so I guess I'll have to purchase a different cable.  I have a commander 3.6 cable too but I doubt that'd work.  I'm starting to amass quite the collection of these cables and I'm guessing near everyone on this forum also has a sizeable collection of their own  Undecided

Heh, I have just two cables. My Hex-can which is literally brand new (and doesn't work with ANYTHING despite having the right drivers and being in dumb mode) and a D+CAN BMW INPA cable which works with EVERYTHING.

The VAG Commander cable should work though.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #11 on: June 04, 2014, 07:46:58 PM »

VAG Commander cable didn't work Sad 

ME7_95040 has been the best though, sort of wish there was a similar command line utility for flashing the 29F800BB

I'm basing my conclusion that the cable i'm using is at fault on the response I've gotten from ME7_95040.

I've been able to read, write and confirm (read again) that I've been able to write the virgin 95040 bin file using my dumb serial-less FT232BL cable with no issues.

If the cable is bad ME7_95040 will return
Code:
Starting Boot_mode ... FAIL ... No echo from cable. (error=0x07)

If the cable is communicating good but the ECU is NOT in boot mode ME7_95040 will return
Code:
Starting Boot_mode ... FAIL ... No echo from cable. (error=0x07)

And if all is well you get
Code:
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK

though if I try to perform a second bootmode operation after one successfull one I'll get the following error
Code:
Starting Boot_mode ... uC identification response = 0xAA. Unknown ID. (error=0x0
1)
which just means I have to reset the ECU into bootmode again and try the command a second time

Point is... ME7_95040 is responsive compared to Galletto that only ever returns "no interface" or "boot mode inactive" which doesn't really help a whole lot.
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #12 on: June 04, 2014, 09:15:49 PM »

Did you edit the Galletto software to match your cable ID?
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
stolenheartdealer
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 50


« Reply #13 on: June 05, 2014, 06:56:53 AM »

Did you edit the Galletto software to match your cable ID?

I can't edit the one cable I know is working, mProg displays it as a 'blank' device when you Scan.  When you read you get some hex but the s/n displayed is 00000001 and when you Read and Parse you get some error and nothing is clickable so I can't click the Fixed Serial Number box and edit the displayed 00000001 data field which is likely erroneous data anyway.  Still I tried adding this to Galletto and I believe I'm able to scan but always says Boot Mode Inactive.  I get the same with VAG Commander and my HEX+CAN in 'dumb mode'.  Is there a text file that needs to be edited with the interface's port?  I can't get my HEX+CAN to be recognized as a virtual com port even though it's set in VCDS as dumb, so I haven't been able to use it with ME7_95040 because I need to specify a port for communication to begin.

For the record my dumb cable is the black 30 dollar one available through ECStuning.com
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #14 on: June 05, 2014, 08:40:33 AM »

I can't edit the one cable I know is working, mProg displays it as a 'blank' device when you Scan.  When you read you get some hex but the s/n displayed is 00000001 and when you Read and Parse you get some error and nothing is clickable so I can't click the Fixed Serial Number box and edit the displayed 00000001 data field which is likely erroneous data anyway.  Still I tried adding this to Galletto and I believe I'm able to scan but always says Boot Mode Inactive.  I get the same with VAG Commander and my HEX+CAN in 'dumb mode'.  Is there a text file that needs to be edited with the interface's port?  I can't get my HEX+CAN to be recognized as a virtual com port even though it's set in VCDS as dumb, so I haven't been able to use it with ME7_95040 because I need to specify a port for communication to begin.

For the record my dumb cable is the black 30 dollar one available through ECStuning.com

You need to install the VCP drivers for your rosstech cable.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.022 seconds with 17 queries. (Pretty URLs adds 0s, 0q)