Hey, so I would like to share my experience of CIC programming with ICOM ISTA-P, after a new FRM installation, especially for tips of how to solve CIC Programming Aborted Mode with ISTA/P.
Background information:
Was trying to install a new FRM (old one bricked itself, was doing some basic diagnostics and the voltage dropped too low I guess). Everywhere I read said that the easiest way to install a new FRM is to just use ISTA/P in expert mode and it will run it through the programming and coding necessary. I bought a nice power supply to prevent any more bricked modules, and figured I’d give it a shot.
I was just blindly clicking through ISTA/P (first time using it) and hadn’t realized that its test plan also included programming and coding a bunch of other modules besides the FRM, some of which were on the MOST bus. I only have a K+D/CAN cable and an ICOM emulator, so when it started programming the CIC nothing really happened (that, or it was happening very slowly). Eventually, my battery died because the power supply had actually slipped off one of the leads. Mega fail!
Now, ISTA/D says that the CIC is in programming aborted mode.
Useful tip i used:
In tool32 run the job:
flash_programmier_status_lesen
My bet is it will return 7 – programming session active for CIC.
I guess as nothing happened during the ISTA flash your CIC is stuck in bootloader mode.
CIC is made up of 3 parts which must be flashed in correct order (obviously ISTA does this automatically but I’ll explain it as it may help you solve the problem).
63 -> 62 -> A0
The numbers refer to ECU addresses so…
63 = MASK/CIC
62 = MOSTGW
A0 = CIC
Bootloader / program / data
I think only an ICOMA+B / Opps unit will you be able to recover this CIC by reflashing with ISTAP. Only 62 can be flashed with K+DCAN. The complete package requires MOST (ICOM B) correctly configured.
Hope this helps…
(case + suggestion from e90post forum, uobdii.com will not responsible for what you will try)
