VAG-COM/VCDS EVERYTHING

[Polocarr]

Impossible. This interface is total crap. Firstly, no ATmega162 chip there. Secondly, there is MCP2561 chip which goes into sleep mode and there's no way it could be compatible with this setup. Besides, I really doubt that your 17.1.3 works correctly (License Valid is NOT an indicator).

All you can do with the above interface is this:
-Return it to the seller and request for a refund if you bought it recently;
-Keep it for spare parts;
-Give it as a gift for a neighbour's kid.

And for yourself you could buy some quality one. I have posted at least 10 times in this thread on where to get quality ones for affordable price, do some search.

Thank you hid3
Currently,it works normally on 17.1.3 🤔
I'm thinking of buying an OBDeleven pro, what do you think?
Multi-Quote This Message

[dudzsi]

Hello!
1 and 4 do not buy it! Bad can not update! Magyar meg a legújabb is megy vele 6.3 loaderrel.

[hid3]

It all depends on yours needs and use case scenarios. If you intend to use it on your personal car just for simple tasks, OBDeleven is a valid choice.
If you prefer \/(DS, you can buy a quality hardware for it.
And if you run a workshop or work on new MQB cars, you'll definitely find VCP more useful than \/(DS

[Polocarr]

OBDeleven pro is it NOT compatible with MQB A0 vehicules? 😨

[hid3]

Not sure, I won't speculate that fact because I've not used a lot (just like 10 minutes of time total). But have in mind these things about OBDeleven: a) it's still fairly new thing (Made in Lithuania BTW); b) their support sucks; c) there's little to no community of OBDeleven so getting advice/support/guidelines from somebody might not be straight forward.

[rivit]

Can I use internet with loader from 6.1 zip?

[M0rtuuS]

Hello all,

I'm trying to flash a VAG171 cable. See pictures below for exact hardware.
DSC03995.JPG DSC03998.JPG
Chips that I can indentify:
Photo 1:
Atmega 162 16 AU
NXP A1050/C
MCP2515
FTDI 232RL

Photo 2:
2x L9637D
Atmel ATF16V8B 15JU 1628
Unbranded chip which reads Y 5FAQ

With HWtype.exe it identifies as:
FW Version : 1.96 HW Version : 0x46
Identification : ROSS-USA
When i try to write to it with EEWriteLang.exe it returns: Not in bootloader mode.

Thus I tried to use an external programmer, I currently only have an Arduino Uno flashed as avrisp.
At first it gave me a device signature mismatch. When I add the command -F to avrdude.exe it starts flashing.
Except it gives an error while verifying the EEPROM. See code block below.

C:\Users\Jochem\Downloads\VCDSLoader_v6.3>avrdude.exe -F -p m162 -c arduino -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

avrdude.exe: AVR device initialized and ready to accept instructions


Reading | ################################################## | 100% -0.00s


avrdude.exe: Device signature = 0x1e950f (probably m328p)
avrdude.exe: Expected signature for ATmega162 is 1E 94 04
avrdude.exe: erasing chip
avrdude.exe: reading input file "Flash1.96_HW_0x46.bin"
avrdude.exe: writing flash (16306 bytes):


Writing | ################################################## | 100% 2.73s


avrdude.exe: 16306 bytes of flash written
avrdude.exe: verifying flash memory against Flash1.96_HW_0x46.bin:
avrdude.exe: load data flash data from input file Flash1.96_HW_0x46.bin:
avrdude.exe: input file Flash1.96_HW_0x46.bin contains 16306 bytes
avrdude.exe: reading on-chip flash data:


Reading | ################################################## | 100% 2.13s


avrdude.exe: verifying ...
avrdude.exe: 16306 bytes of flash verified
avrdude.exe: reading input file "eepromavr_HW_0x46.bin"
avrdude.exe: writing eeprom (512 bytes):


Writing | ################################################## | 100% 1.76s


avrdude.exe: 512 bytes of eeprom written
avrdude.exe: verifying eeprom memory against eepromavr_HW_0x46.bin:
avrdude.exe: load data eeprom data from input file eepromavr_HW_0x46.bin:
avrdude.exe: input file eepromavr_HW_0x46.bin contains 512 bytes
avrdude.exe: reading on-chip eeprom data:


Reading | ################################################## | 100% 0.81s


avrdude.exe: verifying ...
avrdude.exe: verification error, first mismatch at byte 0x0000
             0xb1 != 0xff
avrdude.exe: verification error; content mismatch


avrdude.exe: safemode: Fuses OK (E:00, H:00, L:00)


avrdude.exe done.  Thank you.

After this I disconnected (scratched paths leading away from) pin 34 and 35 of the Atmega162 as suggested in the info.pdf file. Although trying to program still gives the same result as above.

Does anyone have a clue what is happening here and how I can succesfully flash my cable?
Thank you so much!

Edit: All while having an external 12volt source connected.

[hid3]

LOL. Where it says "disconnect" pins 34 & 35 from GAL? You have just spoiled a perfectly good interface.
Solder those paths back ASAP.

Further, can you post a picture of the complete setup how it looks when everything is connected, powered up and prepared for flashing?

[networkers]

Does anyone have a clue what is happening here and how I can succesfully flash my cable?

It seems that your programmer does not detect the Atmega 162 correct.

avrdude -p m162 -c usbasp

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9404 (probably m162)

avrdude: safemode: Fuses OK (E:F9, H:DA, L:CD)

avrdude done.  Thank you.

And the same in "verbose mode":

avrdude: Version 6.2
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

                 Using Port                    : usb
         Using Programmer              : usbasp
         AVR Part                      : ATmega162
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PA0
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           flash         65    10   128    0 yes     16384  128    128  4500  4500 0xff 0xff
           eeprom        65    20     4    0 no        512    4      0  9000  9000 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0 16000 16000 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0 16000 16000 0x00 0x00
           efuse          0     0     0    0 no          1    0      0 16000 16000 0x00 0x00
           lock           0     0     0    0 no          1    0      0 16000 16000 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00

         Programmer Type : usbasp
         Description     : USBasp, http://www.fischl.de/usbasp/

avrdude: auto set sck period (because given equals null)
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9404 (probably m162)
avrdude: safemode: hfuse reads as DA
avrdude: safemode: efuse reads as F9

avrdude: safemode: hfuse reads as DA
avrdude: safemode: efuse reads as F9
avrdude: safemode: Fuses OK (E:F9, H:DA, L:CD)

avrdude done.  Thank you.

[M0rtuuS]

LOL. Where it says "disconnect" pins 34 & 35 from GAL? You have just spoiled a perfectly good interface.
Solder those paths back ASAP.

Further, can you post a picture of the complete setup how it looks when everything is connected, powered up and prepared for flashing?

Oops , I just resoldered them before I had to go to work. But I don’t understand why it indentifies as 0x46 and the info pdf says 0x46 is visually recognized by having those pins not connected? I thought it had to do with the auto reflash that some cables do. Therefore I cut those traces.
After work I’ll take a picture of my flashing setup. Thanks for the help so far.

It seems that your programmer does not detect the Atmega 162 correct.]

Thats what it seems like. Although I have no idea what causes this. Is an Arduino simply incapable of flashing this chip or is it that the wrong signature fuses are set on the Atmega162?

[ouldsmobile]

Thanks to all who have contributed to this project and thread. I just finished programming my HQ clone cable. For those of you who may not already have a USBASP or similar programmer. An arduino can easily be used for such purposes. The sketch needed is built in to the examples menu of the arduino IDE software. Just go to File->Examples and select ArduinoISP, then just upload code to your Arduino board.

The following table will show the pinouts for various Arduino boards. I used Duemilanove board. Pin 10 was reset and I used the 5V/GND outputs from the board to power the cable.

Arduino / Genuino Board	MOSI	MISO	SCK	Level
Uno or Duemilanove	11 or ICSP-4	12 or ICSP-1	13 or ICSP-3	5V
Mega1280 or Mega2560	51 or ICSP-4	50 or ICSP-1	52 or ICSP-3	5V
Leonardo	ICSP-4	ICSP-1	ICSP-3	5V
Due	ICSP-4	ICSP-1	ICSP-3	3,3V
Zero	ICSP-4	ICSP-1	ICSP-3	3,3V
101	11 or ICSP-4	12 or ICSP-1	13 or ICSP-3	3,3V
MKR Family	8	10	9	3,3V

I used the following command to program the Atmega162 in my cable:

avrdude -p m162 -c avrisp -P COM5 -b 19200 -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

Note: You may have to change "-c avrisp" to "-c arduino" depending on your board. I have seen both mentioned on various sites with respect to programming using an Arduino as the programmer. avrisp worked for my setup though. Also change filenames and fuse settings for your hardware type. My cable was type 46. :-)

Hope this helps someone! My little contribution.

[stonecoldro]

@ouldsmobile: it is very interesting what you've mentioned to use a Arduino board as a programmer.

Can you please post a photo of the connections you've made on the vcds PCB? I'm interested to see what kind cables you have used. Also, did you use external 12V? or just relied on the 5V that the Arduino board supplies - again: a photo is worth a thousand words

Thanks!

[M0rtuuS]

As promised the pictures of my setup.

photo_2018-04-05_12-20-26.jpg photo_2018-04-05_12-20-31.jpg photo_2018-04-05_12-20-35.jpg

I don't get it anymore. I used the command ouldsmobile suggested after a couple of tries it detected the signature right and succesfully flashed flash and eeprom.
After that i tried to use EEwritelang, but it gave an error halfway through. Now the LED on the cable stays off.
So I tried to reflash it with the Arduino, but no matter what it now detects the signature as 0x000000. Only once during maybe 10 tries it detected the signature correct, but on that try it failed to verify the eeprom exactly like before.

Thanks!

EDIT:
After having no power what so ever on the cable for a while, because I was doing something. I tried to flash it one more time now.
The LED came on again, first red then green. And it flashed correctly again..
Could this be a heat issue? The 7805 gets pretty warm to the touch after being connected to 12v for a while? Or are there capicitors on there which take a while to decharge?

VCDS 18.2.0 says its license is valid. Testing gives everything ok, except for can which is not ready. But that could be because the cable isnt connected to the car, 12v from bench supply only. Car with can is not here right now so I will report later on that.

[hid3]

So if you power it with +12V power source, then no need to power up with +5V VCC.
If that still won't work, I'd switch to the classic USBasp adapter.

[adicristi]

Hi all,

I have a VCDS cable from CN. I updated this interface from 17 to 18 and of course the clone was destroyed. I reflash with USBASP my VCDS cable and now it works wiith 17.8.0 but I cannot scan an Audi A4 B8.
The loader used is v2 from Kolimer.
My question is. Should I update VCDS cable to v6 and use VCDS 18.1 ? If I broke something..Can I repair again?
Thank you!
P.S. My interface use 1.96 firmware and is type: 0x46.