VAG-COM/VCDS EVERYTHING

[predki]

Hello . It can be fixed so it shows in windows.

[Roma77]

Hello . It can be fixed so it shows in windows.

The archive that I gave you above restores serviceable scanner with a bad pid xxxх vid xxxx
In your case there may be physical problems with both the D+, D- cable and the 232 chip or its strapping components. (flashing IC 93cXX for 232BM,BL)
after recovery, you need a driver for USB <--> Serial vid 0403 pid 6001 (google search for your system)
If you want I can try to help you on timeweaver 14
If this suits you, send me an ID and password in private messages
Just please publish the photos of your PCB from two sides in good quality, I need to know what's inside.
A request to all who need help, the more you write the information for whatever reason the scanner broke and give good photo cards on both sides, the faster other users will tell you how to fix it.

[da78n]

I need help to restore my interface.
I had FW 1.94 & HW 0x46.

After disconnecting the STC chip i flashed the interface with USBasp (loaded the project from archive) and the result was ok.

If i start the VCDS on the desk (not in the car) i receive Interface Found, Type Ross-Tech HEX-USB and Licence status Invalid / Unauthorized.
If i start the VCDS connected to the car i receive Interface Not Found and Licence status Invalid / Unauthorized.

VAGCOM_HWType.exe is reporting ok FW 1.96 & HW 0x46.
VAGCOM_EEWriteLang.exe is not working so only USBasp programming is working.

Where is the problem ?

[alexm1]

Did I missed the part about the loader???? Or you did not use it?


L.E.
About VAGCOM_HWType.exe, I think you have a old version, the last vers. can choose automatic VID/PID and I think here is the part where you are mesing things wrong

[da78n]

I used the loader v7.2
But i also tested the VCDS-Release-18.9.1.

[alexm1]

...and I do not see the pics with PCB with the side where Atmega is placed

[da78n]

[alexm1]

Can you see it in Dev Manager after usb is plugged in? Rigth click on it Properties& Hardware Id

[da78n]

Yes, it's in Device Manager.

[liviudiaconu]

@dan78: Your AVR nothing wrote.
Let me explain: Your settings are F9DCCD. In the right side is the same? If YES..NOT OK.
That mean you set "44" version. Even you opened "46" inside programmer. If the writing is OK on HWType you must obtain in this case "44" or "wrong info".
One by another, your descriptor is RossUSA. Wrong! K0l1 use another descriptor.
So, you did something wrong!
My advice is desolder IC8 and D7 and after try again.

L.E. First photo i see wires from programmes fixed with rubber-band.
In second atmega photo i don't see on pins 1-4 soldering-trace. So..where you soldered programmer's wires?
1-4 = MOSI-MISO-SCK-RESET.

[da78n]

ATMEGA pin 1: MOSI ( pin 1 on USBasp )
ATMEGA pin 2: MISO ( pin 9 on USBasp )
ATMEGA pin 3: SCK ( pin 7 on USBasp )
ATMEGA pin 4: RESET ( pin 5 on USBasp )

I zoomed the picture so wires can be visible now.

After flashing the FW version changed from 94 to 96 (so something got inside ATmega i guess).

And Progisp reported Erase, Writte flash, Verify Flash, Write Eeprom, Verify Eeprom, Write fuse, Lock chip, Successfully Done!

I will recheck those bits and try to reflash again.

[da78n]

I tried to program again now using the AVRdude.
The result:



And again with Progisp v1.72
The result:



And again with AVRdude.
avrdude -p m162 -c usbasp -e -U flash:w:Flash1.96_HW_0x46.bin:r -U eeprom:w:eepromavr_HW_0x46.bin:r
-U lock:w:0x3f:m
-U efuse:w:0xf9:m
-U hfuse:w:0xda:m
-U lfuse:w:0xcd:m

The result:





But the VAGCOM_EEWriteLang.exe is still not working.

[Jerak]

Yes. Undo the date on the laptop up to the release date of vcd$18.2.0.

Yah, can't do that. Ok thanks

Yes. Just use 18.9.0 or 18.9.1

So when Ross updates the popup will return?

[Roma77]

I tried to program again now using the AVRdude.
The result:
And again with Progisp v1.72
The result:
And again with AVRdude.
avrdude -p m162 -c usbasp -e -U flash:w:Flash1.96_HW_0x46.bin:r -U eeprom:w:eepromavr_HW_0x46.bin:r
-U lock:w:0x3f:m
-U efuse:w:0xf9:m
-U hfuse:w:0xda:m
-U lfuse:w:0xcd:m

The result:
But the VAGCOM_EEWriteLang.exe is still not working.

1 photo - an eeprom empty atmel162, 2 photos - an eeprom repaired, 3 photos - its eeprom is correctly sewn. Will you delete IC8 or will it be a problem.

[da78n]

So you suggest to completely remove the IC8 (STC), to unsolder him from the board ?
The interface is working without the STC or i have to solder him again after writing the firmware?
What is that STC doing ?