VAG-COM/VCDS EVERYTHING - Page 408
Register
Page 408 of 844 FirstFirst ... 308358398403404405406407408409410411412413418458508 ... LastLast
Results 6,106 to 6,120 of 12650
  1. #6106
    Newbie mu95f's Avatar
    Join Date
    Apr 2018
    Posts
    8
    Thanks Thanks Given 
    9
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    Hello guys,
    I've followed this topic but I couldn't find exact information for update my VCDS.
    So, I've a VCDS 10.63 cable chinese think. I've check the Firmware (1.83) and Hardware (0x46) version with VAGCOM_HWType.exe.
    If I try to program it with VAGCOM_EEWrite.exe, I receive the message "NO IS BOOTLOADER MODE".
    On the interface are mounted:
    Atmel 162 16AU 1025H
    Atmel 1008 ATF 16V8BQL-15SU
    MCP2515
    MPC25511
    FTDI FT232RL
    I would like to know what steps to take to upgrade the cable to the latest multilingual version.
    Which software to use, which interface to program it.
    There is a guide that you can consult.
    Best Regard1.jpg2.jpg

  2. #6107
    DK Veteran

    Join Date
    May 2010
    Location
    EU
    Posts
    380
    Thanks Thanks Given 
    218
    Thanks Thanks Received 
    188
    Thanked in
    126 Posts

    Default

    Read info.pdf from loader.zip file, buy usbasp programmer to connect appropriate pins to atmega chip (mosi, miso, reset and others) or trace them to the left side of your image.

  3. The Following User Says Thank You to kaalis For This Useful Post:

    mu95f (25th April, 2018)

  4. #6108
    DK Veteran

    Join Date
    Jul 2016
    Location
    Vilnius
    Posts
    1,180
    Thanks Thanks Given 
    57
    Thanks Thanks Received 
    562
    Thanked in
    379 Posts

    Default

    Seems this interface has got some free holes for pins. I'd repurpose them for MOSI, MISO, SCK, RST and GND pins for future to get comfortable access.
    Also, "while you are there" it might be good idea to solder in a protective diode on the ODB2 #16 pin instead of the straight "wire" (personally I don't like this particular setup with these straight wires but well it's only me).
    Worth mentioning that the hardware is actually 0x44 rather than 0x46
    I can calculate ABS module codings for:
    * Continental/Teves MK60EC1 and MK60;
    * TRW systems in Passat B6 / B7 / CC /Tiguan;
    * MK100
    ;
    * Bosch ABS8.2, ABS9.0 and ESP8.2, ESP9.0;
    * EBC 460 (UP!, Mii, Rapid, CitiGo, Fabia, Toledo, etc) New!
    *
    ... and other VW/Audi/Seat/Skoda modules.I can assist with repairing \/CDS interfaces.

  5. The Following User Says Thank You to hid3 For This Useful Post:

    mu95f (25th April, 2018)

  6. #6109
    DK Veteran
    galaxy0634's Avatar
    Join Date
    Jan 2018
    Location
    Namek planet
    Posts
    1,388
    Thanks Thanks Given 
    683
    Thanks Thanks Received 
    199
    Thanked in
    137 Posts

    Default

    hello guys please tell me about carprog 10.94 is it a good tool to work with dashboard mcu without soldering?

  7. #6110
    DK Veteran

    Join Date
    May 2010
    Posts
    634
    Thanks Thanks Given 
    140
    Thanks Thanks Received 
    195
    Thanked in
    123 Posts

    Default

    Quote Originally Posted by hid3 View Post
    Why do you think it is 0x44?
    HW architecture

  8. #6111
    DK Veteran

    Join Date
    May 2010
    Posts
    634
    Thanks Thanks Given 
    140
    Thanks Thanks Received 
    195
    Thanked in
    123 Posts

    Default

    Quote Originally Posted by mu95f View Post
    Hello guys,
    [...] Hardware (0x46) version with VAGCOM_HWType.exe.
    [...]
    Is 44 type, too

  9. The Following User Says Thank You to liviudiaconu For This Useful Post:

    mu95f (27th April, 2018)

  10. #6112
    DK Veteran

    Join Date
    Jul 2016
    Location
    Vilnius
    Posts
    1,180
    Thanks Thanks Given 
    57
    Thanks Thanks Received 
    562
    Thanked in
    379 Posts

    Default

    Quote Originally Posted by liviudiaconu View Post
    HW architecture
    Yeah, I understand it's HW architecture. But that interface looks like it's 0x46 since there are no connections to GAL chip. Or am I wrong?
    I can calculate ABS module codings for:
    * Continental/Teves MK60EC1 and MK60;
    * TRW systems in Passat B6 / B7 / CC /Tiguan;
    * MK100
    ;
    * Bosch ABS8.2, ABS9.0 and ESP8.2, ESP9.0;
    * EBC 460 (UP!, Mii, Rapid, CitiGo, Fabia, Toledo, etc) New!
    *
    ... and other VW/Audi/Seat/Skoda modules.I can assist with repairing \/CDS interfaces.

  11. #6113
    DK Veteran

    Join Date
    May 2010
    Posts
    634
    Thanks Thanks Given 
    140
    Thanks Thanks Received 
    195
    Thanked in
    123 Posts

    Default

    See pin 35.

  12. #6114
    DK Veteran

    Join Date
    Jul 2016
    Location
    Vilnius
    Posts
    1,180
    Thanks Thanks Given 
    57
    Thanks Thanks Received 
    562
    Thanked in
    379 Posts

    Default

    I think it's not enough. Firstly, you need to use a multimeter to confirm that connection in fact doesn't exist. Secondly, the very same interface is in use by Kolimer and I think he has confirmed it to be HW46 actually.
    I can calculate ABS module codings for:
    * Continental/Teves MK60EC1 and MK60;
    * TRW systems in Passat B6 / B7 / CC /Tiguan;
    * MK100
    ;
    * Bosch ABS8.2, ABS9.0 and ESP8.2, ESP9.0;
    * EBC 460 (UP!, Mii, Rapid, CitiGo, Fabia, Toledo, etc) New!
    *
    ... and other VW/Audi/Seat/Skoda modules.I can assist with repairing \/CDS interfaces.

  13. #6115
    Newbie mu95f's Avatar
    Join Date
    Apr 2018
    Posts
    8
    Thanks Thanks Given 
    9
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    Quote Originally Posted by ouldsmobile View Post
    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.
    Hello ouldsmobile
    above all, excellent work,
    I would have a question because you have used " -U lock:w:0x3f:m " ,
    i saw that on the fantomel guide, by programming with USBASP, 0xCC is used.
    Regards

  14. #6116
    Newbie mu95f's Avatar
    Join Date
    Apr 2018
    Posts
    8
    Thanks Thanks Given 
    9
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    Quote Originally Posted by hid3 View Post
    I think it's not enough. Firstly, you need to use a multimeter to confirm that connection in fact doesn't exist. Secondly, the very same interface is in use by Kolimer and I think he has confirmed it to be HW46 actually.
    Hello hid3, liviudiaconu
    I have controlled better, and the pin 34 - 35 of the Atmega 162, are connected respectively to pin 5 - 4 of the ATF16V8.
    So according to the guide it should be a 0x44.
    But as already said the prg. VAGCOM_HWType.exe detects it as 0x46.
    Is this correct?
    I've already installed the programe pins, I'm waiting for the USBASP interface to arrive.
    I have an arduino UNO and am tempted to try to program it with this.

    I include enlarged photo.

    Regards

    4.jpg
    Attached Images Attached Images
    • File Type: jpg 3.jpg (3.37 MB, 60 views)
    Last edited by mu95f; 27th April, 2018 at 07:26 PM.

  15. #6117
    DK Veteran

    Join Date
    Jul 2016
    Location
    Vilnius
    Posts
    1,180
    Thanks Thanks Given 
    57
    Thanks Thanks Received 
    562
    Thanked in
    379 Posts

    Default

    This is NOT correct.
    Your hardware is 0x44 for sure.
    The HW Type tool simply shows what the EEPROM says to it. And EEPROM says what's flashed inside.
    Someone simply flashed 0x46 EEPROM to your interface, either by mistake or lack of knowledge or any other reasons.
    I can calculate ABS module codings for:
    * Continental/Teves MK60EC1 and MK60;
    * TRW systems in Passat B6 / B7 / CC /Tiguan;
    * MK100
    ;
    * Bosch ABS8.2, ABS9.0 and ESP8.2, ESP9.0;
    * EBC 460 (UP!, Mii, Rapid, CitiGo, Fabia, Toledo, etc) New!
    *
    ... and other VW/Audi/Seat/Skoda modules.I can assist with repairing \/CDS interfaces.

  16. #6118
    Newbie mu95f's Avatar
    Join Date
    Apr 2018
    Posts
    8
    Thanks Thanks Given 
    9
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    Quote Originally Posted by hid3 View Post
    This is NOT correct.
    Your hardware is 0x44 for sure.
    The HW Type tool simply shows what the EEPROM says to it. And EEPROM says what's flashed inside.
    Someone simply flashed 0x46 EEPROM to your interface, either by mistake or lack of knowledge or any other reasons.
    Hello
    maybe I expressed myself badly, but I'm saying the same thing, my HW is 0x44.
    Regards

  17. #6119
    Top Poster
    Join Date
    Apr 2010
    Location
    RF
    Posts
    133
    Thanks Thanks Given 
    1
    Thanks Thanks Received 
    39
    Thanked in
    21 Posts

    Default

    Quote Originally Posted by hid3 View Post
    The HW Type tool simply shows what the EEPROM says to it. And EEPROM says what's flashed inside.
    Someone simply flashed 0x46 EEPROM to your interface, either by mistake or lack of knowledge or any other reasons.
    Bootloader (part of flash) or a flash sends data about type flash. It is possible to determine type flash of EEPROM only by implicit signs.

  18. #6120
    DK Veteran
    Join Date
    Feb 2013
    Posts
    392
    Thanks Thanks Given 
    73
    Thanks Thanks Received 
    94
    Thanked in
    77 Posts

    Default

    Ok, so if that hardware is x44 and I use x46 dump should work ok or not?

    In my case, about hardware with pics posted in my last post, I used x46 dump and it works just fine.

    With an older type of hardware, 44 too, I flashed by mistake 46 dump...and no "interface found".

 

 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.