|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Today's Posts | Search |
|
BMW 3-Series (E90 E92) Forum
>
Transmission remap - Let's do it ourselves
|
|
12-03-2015, 04:43 PM | #398 |
715
Rep 755
Posts |
Tiago Can't find it too, sorry.
If i get the Intel HEX description right, we are save to flash the Alpina prog & data. All adresses and the extended segment records are a match. Funny fact: Alpina (7591971) & our *.0pa file (7591972) were finalized just one day apart. --> 22/23.04.2008 ;-) |
Appreciate
0
|
12-03-2015, 04:52 PM | #399 | |
Ballin' out of control.
524
Rep 1,289
Posts |
Quote:
It looks like 7582468 was superseded by 7591320. 7591320 was superseded by 7592136. 7592136 is available in SP Daten 51.1, perhaps even in earlier releases as it is really old. Check your GKE195.DAT file for an entry like the following: ;ZB-NR TYP-NR HW-NR IX SW-NR AM PIN S CS 7592136,0000000,7591972,A,7592137DA,0FFFFFFFFFD,00 0,1 V Hope that helps.
__________________
Alpina B3 Flash/BMS OCC/ER CP/ETS 5/HKS BOV/M3 Control Arms
|
|
Appreciate
0
|
12-03-2015, 05:32 PM | #402 |
F11 520D LCI - Stage I
45
Rep 187
Posts |
|
Appreciate
0
|
12-03-2015, 05:56 PM | #403 | |
Private First Class
25
Rep 153
Posts |
Quote:
|
|
Appreciate
0
|
12-04-2015, 07:00 AM | #404 | |
Major
808
Rep 1,192
Posts |
Quote:
Anyway, he came to the same conclusion that the program files for the Alpina B3 (7591971) and the US335 (7591972) are based on the same project which makes it very likely that they use the same memory mapping. So, I guess we are good to go for a first shot. You're welcome to beat me to it. Otherwise I'll try it on the weekend. |
|
Appreciate
4
|
12-04-2015, 08:49 AM | #405 | |
Banned
799
Rep 1,630
Posts |
Quote:
Regardless of the outcome, just want thank you for keeping this alive and persevering. You've provided tremendous service to this community. |
|
Appreciate
1
|
12-04-2015, 08:23 PM | #407 |
Colonel
871
Rep 2,611
Posts |
Ditto that. Thank you for all your efforts and other guys that joined in to expand the knowledge and the effort. Once you do your car make sure to come here every other day and tell us how great it is
|
Appreciate
0
|
12-05-2015, 05:09 AM | #408 |
715
Rep 755
Posts |
Ok, I'll give it a shot in the afternoon.
If that works, we would not only have a solution for the 335d, but also for 325d/330d models outside of US. At least for the LCI ones. I wonder when they started to use 7591972 hw in production. |
Appreciate
0
|
12-05-2015, 01:01 PM | #409 |
715
Rep 755
Posts |
1st try wasn't a success. The TCU kind of disappears from the CAN bus after flashing with Alpina prog & data. DME & DSC then constantly argue about missing messages from the TCU and most of the jobs from tool32 throw an error. I was able to bring it back to stock, but i learned that my WinkFP installation crashes when trying to write the UIF in expert mode. I shit my pants when seeing the windows error msg...
I stopped for today because i don't have my voltage supply here and battery got low. |
Appreciate
1
|
12-05-2015, 05:07 PM | #410 | |
Major
808
Rep 1,192
Posts |
Quote:
I switched off the UIF write in the configuration. Also, make sure you disable the "Fast baudrate" in the configuration. Always have a good power supply connected when flashing. It is extremely risky without. Programming voltage should be above 13V at all times. You need at least a 50A power supply for that. BMW recommends 70A. I'm using an older 45A but it is sweating... So am I now. I was hoping to find some encouragement before I try it myself. Hmpf. |
|
Appreciate
0
|
12-05-2015, 09:10 PM | #411 |
Major
808
Rep 1,192
Posts |
News from the fearless flasher
Bad news guys. I just can't get the Alpina flash to work. Even though my WinKFP doesn't crash when writing the UIF I still get the same effect that RayBan81 experienced. It gets stuck in boot mode and is invisible for the other ECUs.
Here's what I did: 1. In order to verify that WinKFP expert mode works, I tried flashing the original tranny program and data file (see first screenshot). Even though everything seemed fine and I got the "Programming OK" message, the car soon let me know that something was wrong (see second and third photo). The EGS was not communicating on the bus and the other modules were missing it dearly (see forth screenshot). The EGS was obviously in bootmode since it still responded to some Ediabas jobs like AIF read (handled by bootloader) but not to DTC read which is handled by the application. 2. So I tried going back to Comfort mode and flash its original file back. But wait, there's one Datafile I hadn't tried yet (A7587868.0da), so I selected that one and went on with the flash. Bad mistake. The reason why I never tried that one was not because this one wasn't available in earlier SP-daten versions as I thought, but it uses a different main program (7573100A.0pa). Since the EGS was in boot mode, it wasn't able to check if that was ok or not so it took the flash. But it wasn't finished after the flash went through 100%, it started flashing again but it went much faster this time. This is what I remembered happens when it updates the main program (first flash) and then writes the data program. That's when I noticed that it used a different .0pa for flashing then the known 7591972A.0pa. However, everything went back to normal after the flash, I cleared all faults and everthing was green in the ECU tree. I took a short drive and everything seemed normal. |
Appreciate
1
|
12-05-2015, 09:28 PM | #412 |
Major
808
Rep 1,192
Posts |
News from the fearless flasher
3. So then I went back to trying to flash the Alpina data. But now I'm getting always an error when I select the files for flashing (see screenshot): Error 501: Wrong project. So I tried flashing back the original files in Comfort mode. Also no go, because the HW doesn't match.
Now I'm slowly realizing that I'll probably pay Robert a visit in the beginning of January - with my mechatronic unit (plan B). Since the ECU is still responding I figured, let's flash the Alpina data anyway even though I'm getting the "Wrong project" warning. The flash finishes with "Programming OK" but with the same problem from the previous posts. It is stuck in Boot mode again. But it should have the new boot loader in there that "knows" that the Alpina files should be there. So I try to flash the Alpina file again in Comfort mode. Flash finishes and now I'm getting a WinKFP error message (see screenshot 2): [20:05:31.597] [2015-12-05] [<WinKFP Tool] 2089 PABD/CABD 06FLASH Programmieren 2538 [20:05:31.597] [2015-12-05] [<WinKFP Tool] switching programming mode failed 10FLASH, DIAGNOSE_MODE (ECUPM): ERROR_ECU_SECURITY_ACCESS_DENIED__SECURITY_ACCESS_ REQUESTED [20:06:21.111] [2015-12-05] [<WinKFP Tool] 2080 PABD/CABD 06FLASH Programmieren 3363 [20:06:21.111] [2015-12-05] [<WinKFP Tool] Programming state invalid 10FLASH, FLASH_PROGRAMMIER_STATUS_LESEN, Programmierstatus nicht plausibel [20:06:21.142] [2015-12-05] [<WinKFP Tool] 2080 Error COAPI2.CPP coapiRunCabd 6 [20:06:21.142] [2015-12-05] [<WinKFP Tool] Programming state invalid SG_PROGRAMMIEREN [20:06:21.142] [2015-12-05] [<WinKFP Tool] 2080 Error COAPIKF.CPP coapiKfProgSgD2 19 [20:06:21.142] [2015-12-05] [<WinKFP Tool] Programming state invalid At this point it is important to save the error log of WinKFP (Display -> Error.log). Which I copied and posted above so experienced people may be able to help later. Pulse is about 180 but I try to calm myself knowing that I have a plan B. But that involves draining the oil from the tranny and unmounting the mechatronic unit . So I keep trying flashing the Alpina with different settings of WinKFP. Maybe it's looking at the AIF field and finds the old data in there. So I configure WinKFP to write the UIF field (but those can be only written about 60 times) and I have used up some of them already. WinKFP now doesn't complain about the Wrong project anymore when I try to flash in Expert mode and it even finishes with "Programming OK" but it doesn't get past the boot loader. It could be worse. At least it's booting which enables flashing. I'm now letting the car go to full sleep to see if it maybe wakes up and everything is fine. Last edited by Mik325tds; 12-05-2015 at 09:39 PM.. |
Appreciate
1
|
12-05-2015, 10:06 PM | #413 |
TL/DR
100
Rep 237
Posts
Drives: 2009 335d Sport
Join Date: Oct 2012
Location: Arizona
|
You are a brave soul!
|
Appreciate
0
|
12-05-2015, 11:10 PM | #415 |
Major
808
Rep 1,192
Posts |
News from the fearless flasher
Wishful thinking - both: hoping the car would wake up and everything would be fine and also me getting a good night sleep without having this fixed.
4. So now the last resort is to Expert back to the original cal (A7606274.0da) and program (7591972A.0pa). Getting the warning message again: Wrong project. I'm guessing this must be normal when jumping program versions. Same story, the programming is successful but the ECU stays in bootloader. Then flashing the same files again in Comfort mode. ---and hooray it comes back to life. RayBan81: Did you also get the warning about the wrong project and did you have to flash twice (once in Expert and then in Comfort mode) to get your EGS back to the starting point? Did you use the PABD: 11GKE215.IPO when going to Alpina or the original 03GKE195.IPO? I suggest you update your installation of WinKFP before you try again (and a good power supply). You should be at Standard Tools version 2.12 for proper use in Win7. At least now I have a chance of getting a night sleep. |
Appreciate
0
|
12-06-2015, 10:10 AM | #416 |
Major
808
Rep 1,192
Posts |
End of story?
I'm very sad to announce that the US335d does not take the Alpina flash.
I tried again this morning with several different attempts and no matter how I do it, it just stays in boot mode after the Alpina flash. But I learned something. The reason why I had to use comfort mode again after reflashing to the original program was that in Expert mode you have to flash program and data separately, which I completely overlooked. As soon as I flashed the correct data file with the program, everything starts working again. So I tried just flashing the Alpina data file to the original program file. But that also locks the ECU. And I think I know the reason why: Every file (data and program) contains a Referenz identifier. Here's the one for the Alpina program: $REFERENZ 0479SA0T641Z U The 9SA0T is the ECU project reference. The EGS contains also a non-changeable HW reference which can be read by the Diagnostic page of WinKFP. Here's mine after going from the Alpina Flash back to the original flash: Entries of data reference: -------------------------------------- ECU identifier: 047 Project: 9S90T Program version: 641Z Data version: 1UE12 Status: 34 -------------------------------------- Entries of HW reference: -------------------------------------- ECU identifier: 047 Project: 9S90 Status: 34 -------------------------------------- Entries of ZIF: -------------------------------------- ECU identifier: 047 Project: 9S90T Program version: 641Z BMW hardware number: 7591972 Status: 34 -------------------------------------- Entries of ZIF-Backup: -------------------------------------- ECU identifier: 047 Project: 9SA0T Program version: 641Z BMW hardware number: 7591971 Status: 34 -------------------------------------- ECU-Status: 01 -------------------------------------- Notice, how all Project numbers line up? That's when the ECU-status goes to 01 and everything works ok. The ZIF-Backup contains the data of the previous flash and we can easily see that the project numbers don't line up. Unless we find a way to make the Project numbers match, I guess this is the end of the story for the Alpina flash. |
Appreciate
0
|
12-06-2015, 10:25 AM | #417 | |
Ballin' out of control.
524
Rep 1,289
Posts |
Quote:
The HW-NR (7591972) is the same as your 335d. Even if the program file doesn't work, perhaps the data file will...just a thought.
__________________
Alpina B3 Flash/BMS OCC/ER CP/ETS 5/HKS BOV/M3 Control Arms
|
|
Appreciate
0
|
12-06-2015, 11:27 AM | #418 |
715
Rep 755
Posts |
Mik325tds I used the 195 ipo file the whole time. Made the most sense to me. Seems like both work.
Concerning the flash procedure: I always use the supply when flashing the CIC or an ECU where I don't know how long it will take. From experience i can tell that it's quite safe to flash EGS & DME without the supply. (via CAN & ICOM and if your batterys in good condition) Power drain isn't that high and it's done in ~ 1 minute. I did that for sure 200 times until now and never had problems. But i will try it today with the supply connected, just to be bullet proof. Also i never experienced more than 25amps during flashing. My supply is rated at 50A, but never came even close to that with stable 13,8V. Maybe there's a way to change the project numbers with tool32..did you investigate that already? I'm going to try the B5 data now...the adress records match, so that should be safe too. Please keep your fingers crossed. |
Appreciate
0
|
Bookmarks |
|
|