VAG-COM/VCDS LATEST DUMPS

[Azorath]

I need this in my life..

my cable only ave FT343BL and LM393 as IC's..

[Fabius72]

Hello, I'm trying to get my cable working, so I'm here to try with your dump files.
Firmware version 1.96
VCDS 18.9.0
FT232RL - VID 0403 PID FA24
PALCE 16V8H -7JC/5

Cable recognized by the software but corrupted in someway in an old eeepc laptop with XP and never connected to internet nor updated.
I've successfully tried to flash Atmel162 via FT232H ISP programmer and command line, but I didn't know about the e2prom & fuse roles, so the interface can't pass self test.
Now I've understood that I must flash with firmware and eeprom files at the same time.
I know I must read a bit more here before try other things, but can I flash old version in my interface, since I would connect to my old Audi A3 8L1 year '02?
Or maybe I can find the eeprom hex file somewhere?
Thank you for your help.
Fabio

[Fabius72]

Sorry, I forgot to insert some pictures:

Attachment 1004929
Attachment 1004930
Attachment 1004931photo_2024-01-07_18-48-46.jpg

photo_2024-01-07_18-48-45.jpg

photo_2024-01-07_18-57-15.jpg

[Fabius72]

Hello!!! There are VCDS 18.9 (soft + dump ATMEGA162+photo of fuse settings), if somebody needs

I was looking for this version and found it, thank you very much!
I though I was lucky, but unfortunately... flashed with avrdude as I normally do with other Atmel uController (Arduino's world) and everything seems to be ok, but the led stay off when connected to the car, no connection. Uhhh

This is the output from the linux terminal:

avrdude -c FT232H -p m162 -P /dev/ttyUSB0 -b 234375 -U flash:w:flashATM162.BIN:r -U eeprom:w:eepromATM162.BIN:r -U lfuse:w:0xcd:m -U hfuse:w:0xda:m -U efuse:w:0xf9:m -U lock:w:0xcc:m
avrdude warning: mosi is deprecated, will be removed in v8.0, use sdo [/home/fabio/.avrduderc:17]
avrdude warning: miso is deprecated, will be removed in v8.0, use sdi [/home/fabio/.avrduderc:18]
avrdude warning: programmer FT232H overwrites previous definition /etc/avrdude.conf:735. [/home/fabio/.avrduderc:4]
avrdude: AVR device initialized and ready to accept instructions
avrdude: device signature = 0x1e9404 (probably m162)
avrdude: Note: flash memory has been specified, an erase cycle will be performed.
To disable this feature, specify the -D option.
avrdude: erasing chip

avrdude: processing -U flash:w:flashATM162.BIN:r
avrdude: reading input file flashATM162.BIN for flash
with 16382 bytes in 1 section within [0, 0x3fff]
using 128 pages and 2 pad bytes, cutting off 2 trailing 0xff bytes
avrdude: writing 16382 bytes flash ...
Writing | ################################################## | 100% 2.94 s
avrdude: 16382 bytes of flash written
avrdude: verifying flash memory against flashATM162.BIN
Reading | ################################################## | 100% 2.30 s
avrdude: 16384 bytes of flash verified

avrdude: processing -U eeprom:w:eepromATM162.BIN:r
avrdude: reading input file eepromATM162.BIN for eeprom
with 512 bytes in 1 section within [0, 0x1ff]
using 128 pages and 0 pad bytes
avrdude: writing 512 bytes eeprom ...
Writing | ################################################## | 100% 4.68 s
avrdude: 512 bytes of eeprom written
avrdude: verifying eeprom memory against eepromATM162.BIN
Reading | ################################################## | 100% 0.51 s
avrdude: 512 bytes of eeprom verified

avrdude: processing -U lfuse:w:0xcd:m
avrdude: reading input file 0xcd for lfuse
with 1 byte in 1 section within [0, 0]
avrdude: writing 1 byte lfuse ...
avrdude: 1 byte of lfuse written
avrdude: verifying lfuse memory against 0xcd
avrdude: 1 byte of lfuse verified

avrdude: processing -U hfuse:w:0xda:m
avrdude: reading input file 0xda for hfuse
with 1 byte in 1 section within [0, 0]
avrdude: writing 1 byte hfuse ...
avrdude: 1 byte of hfuse written
avrdude: verifying hfuse memory against 0xda
avrdude: 1 byte of hfuse verified

avrdude: processing -U efuse:w:0xf9:m
avrdude: reading input file 0xf9 for efuse
with 1 byte in 1 section within [0, 0]
avrdude: writing 1 byte efuse ...
avrdude: 1 byte of efuse written
avrdude: verifying efuse memory against 0xf9
avrdude: 1 byte of efuse verified

avrdude: processing -U lock:w:0xcc:m
avrdude: reading input file 0xcc for lock
with 1 byte in 1 section within [0, 0]
avrdude: writing 1 byte lock ...
avrdude: 1 byte of lock written
avrdude: verifying lock memory against 0xcc
avrdude: 1 byte of lock verified

avrdude done. Thank you.

What goes wrong? Am I missing something? It is all so unclear and chaotic all about vcds cables for me...

EDIT: if I re-flash the previous 1.96 firmware I've downloaded yesterday, the led works normally: red after interface plugged in and became green after a second, but still "Failed self test"
Any advice? Thank you.

[Fabius72]

Problem solved.
After a lot of frustration the interface is alive and I share with you what works for me:
for my interface the firmware that now is running was found in the downloaded VCDSLoader_v9.2 folder: (EDIT: the link is https://sidicer.lt/files/VCDSLoader_v9.2.zip )
Flash1.96_HW_0x44.bin
eepromavr_HW_0x44.bin

So the command to upload the files on the atmel chip from the command line (linux in my case), by an usb-isp converter (in my case an FT232H which is good for me) is:
[fabio@fabio-PC ~]$ avrdude -p m162 -c FT232H -e -U lock:w:0x3f:m -U efuse:w:0xf9:m -U hfuse:w:0xdc:m -U lfuse:w:0xcd:m -U flash:w:Flash1.96_HW_0x44.bin:r -U eeprom:w:eepromavr_HW_0x44.bin:r

At this point, following the VCDS installing guide, like the four days gone, the interface didn't work again, but... I decided to make a thing:

This is the "official" instructions about "How to install VAG 18.9 in the PC":
1...
2...
3...
4. First time to plug cables into the PC, wait a while to run VCDSLoader.exe. Click Options to run the self-test, and then click Save Data.
5. Turn off all vcds software, (***) plug in your car, and run VCDSLoader.exe again.

*** NO! Before plug the cable in your car, we also need to disconnect USB from computer port!
Then, connect the interface to the OBDII port, than reconnect the cable to the USB and finally run VCDSLoader.exe

After this second test, the interface was finally found, connected to the car and... registered!
Good luck!

Fabio

[imed88]

I bought this cable on a Chinese site aliexpress vag commander 5.5 but I cannot install
the driver on win 10 and if I install with other files it displays serial
to port but the vag commander software does not detect it