VAG-COM/VCDS EVERYTHING

**KenshinPT** · 25th January, 2011, 01:38 PM

Originally Posted by croatiaobd

I know that im probably boring with this questions "why this and why that but....Why is this happening...Chip type FT245R?????(attached picture)

Also i have noticed when opening .ept file for FT232RL ("VCDS 908 FT232RL.ept")in Mprog stands for Device Type: FT232BL ....not RL? is it mistake?

You need to open the correct template and then apply it in the correct device.

It's hard to explain it here... but in the help it's very clear.

Good luck

**aminebot** · 25th January, 2011, 05:51 PM

Originally Posted by croatiaobd

I know that im probably boring with this questions "why this and why that but....Why is this happening...Chip type FT245R?????(attached picture)

Also i have noticed when opening .ept file for FT232RL ("VCDS 908 FT232RL.ept")in Mprog stands for Device Type: FT232BL ....not RL? is it mistake?

ept file format is different from xml file format , i think that you can not only change extension from ept to xml.

See attached video , it show how to use Ftprog

i want to upload FT232R dump in xml format but i don't know if uploading dumps is against DK rules or not.

video3.rar

**mattydr67** · 25th January, 2011, 05:57 PM

Originally Posted by aminebot

ept file format is different from xml file format , i think that you can not only change extension from ept to xml.

See attached video , it show how to use Ftprog

i want to upload FT232R dump in xml format but i don't if uploading dumps is against DK rules or not.

video3.rar

i want to upload FT232R dump in xml format but i don't if uploading dumps is against DK rules or not.

I know that a lot of peaple share this kind of dumps here even for Atmega.
So I belive it is not against the rule but for sure let a Moderator to replay and explain if this is against the rules or not.
I don't want you to be banned ( I said "I" but I suppose that is "WE")
Good luck

**tomasfilip** · 25th January, 2011, 06:07 PM

Originally Posted by croatiaobd

Friend of mine had an interface 10.6 that worked well...fully registered, autoscan worked fine...everything perfect...changed labels....
My 10.6 interface didn't work...so we tried to fix mine....to make it as a clone of his..We were trying to use ftprog but with no success.....and somehow i have run the "Eeprom programmer_RTQX615IX.exe" downloaded i think form here... to see what it is and friend's cable was plugged in....and now i have only USB-serial converter (when i plug it into usb port)...I have obviously erased evrything because ftprog does not recognize it...??

What can i do now? How to make it Rosstech USB direct interface, cause friend if pretty angry now???

this eeprogrammer_rtqx.. is writting data (really), because is main purpose is reprogramm damaged cable, they also show what is before in memory, but after that, data is written there automatically. What is currious, that cable isn't recognized after that..

anyway, sorry if isn't clear the program is reprogramming tool and not reading tool

**tr3ce13** · 25th January, 2011, 08:43 PM

................................

**hneel** · 25th January, 2011, 08:49 PM

I have used my 805.1 cable with newer versions of VCDS, just to see if it worked or not. Is my cable now doomed?

Before I found this forum I was totally unaware that my cable could get damaged by VCDS. So I also didn't include ross-tech in my hostfile. Speaking of which, is it also possible to use windows firewall to prevent VCDS connecting to the internet?

BTW, how exactly is the cable damaged? Is it the contents of the 93Cxx chip that get overwritten or also the eeprom area within the atmega chip? As far as i understand at this moment, reviving the serial eeprom seems a lot easier than updating the atmega.

**croatiaobd** · 25th January, 2011, 11:53 PM

So guys....i'm going slightly mad...
Now my device is recognized as you can see in the attached pictures...as unknown device...no VID and PID...so how im going to make it work now-UDfixer can help me now!!? or?? I really dont know how i did it?

And while i was trying to use FTPROG as in video tutorial i got message : something like incompatibile devices or files (it is, i suppose, caused by not recognizing interface (friends one) as FT232...it was recognized as FT245-as posted few posts before...and mine is still recognized and can be programmed by FTProg-but does not work with software-after plugging it into OBD says "no interface found")

And yes...friend is also mad...but not slightly....

. And i'm trying to find a way to spend money in a better way....than buying new interface for him...:=)

**aminebot** · 26th January, 2011, 02:01 AM

Originally Posted by croatiaobd

So guys....i'm going slightly mad...
Now my device is recognized as you can see in the attached pictures...as unknown device...no VID and PID...so how im going to make it work now-UDfixer can help me now!!? or?? I really dont know how i did it?

And while i was trying to use FTPROG as in video tutorial i got message : something like incompatibile devices or files (it is, i suppose, caused by not recognizing interface (friends one) as FT232...it was recognized as FT245-as posted few posts before...and mine is still recognized and can be programmed by FTProg-but does not work with software-after plugging it into OBD says "no interface found")

And yes...friend is also mad...but not slightly....

. And i'm trying to find a way to spend money in a better way....than buying new interface for him...:=)

for "unknown device" problem , check if USB wires and FTDI pins are soldered correctly.

**aminebot** · 26th January, 2011, 05:27 AM

Originally Posted by tr3ce13

hex0000-xxxxxx-xxxxxx-ffffff-aaaaaa-ffff

Something about this serial number & eeprom.
In the atmega eeprom are writing the xxxxxx-xxxxxx the other digits are calculated.
Eeprom have no cheksum and can change anything, if put a valid serial it can communicate with the soft but is unregistered.
Some serials have "+CAN", others not, some comunicate.... bad serials/eeprom says "failed self test", banned "interface not found" ....
In the eeprom is also the activation for the serial but is more dificult to find the good code.

It's wrong , please don't post unverified informations .

All serial numbers are valid if you know how to calculate encrypted data and checksums.
You get "failed self test" error when first checksum (2 bytes at adress @0011) is incorrect.

Originally Posted by hneel

Is my cable now doomed?
So I also didn't include ross-tech in my hostfile. Speaking of which, is it also possible to use windows firewall to prevent VCDS connecting to the internet?
BTW, how exactly is the cable damaged? Is it the contents of the 93Cxx chip that get overwritten or also the eeprom area within the atmega chip? As far as i understand at this moment, reviving the serial eeprom seems a lot easier than updating the atmega.

You can use firewall to prevent communication between VCDS soft and rosstech server.
In most cases using lower version does not damage interface.
First data damaged is eeprom area in atmega , the last damaging step is the FTDI eeprom ( 93CXX for FT232B or inside FT232R).
I uploaded a loader for 812 version in a previous post, this loader can repair modified data into Atmega.
For more info , see this post

**tr3ce13** · 26th January, 2011, 08:51 AM

...............................

**KenshinPT** · 26th January, 2011, 11:09 AM

Yesterday I was replacing my old AT93C56A (ATMEL EEPROM) 8/16bit without Program Enable to another one from Microchip: 93LC86C 8/16bit with Program Enable.

Datasheet is clear: when PE is tied to GND, program is disable, when is tied to VCC program is enable and this pin cannot be left unconnected.

My PCB has this pad connectd to GND so I lifted up that pin and tied to VCC. Till now everything OK, right?

I tried to program the EEPROM via FTPROG and MPROG and no matter what I couldn't.

That's when I remembered that FT232BL only supports 93C46, 93C56 and 93C66... But I tought that the FTDI's datasheet was old and newer versions of the 93C will also be compatible.

I tried with another one: ST M93C86 and the result was the same.

I emailed FTDI if to check If I am doing anything wrong of if FT232BL doesn't support this EEPROM's

**croatiaobd** · 26th January, 2011, 11:55 AM

Originally Posted by aminebot

for "unknown device" problem , check if USB wires and FTDI pins are soldered correctly.

yes...everything is soldered and connected right...

**KenshinPT** · 26th January, 2011, 11:56 AM

My email to FTDI:

Originally Posted by KenshinPT Email

Dear Sir or Madam,

I have a question about one FTDI products because I need to replace the external EEPROM from a FTDI232BL.

The EEPROM that needs to be replaced is a ATMEL - AT93C56A

datasheet:
http://www.atmel.com/dyn/resources/prod_documents/doc3378.pdf

The AT93C56A provides 2048 bits of serial electrically erasable programmable read-only memory (EEPROM) organized as 128 words of 16 bits each (when the ORG pin is connected to VCC) and 256 words of 8 bits each (when the ORG pin is tied to ground).

I found out that Microchip's EEPROM 93LC76C and 93LC86C are also a 8bit/16bit with Program Enable and more memory (8KB/16KB).

This is exactly the memory I want to use but I tried to use those for a direct replacement and I can't program the EEPROM via FTPROG (or MPROG).

That's when I realise that in FT232BL's datasheet I found out that this chip is only compatible with 93C46, 93C56 or 93C66.

So my question here is: Where can I find an EEPROM 16 bit wide, with Program Enable and full compatible with FT232BL?

Best regards

FTDI response:

Originally Posted by Gordon Lunn from FTDI

Hello,

Sorry we are not EEPROM experts and do not supply such products.

All we can state is what is required to connect to our devices.

Ie 93C46/56/66 with a x16 organization.

Most users seem to source their EEPROMs from ATMEL, ST or Microchip.

Regards,

Gordon Lunn
Senior Applications Engineer

Future Technology Devices International LTD.
Unit 1, 2 Seaward Place
Centurion Business Park
Glasgow, G41 1HH, UK

Tel: +44 (0) 141 429 2777
Fax: +44 (0) 141 429 2758
Email: support1@ftdichip.com
Web: www.ftdichip.com

**KenshinPT** · 26th January, 2011, 12:00 PM

Originally Posted by croatiaobd

yes...everything is soldered and connected right...

Maybe:

Faulty FTDI
Faulty USB port
USB cable wires are in short circuit

Is that a new cable? Give it a better look into the PCB. Maybe you'll find some components without solder.