[russellg]

Hello, I'm stuck and I wonder if anyone can assist.

I have factory CCC and i'm trying to upgrade to CiC in my R56 Pre-LCI.

I removed the CCC and retrofitted a Champ2 headunit, everything worked initially incuding DAB, bluetooth and USB (via retrofitted combox) but I wanted to flash to latest firmware to use intel123's SWT Patcher so that I can have navigation enabled too.

I have been tryng to upgrade the firmware now for about three months almost non-stop and im at the end of my tether. I cant use ISTA/P as my car is pre-LCI.

However, I bought and original ICOM Next A&B, but flashing is painfully slow (approx. 72hrs for address, 63, A0 and 62 is about 24hrs). The car has been off the road for three months.

The Combox CMEDIAR 36 flashed first time with no problems, but I have tried flashing the CiC 63, 62, A0, with limited success in both comfort mode and expert mode on three different laptops running WinKFP, updated with SP-Daten.v3.58.1 using BMW Coding Tool v 2.5.0.

I've tried in order 63, 62, A0 and 62, 63, A0 with MOST_Async_ab625, MOST_Async, MOST_CTRL and OBD_625.

Currently this my UIF looks like from INPA: -

36 TEL/MULF OKAY 9257165 TL02970 09.12.2017
62 MOSTGW OKAY 9290218 TL02970 30.01.2018
63 MASK/CCC OKAY 9290212 TL02970 06.02.2018
92 VIRTSG92 OKAY 9233590 0000000 01.01.2008
9B VIRTSG9B OKAY 9248629 0000000 01.01.2008
A0 CCC OKAY 9290230 TL02970 03.02.2018

I've tried to flash: -
CH63F1
CH62F1
CHA0F1

After flashing I tried to read CHAMP in NCS Expert but recieve the ECU_CONDITIONS_NOT_CORRECT error, ISTA/D also reports the ECU as partially responding.

So i'm at a loss.

So I guess the next step is:-

Can anyone assist or at least tell me what 92 VIRTSG92 and 9B VIRTSG9B is and why they do not update after updating 63, 62 and A0?

Or if you can offer anyt other guidance any help is appreciated!

[hojo29]

These are virtual controllers
And CIC flashing with Winkfp lasts no 72 hours.

[russellg]

These are virtual controllers
And CIC flashing with Winkfp lasts no 72 hours.

Thanks, do you know if they are updated automatically when you update 63,62 or A0?

I beleive the slow flashing may be to do with using an orignal ICOM NEXT.

[hojo29]

The 3 control unit addresses are flashed and that was it.
The virtual ECUs do not matter and are not updated.
And with ICOM, CIC flash takes about 2 - 3 hours.

[russellg]

Thats great, thanks for that.

So it could be possible that the flash has worked sucsessfully?

If there anythiung I need to do to the CiC after zUSB programing okay to boot it up?

I attached a screen grab in my original post of the error I get when I try to read the CHAMP ECU in NCS expert, but maybe I have missed a step after flashing with WinKFP?

[blax123]

You cannot use Intels Patch for Champ2 (CIC-MID), its just for CIC (High)

[russellg]

You cannot use Intels Patch for Champ2 (CIC-MID), its just for CIC (High)

Disaster!

Now I am in double trouble. Navigation is the long term goal, but in teh short term i'lll be happy if I can get the CiC working again.

[blax123]

You cannot use Intels Patch for Champ2 (CIC-MID), its just for CIC (High)

Disaster!

Now I am in double trouble. Navigation is the long term goal, but in teh short term i'lll be happy if I can get the CiC working again.

first of all, update the firmware of your icom next. 3.15 is the newest.
then, the fsc story, you can solve it with an fsc emulator/can filter. thats not the problem.
Update sequence is 63, 62, a0.

if it still does not work, then we gonna try it via ISTA-P
for ista-p you have to change this information:

start tool32; load r56.prg; i_stufe_lesen and notice anyhwere this information (very important!).
then go to i_stufe_schreiben and in the argument field load this:
R56x-10-03-501; R56x-10-03-501; R56x-10-03-501
or this
R056-10-03-501; R056-10-03-501; R056-10-03-501
then start ista-p and check if cic is showing and measure plan etc.

[russellg]

Thanks blax123

Current firmware is as below, downloaded from AOS around November 2017, but I don’t know if there is a later version.

Firmware: -
Current PACKAGE IMAGE version: 03.15.00
Current SYSTEM IMAGE version: 01.01.00
Current APPLICATION IMAGE version: 01.01.00

I have previously completed the WinKFP update in order of 63, 62, A0 as you have detailed but still it have not been able to get the CiC to boot (cooling fan on permanently)

I am willing to try the ISTA/P process, will this still work even though my vehicle is pre-LCI and did not originally come with CiC? ( for some reason I wasn’t able to change the data in my VO until later than approx. #0608 from original #0606)

On a side note I did source and install a CAN nav emulator but it would allow nav to work for a few seconds, hence why I attempted the CiC flash to try intel123’s exploit. If I realised it was not suitable for CiC-Mid back then I would have tried another emulator fist!


Thanks for your help so far. I will try the Tool 32 and ISTA/P steps this evening and revert.

[russellg]

Okay,

I loaded up Tool32 and ran r56.prg I_STUFE_lesen, and made a note of the I_STUFE_WERK, I_STUFE_HO and I_STUFE_HO_BACKUP values.

I_STUFE_WERK = R056-06-12-511
I_STUFE_HO = R056-10-03-501
I_STUFE_HO_BACKUP = R056-08-09-510

However I am presented with: -

JOB_STATUS = ERROR_ARGUMENT when I run
apiJob("R56","i_stufe_schreiben","R056-10-03-501; R056-10-03-501; R056-10-03-501","")

or

apiJob("R56","i_stufe_schreiben","R56x-10-03-501; R56x-10-03-501; R56x-10-03-501","")


I tried with Base and Diagbus.

Have I missed a step?