The enhanced IPC in my 2013 XTS was beginning to fail, experiencing repeated resets/reboots while driving. Before replacing I wanted to try reloading all the calibrations to see if that might address the issue (if it was a software corruption issue and not hardware). Using TechLine Connect/SPS I downloaded the USB firmware to a USB key and plugged it into the Caddy. The update firmware prompt was displayed on the infotainment screen and I continued. At 75% the update failed leaving the IPC totally inoperable without any display.

I replaced the IPC with a salvage yard pull, since this was my original plan, updated the replacement IPC VIN and all is well in the Caddy world again.

 

On the bench, I am trying to revive the bricked IPC for funsies. Looking at the IPC calibrations after the failed firmware update, they are now:

Software Module Identifier          
   DID         Module ID  DLS
    C0          28345459   AE
    C1          23355861   BH
    C5          23125011   AB
    C6          22954399   AC
    C7          22876784   AC
    C8          22795224   AC
    C9          22937340   AB
    CA          22783207   AC
    40          22879020   AC
    69          23319822   AA
    71          84335758   AA
    74          84221442   AA

 

The working salvage yard pull has these calibrations:

Software Module Identifier          
   DID         Module ID  DLS
    C0          28345459   AE
    C1          23355861   BH
    C5          23125011   AB
    C6          22954399   AC
    C7          22876784   AC
    C8          22795224   AC
    C9          22937340   AB
    CA          22783207   AC
    40          22879020   AC
    67          23319820   AA
    69          23319822   AA
    71          23319824   AA
    74          23319826   AA
    76          23319828   AA

 

The problem I see is the calibration that SPS downloads for the bricked IPC USB update is 84221443 which loaded two out of four downloaded calibrations into DID 71 and 74 before failing. I tried updating twice.

 

- Is there a trick to obtain the calibrations for DID 67 and 71-76 that the working IPC is using? I've used three different VINs on SPS that I have for a 2013, 2014, and 2016 but none of them have calibration numbers even close to the working IPC.

- Any ideas on how to resurrect the bricked IPC?

- Is someone able to generate a VCI for these exact working calibrations?

 

Cheers!

Did you try to use VIN from donor vehicle (this one where u get new cluster)?

@Lyubomir Krastanov I did not try donor VIN since I have two other active paid SPS VINs that already give the same results. 

Share your and donor car ViN. Look like donor vehicle is totally different. Is not just higher number. 

If the IPC died while doing a firmware update that means the boot OS is not loading. One option would be to figure out which chip has the boot OS then remove the chip and try cloning the chip. Not an easy route. There could be a reset port on the circuit board but without having the schematics it will be difficult to find it. 

My VIN is 2G61V5S36D9163129 and the donor VIN is 2G61S5S30D9197799. The cars were manufactured about 3 months apart and have nearly identical RPO lists. This donor was selected specifically because they are nearly identical vehicles.

 

I may try removing and reading, saving, clearing the Flash ROM and trying again. Since DPS can communicate with the IPC, my hope is to obtain the calibration files that match the donor calibrations and try loading them manually through DPS first. 

Since DPS is still reading the IPC that means it's not entirely dead. Have you tried re-doing the USB firmware update?

I have recreated the USB drive from SPS twice and get the same failure at the same point, 75%.

Since the IPC was already failing, it could be possible that the reflash will never succeed until I am able to identify and correct the original failure. Perhaps a bad flash chip... 

I'm just terribly confused as to why the calibration numbers are vastly different than a working IPC from the same period.

have you tried load calibrations to the IPC with DPS? If is yes, what message have it in the log? i have a radio half-bricked (black screen), dps read the data perfectly, but i cant load calibrations because in the log have a 7F 34 22 (ConditionsNotCorrectOrRequestSequenceError) message when i try program.

In the radio i find a W25Q80DVSNIG 8Mb eeprom, and i think in this eeprom are stored the calibrations. but i dont have how read it....

You could also try updating the IPC firmware on the bench or with the BCM disconnected. The IPC depends a lot on the BCM. 

All this work is being done on the bench with the IPC, BCM, HMI, CD, Radio, and Infotainment console. 
 

My next attempt was going to be to build a DPS archive to try but ran out of time on the weekend. Does the order of calibrations matter in the archive? There are two calibrations out of four on the thumb drive that were not copied to the IPC and don’t know which slots they should be in if the order matters. 

Yes, the order matters. If those two calibration files are not from slot 01 ( slot 01 is always system calibration), You could try making two separate DPS archives and then flip those two calibrations around, I don't think swapping around those two calibration files will hurt the IPC.

12 hours ago, Arbe_gtc said:

have you tried load calibrations to the IPC with DPS? If is yes, what message have it in the log? i have a radio half-bricked (black screen), dps read the data perfectly, but i cant load calibrations because in the log have a 7F 34 22 (ConditionsNotCorrectOrRequestSequenceError) message when i try program.

In the radio i find a W25Q80DVSNIG 8Mb eeprom, and i think in this eeprom are stored the calibrations. but i dont have how read it....

The W25Q80 has HDRadio installed (RPO U2M) which includes the SAF3560HV/100, but the W25Q80 and SAF3560 do not (RPO U2K). Looking at the datasheet for the SAF3560 we see that it needs SPI2(W25Q80) so it's there.

1 hour ago, Mindaugas Cernius said:

I think the calibration is here.

 

W9812G6JH.pdf

19 minutes ago, Mindaugas Cernius said:

 

W9812G6JH.pdf 778.3 kB · 3 downloads

this is a SDRAM  i think the flash its the S29JL032J.

 

Too hard for me...

 

Maybe there are a method to force the boot to program it....

11 minutes ago, Arbe_gtc said:

 

Oh, sorry, that's not what I wrote.

Infineon-S29JL032J_32_Mb_4M_X_8_BIT_2M_X_16_BIT_3_V_SIMULTANEOUS_READ_WRITE_FLASH-DataSheet-v01_00-EN.pdf

24 minutes ago, Arbe_gtc said:

 

 

Maybe there are a method to force the boot to program it....

So far I haven't succeeded either. Eprom is bricked radio, I don't know if it is correct.

radio satelite usa eprom.bin

2 minutes ago, Mindaugas Cernius said:

So far I haven't succeeded either. Eprom is bricked radio, I don't know if it is correct. W25Q80DV

radio satelite usa eprom.bin 1 MB · 0 downloads

 

2 minutes ago, Mindaugas Cernius said:

So far I haven't succeeded either. Eprom is bricked radio, I don't know if it is correct.

radio satelite usa eprom.bin 1 MB · 0 downloads

I have readed the W25Q80 using a ch341 and i have the same file.

3 minutes ago, Arbe_gtc said:

I have readed the W25Q80 using a ch341 and i have the same file.

Are they identical?

Just now, Mindaugas Cernius said:

Are they identical?

yes

W25Q80 eeprom.bin

This 48 pin Tsop chip would be the chip that holds the VIN and maybe the boot OS. Was it the chip you dumped?

4 minutes ago, Troy said:

This 40 pin Tsop chip would be the chip that holds the VIN and maybe the boot OS. Was it the chip your dumped?

 

No this w25q80 for HD Radio

Is the radio you have the same as the one in this photo that uses the HMI 2.5 module? 

84278527 (U2M with HDRadio) +HMI 2.5