VAG-COM/VCDS EVERYTHING

[gini80]

I tried 17.8.1 ROJ, it does not work

[xoom]

I tried 17.8.1 ROJ, it does not work

Tried also V6.1 with ROJ..

First test: Invalid/Unregistered

but connects to modules..

Checked again About window and it's Registered :
rojtst.jpg

[gini80]

thanks, loader v2 works well with 17.8.1 ROJ

[djrjay]

hi.
can anybody how remove GAL F16V8BQL?
what connect with?
thanks20180214_195248.jpg20180214_195341.jpg

GAL is now removed from PCB.
then i need coonect pins

[AndreaEl]

why removed GAL?

[ccr64k]

Tested on a previous interface that was down due to V5 loader and 18.1 VCDS
Used external programmer, writing OK

Test on Golf Mk5, coding OK, autoscan OK, clear DTC OK, licence valid.

Rewriten it with USB write, all OK.

So far so good

Do you have a way to "lock" it, I mean VCDS can't rewrite with unvalid licence or modify as with V5 and lock the eeprom? Fuses maybe?

Simple hooking of EEPROM writing function from RT_USB.dll will do the trick. Kolimer hooks EEPROM reading function already, it should be a minor adjustment for him.

[xoom]

Simple hooking of EEPROM writing function from RT_USB.dll will do the trick. Kolimer hooks EEPROM reading function already, it should be a minor adjustment for him.

RT_USB.DLL have functions to read and write FT232 EEPROM.. but not ATMEGA162 EEPROM if you want to BLOCK writing to AVR EEPROM you should modify FW.. But VCDS writes to eeprom many times

[djrjay]

it block write to Atmega

[eliotroyano]

Can be PLD chip (GAL16V8) draws excess current and 8705 gets HOT.. Maybe you have dropping voltage.. (ATF16V8BQL) draws way less current..

These are the 7805 and GAL16V8 ICs. MCP2515 is working just gets slow after some seconds of use CAN protocol.

Sent from my Android Smartphone

[eliotroyano]

Can be PLD chip (GAL16V8) draws excess current and 8705 gets HOT.. Maybe you have dropping voltage.. (ATF16V8BQL) draws way less current..

Also weird thing is that I have another similar interface (my backup one just newer V11.3 with same HW, ICs and FW) and works quite nicely.

Sent from my Android Smartphone

[ccr64k]

Simple hooking of EEPROM writing function from RT_USB.dll will do the trick. Kolimer hooks EEPROM reading function already, it should be a minor adjustment for him.

RT_USB.DLL have functions to read and write FT232 EEPROM.. but not ATMEGA162 EEPROM if you want to BLOCK writing to AVR EEPROM you should modify FW.. But VCDS writes to eeprom many times

Definitely ATMEGA 162 EEPROM is written by FW in ATMEGA 162 flash, but VCDS must trigger the unwanted write and provide mangled content. It should be similar to flashing new firmware. What does VCDS write to ATMEGA 162 EEPROM? The number of coding and adaptation performed?

[dj2d]

I have an old 16.8.x cracked VCDS that was working with cracked RT_USB.dll, I don't know in what way it's modified but I can assume it is in a good way, I will try to use this one and check what's happening.

That's the only real issue I got so far, from time to time invalid licence, sometimes uninstall/clear windows reg/reinstall do the trick, other times I have to reflash the atmega.

[ccr64k]

Please delete

[dj2d]

I never read/edit a DLL, I'm downloading Reshacker, I will try to find that and report.

[dj2d]

I am no engineer but either Ressource Hacker can't read all the DLL, either it's empty AF.

1 VERSIONINFO
FILEVERSION 3,2,8,0
PRODUCTVERSION 2,10,0,1
FILEOS 0x40004
FILETYPE 0x2
{
BLOCK "StringFileInfo"
{
BLOCK "040904b0"
{
VALUE "CompanyName", "Ross-Tech LLC"
VALUE "FileDescription", "RT-USB library"
VALUE "FileVersion", "3.02.08"
VALUE "InternalName", "RT-USB.DLL"
VALUE "LegalCopyright", "Copyright © 2001-2014"
VALUE "OriginalFilename", "RT-USB.DLL"
VALUE "ProductName", "RossTech USB Drivers"
VALUE "ProductVersion", "2.10.00.1"
}
}


BLOCK "VarFileInfo"
{
VALUE "Translation", 0x0409 0x04B0
}
}