NefMoto

Hi,

I'm awaiting delivery of a galletto 1260 and I'm about to buy a kwp2000+ to flash by obd.

I currently use my own software to flash.

But I didn't have problems flashing via OBD with Galletto.

Tony,
   
Have you tried your software on a VW 1.8T?

I have only tried on my 2001.5 Audi S4.

The free flashing tool I am finishing up write now "SHOULD" work on any ME7x based ECU. It will let you define your own memory start address and layout, and that is really all that should change between different ME7 versions.

Tony

Any chance to make your software work with M3.8 with 29f200 ?

Ok, I am very green about this but none the less,i like to try. What I need to know is, how to identify memory start address and layout.

You identify the memory layout by determining what flash chip is in the ecu. Then find the data sheet for the flash chip. The data sheet will tell you the sector layout for the chip.

As for the start address, as far as I know, all ME7 ecus have the flash chip start address at 0x800000. The flash memory space is mapped to every multiple of 0x100000 starting from 0x100000, but the flashing protocol for the ME7 only accepts a specific address.

Sure. Just give me all of the info on the M3.8.  ;D

What Kind of Info you need ?

kind of memory, processor, some files ?

what else ?

Information on all of the chips in the ECU.
Memory dumps of all memory chips in the ECU.
Some information on what cars came with this ECU and what years they were made.
Damos files, map definition files, etc.

Currently I only support flashing via the KWP2000 protocol. So if the ECU does not support this protocol, then I won't be supporting it any time in the near future.

I get an "Opening Port Impossible? error with Galletto over my FTDI cable that operates over COM1 (virtual through FTDI drivers on Windows XP). Any thoughts?

galletto specific drivers needed....

I too am getting this... where can we get those drivers?

josh

It seems strange that Galletto operates on COM1 because COM1 and COM2 are assigned to physical ports. Usually you use COM3+ for virtual ports.

Incorrect. My laptop does not have any physical COM ports. COM 1-4 only appear when I plug in the FTDI cable. The upper 5-14 or so are virtual, and they are there (my bluetooth drivers take up some of them). I have been using wbh-diag and VAG-COM/VCS over those non-physical COM porta that are created through the FTDI driers for years now.

If anybody knows what I need to do to get galletto to read an ECU (at least) through the COM ports let me know. The problem, as I see it, is that Galletto does not open those virtual COM ports as expected. Or, it needs some response over the COM ports that the FTDI does not do.

Ideas?

Galletto uses FTDI's FT232R chip so maybe this can help you: FTDI_Drivers_Installation_Guide_for_WindowsXP (http://www.ftdichip.com/Documents/AppNotes/AN_104_FTDI_Drivers_Installation_Guide_for_WindowsXP%28FT_000093%29.pdf)

I think first you must uninstall the drivers that you installed previously in the Device Manager and then install a updated driver version here (http://www.ftdichip.com/Drivers/CDM/CDM20600.exe).
   
I have not tried it myself because galletto 1226 works plug and play in vista, so Good Luck.

That would be why mine isn't working... I was trying to use my cable which uses the 232BL chip. Not the R chip....

Guess I will just wait for Tony's program... Anyone know how long till its out? (Im not impatient... just really want to get to tuning! :)

Josh

Negative, sir. I glanced through the document and then followed your link for updated WinXP drivers. Uninstalled the old ones I had on the laptop and used the EXE in the link to update. Tested functionality of the cable with the new drivers with wbh-diag and all is fine. The driver may actually work a little better too.

But Galletto still gives "Opening Port Impossible' and that is it. I tried using the COM14 port where the driver first installed the COM port after instaalling the new drivers but that did not work. I reverted back to COM1 which is what makes VAG-COM and wbh-diag work fine. Galletto does not like either of them.

I may not have the right FTDI cable that Galletto needs, but I doubt it. Everything else works over it, and since it is nothing more than a serial port over USB, I do not see how a different cable would be any different. But what do I know.

Something that may help is knowing which COM port Galletto is trying to access. I tried an "strace" of the executable but failed. Strace is the system trace under linux, and since I have Cygwin for using a linux environment over WinXP I tried that. There is no output that is produced from strace, so that did not help. Is there anything equivalent to that for WInXP that I can try?

Josh, the driver I gave you works for all FTDI chips.

Iznogoud, you can test communication with the FT232xx using FT_PROG (http://www.ftdichip.com/Resources/Utilities/FT_PROG.zip)

This is the eeprom dump from my galletto (ver. 1260)
(http://img40.imageshack.us/img40/8476/ftprog.th.jpg) (http://img40.imageshack.us/i/ftprog.jpg/)

I think Galletto seeks specific (vendor id, product id, product description, serial number), maybe your dump is corrupted or missing.

Crap, this is an uphill battle for me...

I downloaded straight the FT_PROG.zip and dropped it in the real (not virtual) WinXP. The two applications that are in there fail to initialize and simply do not run after they have been extracted with all the contents of the zip file. I also went to the following "Resources" link, which is probably where you went to fetch that zip file, but could not find anything relevant, icluding that zip file.

Linky Clicky (http://www.ftdichip.com/Resources/Links.htm)

On the up side, I found a link to somebody's POSIX serial programming document and realized that I may be doing something wrong in my serial port initialization when I try to connect to the ECU with my homebrewd linux software. So, thanks for that!

Still at a loss with Galletto.