Cc generals zero hour maps pack download pc. Game or Patch Questions?
I tried using nef software yesterday to no avail. There are logs attached here. I have a hunch it may be my generic ebay cable. I am going to try.
From Nefmoto
|
The Galletto 1260 flashing cable allows you read and write access to various types of ECUs. It is most commonly used to access the ECU in boot mode when higher level flashing utilities, such as the NefMoto ECU Flashing Software, fail.
Requirements
Should work with Windows XP and Windows Vista/7 32bit.
If you have other cable software installed (APR Cheetah, VCDS) you may experience driver conflicts that break Galletto. If you have other cable drivers installed and connect connect to your ECU with Galletto uninstall all other cable drivers and start fresh with Galletto.
How to use
- Insert the disk that came with the Galletto cable into your computer and copy the contents to your local drive. Or download them from here
- Connect your Galletto cable to the ECU. You can do this on the bench or in the car. Make sure the ECU has constant, reliable power during any flashing operations!
- Plug the Galletto cable into your PC and install the drivers that come on the disk.
- Put the ECU into boot mode
- Launch the EOBD1260.exe program, it'll look like this:
- Select the 29F800BB memory layout. 'Cars' selection does not matter.
- Choose Open ECU to connect
- Choose Read ECU to read the file from the ECU. It will prompt you where to save the file.
- Choose Write ECU to write the file to the ECU
- Exit when complete
Galletto software displays 'Boot mode inactive'
- This seems to be caused by a driver conflict with the Galletto cable. Try reinstalling the driver and/or removing other cable drivers that may conflict.
Hello everyone,The ECU from my Leon Cupra R chipped AMK engine is broken through water damage.
Recently i bought a ECU from Ebay and i have the immo files copyed to the new ECU, car runs fine.
Now i will copy the maps, because my old ECU is chipped, can i not connect it whith Nefmoto flash software.
Validated FTDI device is in dumb mode.
Disconnected
Connecting..
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
The ME7_95040 tool says:
D:>me7_95040 --bootmode -r -p 4 95040.bin
Ver: 1.31
Com Port: 4
Baud Rate: 10400
Opening COM4 .. OK
Starting Boot_mode .. uC identification response = 0xC5 (C167 derivatives) ..
OK
Sending Loader + MonitorCore .. MonitorCore successfully launched
Initializing registers .. .. OK
Sending EEPROM driver .. OK
Searching Chip_Select pin .. FAIL. (error=0x01)
Closing COM4
I think the ECU is bricked. Now have i a MPPS (clone) cable and i try with bootmode(generic) to connect ECU.
ECU indentifaction and reading the ECU goes succesfully.
But when i will write the ECU in bootmode says the program: ECU not found.
Has anyone a idea to fix this issue?
Thanks in advance,
Dennis from Holland!:>