Autocom CDP Pro “Unable to read” and “Firmware version not load” Solution

Some reader said their Autocom CDP Pro was damaged,they got massage:Unable to read…and “Firmware version not loaded” problem,when they using their Autocom CDP Pro.Here i put the solution here,hope it helps!

 

Firstly,i need to thanks for titoun,his share this solution at:https://cartechnology.co.uk/showthread.php?tid=4258&highlight=delphi+ds150e

 

DELPHI DS150E Cars & Trucks Software Free Download

 

Solution:Change the FLASH 29F800BB AM.

Here is the CPU board after desoldering the flash ( old method: with heat gun ..)

Autocom CDP Pro “Unable to read” and “Firmware version not load” (1) Autocom CDP Pro “Unable to read” and “Firmware version not load” (2)

I will replace a Fujitsu AMD (with a slower maximum time access! )
Fujitsu :

Autocom CDP Pro “Unable to read” and “Firmware version not load” (3)

AMD:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (4)

Before mounting, a passage on universal programmer GQ -3X with socket,
to inject the firmware of 1-2011 version, before reassembly :

Autocom CDP Pro “Unable to read” and “Firmware version not load” (5)

Identification Chip:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (6)

Writing chip :

Autocom CDP Pro “Unable to read” and “Firmware version not load” (7) Autocom CDP Pro “Unable to read” and “Firmware version not load” (8)

Write verification :

Autocom CDP Pro “Unable to read” and “Firmware version not load” (9)

Firmware uploaded :

Autocom CDP Pro “Unable to read” and “Firmware version not load” (10)

Chip flash resoldered :

Autocom CDP Pro “Unable to read” and “Firmware version not load” (11)

and this is the VCI ready for a test vehicle …

Autocom CDP Pro “Unable to read” and “Firmware version not load” (12)

Now, no problem of Firmware : not loaded , when i change vehicle!

 

More:

Here is Delphi DS150E interface TCS CDP + microprcessor board that have suffered damage on STM32 microprocessor, FTDI FT232RL and a torn track among others:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (13) Autocom CDP Pro “Unable to read” and “Firmware version not load” (14)

The interface is no longer recognized on the USB port and the four LEDs will light up more!

After having desoldered micro STM32, SN74LVC2G04DBVT components is what one gets, you can see the layout of the track below the microprocessor:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (15)

Autocom CDP Pro “Unable to read” and “Firmware version not load” (16)

For FTDI FT232RL, there was a short circuit between the two power pins + 5Vdc USB; once connected, the component that hard put to heat (risk of breakage
USB port of the PC!)
So I replaced with a new one then I reprogrammed the EEPROM of this one with the soft FTprog by injecting the USB file CDP + _FT232R_ftdi.ept of Fantomel

Returning to our micro STM32: once the ordered components (FARNELL) resoldered and here is the result:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (17) Autocom CDP Pro “Unable to read” and “Firmware version not load” (18) Autocom CDP Pro “Unable to read” and “Firmware version not load” (19)

Now you must reload the firmware and serial No. 100251 into the microprocessor.
For the firmware two ways:
– For the PC USB port, with the micro BOOT 0 mode and injecting the program with little software FLASH loader demonstrator:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (20)

– For the J400 connector directly on the PCB and with ST link V2 programmer. The desired file will be injected with soft STM32 ST LINK utility v3.4.0.

Autocom CDP Pro “Unable to read” and “Firmware version not load” (20) Autocom CDP Pro “Unable to read” and “Firmware version not load” (22)

For the serial there is no choice, it is necessarily a ST LINK V2 programmer (I have not had time to try with a JTAG … but it must be possible to access
to the memory area with)
Moreover, as already explained Fantomel, attention to this area of ​​memory that can be updated …
The OTP100251 SWD.bin file will be injected with soft STM32 ST LINK utility v3.4.0 like this:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (23)

The STM32 micro power comes from the power prog 3,3Vdc ST LINK V2 therefore not need anything else.
Connection to the microphone STM32, the LEDs light up blue and then 3 times with 3 flashes of red LEDs …

Autocom CDP Pro “Unable to read” and “Firmware version not load” (24) Autocom CDP Pro “Unable to read” and “Firmware version not load” (25) Autocom CDP Pro “Unable to read” and “Firmware version not load” (26)

Then we make a comparison of what’s in memory and serial file to inject:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (27)

It injects the serial file indicating the start address is then 0x1FFF7800 start:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (28)

And we see that the area has been written:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (29)

Finally, it disconnects from the micro STM:

Autocom CDP Pro “Unable to read” and “Firmware version not load” (30)

Finally we test the interface in WoW software with firmware updating and then under Delphi or Autocom (depending on preference) to check the serial.