VAG-COM/VCDS EVERYTHING

[zed1011]

Hi, I have vcds like foto atmel mega 162 Is this a good cable?20190313_144227.jpg20190317_182507.jpg20190313_144247.jpg20190317_180033.jpg

[alexm1]

Where is the "Atmel mega" on your pcb? Draw a circle around it and take a closer picture.

[LostAngel]

In the first photo, it is hard to see at the top ATMEGA 162 16 AU
Apparently the interface is a good one, I think!
in the first photo, it is hard to see at the top ATMEGA 162 16 AU

[kaalis]

Top middle 4x11 pin chip in first picture. Wow, where are everybody getting these pieces of %#^#% out of?
Picture is large enough to zoom in, but too bad quality and no focus.

[zed1011]

Hello, I added more photos to my post now more accurate Is this cable good or different from Atmega 162?

[alexm1]

In the first photo, it is hard to see at the top ATMEGA 162 16 AU
Apparently the interface is a good one, I think!
in the first photo, it is hard to see at the top ATMEGA 162 16 AU

You updated your post, at first you did not post all the pics, now I see clearly "Atmel Mega".
So, that IC should replace the weel known Atmega162?

......but I never seen before this type of cable and the the "real" Atmega162 looks/behave different and for sure you can not use dumps shared here. But if you manage to update this cable, came back and tell us how you did it.

[zed1011]

I'm asking you all because for the first time I see this type of cable, I've always had an older classic version of Atmega 162
I updated this cable from version 18.2.1 to version 18.9.0 through the v7.2 charger from my colleague KOLIMER
The cable works fine without malfunctioning.

[liviudiaconu]

Ia a "44" HW Atmega 162-16MU

[Fabio89]

Anyone has a link to download VCDS 18.2.1 English ? Thanks

[bg17aw]

Hello guys,


My interface runs VCDS 17.1, I am trying to update to 18.9 or whichever is the latest working on my config:
ATMEGA162 16AU 1648H + FT232RL + L7805CV + ATF16V8B + MCP2515 IST 05D 1721 can controller + 2 x L9637D GK725 + NXP A1050/C JQP000 D722


Firmware is 1.96, VAGCOM_HWType.exe says HW is 0x46, and bootloader is disabled (unfortunately!)


It has a 6 pin programming interface (connectons to pins 1-6 on the ATMEGA chip) and 2 jumpers (see pics).


0) Is there a way to make a backup of everything before I begin experimenting? Using either the programmer or not

1) is there a way to enable bootloader?

I do have a USBASP programmer (but never used it before).

2) If yes, is the way I connected the 12V supply correct? PIN 4+5 I shorted to Ground, and pin 16 to 12V

3) How to unlock bootloader? From what I understand, this will help a lot with future updates?

4) Do I need to fix the VID and PID? VID is 0403 but PID is FA24 (does it need to be FA20?)

5) Tried VAGCOM_EEWriteLang.exe (took the two jumpers off) but got error "Not in Bootloader mode", so USBASP seems the way to go.

6) Any chance of some step-by-step instructions on how to put the interface into bootloader mode and update using USBASP?
I did read info.pdf from the 7.2 pack, but no idea what avrdude is (it is not in the pack!), what FuseBits means etc
The instructions should be more noob-proof I think

Thank you!

[kaalis]

you search google for avrdude download and save avrdude.exe and avrdude.conf in unarchived directory with loader files, connect cable with usbasp, connect 12v, run appropriate cmd file according to your real hardware (not hwtype, check info.pdf), put loader exe into vcds directory and run it. Just take some more days reading this topic and eventually you will get answers to all your questions without even asking. You have made a good progress already.

Is something wrong with 17.1.0 version?

[bg17aw]

0x44: ATmega 34 and 35 pins are connected to GAL pins 5 and 4 accordingly and GAL pin 9 is connected to some pin on the FTDI (use multimeter in diode testing mode to confirm).
0x46: no connection from ATmega 34 and 35 pins exist to any pins of GAL and GAL pin 9 is NOT connected to FTDI and GAL pin 5 is connected to FTDI.

GAL pin 5 should be connected to what pin on FTDI?

ok, seems like i have a 0x44 after all... not 0x46 as VAGCOM_HWType reported

[bg17aw]

your real hardware (not hwtype, check info.pdf)

after hours of fiddling with the multimeter, seems like I have a 0x44 after all, although VAGCOM_HWType.exe was reporting 0x46!

[hid3]

Hours spent for what only takes a few moments to check? Wow...
HWType tool reports what has been flashed into the chip - it has no ability to check actual harware configuration. Since chinese incorrectly flashed your cable as 0x46, that's why it reported like that

[bg17aw]

you search google for avrdude download and save avrdude.exe and avrdude.conf in unarchived directory with loader files, connect cable with usbasp, connect 12v, run appropriate cmd file according to your real hardware

I executed avrdude succesfully, installed vcds 18.9 and ran kolimer loader, however, the drivers refuse to load:
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

The VID and PID remained the same, 0x403 and AF24

any ideas? i was thinking to reprogram interface with 0x46 version