So I took a study break from the brachial plexus and other stuff to put the BMS flash back on my car (missed it ever since I gave my Cobb to a friend). Downloaded the files, the bbflash utility, and the BMS modified bbflash utility. Of course, being Kline with a useless 6amp charger, and with every modern computer I own using intel chipsets, I couldn't read the car. Lots of dropped communication in the logs.
For failed computers reference: a Core2Duo laptop (memron/perym chipset) failed. First, second and third gen i7 chipset laptops failed (ivybridge was an ultrabook) which should mean any of the first three generations of i5/i7 based laptops with Nahalem, Clarksfield, Sandy bridge and Ivy bridge will fail... or at least take over 5 hours (not a good idea with a 6amp charger). Basically anything from 2009+ from intel probably won't work well for Kline.
Anyway, I dug out my old desktop from the closet, an AMD rig I built in 2003. To my surprise it booted up into windows XP service pack something faster than my current i7 boots. One thing I'd like to mention is you need .NET framework installed to use the bimmerboost software. Moving along... I attempted communication, I got voltage sometimes, sometimes not. VIN sometimes, sometimes half VIN. Tried a read and 70 minutes later I had what looks like a clean ROM.
Took it to TunerPro and started porting the BMS maps into my ROM (OCD about things like that). Afterwards saved it, brought my stock, modified, and the canned BMS ROM to the computer to write. This is where headaches insued.
On the first attempt, it said communications failure, but the fuel pump kicked on. Red light on cable blinking away... I thought it had failed so I closed everything. And now the car won't start, so was apparently writing even though it gave an error. Couldn't get anything to write now, got the same thing over and over. The software was saying the computer was in recovery mode and I need to upload a working ROM.
So to fix it and get things working, in case anyone else runs into similar issues, I had to unplug the battery for a minute or so and try again. My car has about a 50/50 chance of a write starting correctly. If it fails off the get go, I had to unplug the battery and try again. But, if it progressed to step 1/2/3 everything works fine, 10 minutes later I have a BMS flash again. I was able to write the canned flash and the one I modified no problem, well, 50% of the time.
Still buggy for sure but props for this! Should be relatively smooth sailing now that I know what to expect! On a final note, I ended up using the BMS modified version 1.1 for all of this. The normal bbbflash beta was definitely more aggressive at trying to write it seemed, but it failed once at step 3. Terry's version whatever he changed seems a bit more stable for KLINE, may want to think about incorporating those changes into the main release.
![Click here to enlarge]()
For failed computers reference: a Core2Duo laptop (memron/perym chipset) failed. First, second and third gen i7 chipset laptops failed (ivybridge was an ultrabook) which should mean any of the first three generations of i5/i7 based laptops with Nahalem, Clarksfield, Sandy bridge and Ivy bridge will fail... or at least take over 5 hours (not a good idea with a 6amp charger). Basically anything from 2009+ from intel probably won't work well for Kline.
Anyway, I dug out my old desktop from the closet, an AMD rig I built in 2003. To my surprise it booted up into windows XP service pack something faster than my current i7 boots. One thing I'd like to mention is you need .NET framework installed to use the bimmerboost software. Moving along... I attempted communication, I got voltage sometimes, sometimes not. VIN sometimes, sometimes half VIN. Tried a read and 70 minutes later I had what looks like a clean ROM.
Took it to TunerPro and started porting the BMS maps into my ROM (OCD about things like that). Afterwards saved it, brought my stock, modified, and the canned BMS ROM to the computer to write. This is where headaches insued.
On the first attempt, it said communications failure, but the fuel pump kicked on. Red light on cable blinking away... I thought it had failed so I closed everything. And now the car won't start, so was apparently writing even though it gave an error. Couldn't get anything to write now, got the same thing over and over. The software was saying the computer was in recovery mode and I need to upload a working ROM.
So to fix it and get things working, in case anyone else runs into similar issues, I had to unplug the battery for a minute or so and try again. My car has about a 50/50 chance of a write starting correctly. If it fails off the get go, I had to unplug the battery and try again. But, if it progressed to step 1/2/3 everything works fine, 10 minutes later I have a BMS flash again. I was able to write the canned flash and the one I modified no problem, well, 50% of the time.
Still buggy for sure but props for this! Should be relatively smooth sailing now that I know what to expect! On a final note, I ended up using the BMS modified version 1.1 for all of this. The normal bbbflash beta was definitely more aggressive at trying to write it seemed, but it failed once at step 3. Terry's version whatever he changed seems a bit more stable for KLINE, may want to think about incorporating those changes into the main release.