VAG-COM/VCDS EVERYTHING

[apsol]

Hello again, so I found out my cable has the bootloader locked and I don't want to be fiddling with wires and soldering, I may break it instead of fixing it.

So do you recommend any cable that I can update further to 19.6.1 ? I've seen a link here with a discount for members but I don't know if that one needs to solder wires etc in order to work.

Ideally it would be nice a good cable ready to go on latest version or close but if it's just a matter of flashing the eeprom then i think i can do it, there's so many on obd2cartool that I don't know what to choose.

[kaalis]

That discounted cable you found will allow to update without soldering. You may want to buy it together with Uspbasp to change 0x46 to real 0x44.

Sent from my SM-J510FN using Tapatalk

[DrCrazy]

Hi all,
I used perfect until now VCDS ROJ 19.6.1 with loader 9.2, but from 10 min ago the loader is blocked with message: " failed 4 "
You can tell me what's going on?

Many thanks

[FredrikO]

I really need some help from you... and I would be really happy if you can help me.
I have soldered the wires from the USBASP to the HEX-cable like this:

MOSI -> pin 14 MCP2515
VCC -> pin 18 MCP2515
RESET -> pin 4 ATMEGA162
SCK -> pin 13 MCP2515
MISO -> pin 15 MCP2515
GND -> 7805

I have verified with multimeter that it is okay and that the pins not connects to eachother.

I put the USBASP (it's set on 5V) in the computer and start PROGISP, PROGISP finds the USBASP and the LED on the HEX-cable starts blinking red. I click "RD" in PROGISP, the LED stops blinking (still red) but I get the error message Chip Enable Program Error.
If I load the flash and the EEPROM and changes the fuse and lock so it is correct and then clicks "auto" the LED goes green but I still get the "Chip Enable Program Error".

Any suggestions?

Edit: I have tried with different USBASP-drivers and also with eXtreme Burner AVR without luck.

[apsol]

That discounted cable you found will allow to update without soldering. You may want to buy it together with Uspbasp to change 0x46 to real 0x44.

Sent from my SM-J510FN using Tapatalk

And what difference would that make ?

[rak183]

And what difference would that make ?

Its for me also interresting to know this Difference

[Roma77]

And what difference would that make ?

Its for me also interresting to know this Difference

Those who are interested, study the schemes on the platform and know the differences between 0x44 and 0x46, at the moment all Atmega firmwares go 0x46, and there are different boards, and 0x46 and 0x44, it is logical that the seller knows about this and offers to buy a programmer.

[mattock808]

hi man, i have problem with my cable , the cable has stopped working.

led in cable no shine, PC no see cable. NO reaction PC after connecting.
where could be the problem? IMG_20190913_062000.jpgIMG_20190913_062020.jpg

[Roma77]

hi man, i have problem with my cable , the cable has stopped working.

led in cable no shine, PC no see cable. NO reaction PC after connecting.
where could be the problem? IMG_20190913_062000.jpgIMG_20190913_062020.jpg

Check 12 volts on the diode D1 and transistor 1705 - at the input of 12 volts at the output of 5 volts.

[mattock808]

thanks, yes i have 12v input 1705, output 1705 i have 5V

[FredrikO]

I really need some help from you... and I would be really happy if you can help me.
I have soldered the wires from the USBASP to the HEX-cable like this:

MOSI -> pin 14 MCP2515
VCC -> pin 18 MCP2515
RESET -> pin 4 ATMEGA162
SCK -> pin 13 MCP2515
MISO -> pin 15 MCP2515
GND -> 7805

I have verified with multimeter that it is okay and that the pins not connects to eachother.

I put the USBASP (it's set on 5V) in the computer and start PROGISP, PROGISP finds the USBASP and the LED on the HEX-cable starts blinking red. I click "RD" in PROGISP, the LED stops blinking (still red) but I get the error message Chip Enable Program Error.
If I load the flash and the EEPROM and changes the fuse and lock so it is correct and then clicks "auto" the LED goes green but I still get the "Chip Enable Program Error".

Any suggestions?

Edit: I have tried with different USBASP-drivers and also with eXtreme Burner AVR without luck.

No one with a suggestion what could be wrong or how to troubleshoot?

[hid3]

thanks, yes i have 12v input 1705, output 1705 i have 5V

Try reflashing the (correct) firmware then, along with proper fuses

[hid3]

No one with a suggestion what could be wrong or how to troubleshoot?

Are you sure you haven't swapped MOSI with MISO when connecting to the programmer?
Also, I'd suggest powering the chip via OBD2 12V circuit and do not power it from the 5V USBASP source (jumper removed)

[mattock808]

yes this action is no problem , with USBasp i flashing firmware no problem - this is done

PC no see cable, no reaction

[hid3]

Do you get red/green LED when plugged into car?