Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
 |
« Reply #15 on: March 01, 2011, 05:35:16 PM »
|
|
|
I'm trying right now with my FT232R and I will let you guys know how it goes.
I recommend upgrading to version 1.7.0.0 if you haven't. It contains a bunch of bug fixes just for you and your evil cable. |
|
|
|
|
Logged
|
|
|
|
GWerks
Full Member
Karma: +3/-0
Offline
Posts: 66
|
|
« Reply #16 on: March 01, 2011, 07:56:31 PM »
|
|
|
I'm trying right now with my FT232R and I will let you guys know how it goes.
I recommend upgrading to version 1.7.0.0 if you haven't. It contains a bunch of bug fixes just for you and your evil cable. I will for sure! I already downloaded it  Thanks so much Tony. |
|
|
|
|
Logged
|
|
|
|
GWerks
Full Member
Karma: +3/-0
Offline
Posts: 66
|
|
« Reply #17 on: March 01, 2011, 10:33:24 PM »
|
|
|
Tried flashing with NefMoto's software, first I tried with Maximum Baud and Slow Init and it wouldn't flash at all and I had to do it in 10400 Baud and Slow Init, first try failed at 8%, second time at 51%. Decided to call it a night, and I will try again tomorrow. The flashing was really slow, I think I just need a new cable.
Since it flashed all the way to 51%, maybe it did the checksums and now I can flash it Galletto?
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #18 on: March 01, 2011, 11:29:39 PM »
|
|
|
Tried flashing with NefMoto's software, first I tried with Maximum Baud and Slow Init and it wouldn't flash at all and I had to do it in 10400 Baud and Slow Init, first try failed at 8%, second time at 51%. Decided to call it a night, and I will try again tomorrow. The flashing was really slow, I think I just need a new cable.
Since it flashed all the way to 51%, maybe it did the checksums and now I can flash it Galletto?
It may have completed enough of the flashing process to clear the invalid checksum error codes. You can try this latency adjustment to see if it helps with your cable: http://www.nefariousmotorsports.com/forum/index.php?topic=409.0Do you have a log file of what went wrong? |
|
|
|
|
Logged
|
|
|
|
GWerks
Full Member
Karma: +3/-0
Offline
Posts: 66
|
|
« Reply #19 on: March 02, 2011, 09:53:27 AM »
|
|
|
Tried flashing with NefMoto's software, first I tried with Maximum Baud and Slow Init and it wouldn't flash at all and I had to do it in 10400 Baud and Slow Init, first try failed at 8%, second time at 51%. Decided to call it a night, and I will try again tomorrow. The flashing was really slow, I think I just need a new cable.
Since it flashed all the way to 51%, maybe it did the checksums and now I can flash it Galletto?
It may have completed enough of the flashing process to clear the invalid checksum error codes. You can try this latency adjustment to see if it helps with your cable: http://www.nefariousmotorsports.com/forum/index.php?topic=409.0Do you have a log file of what went wrong? Sorry, I thought I had uploaded it already. |
|
|
|
« Last Edit: March 02, 2011, 09:57:12 AM by GWerks »
|
Logged
|
|
|
|
GWerks
Full Member
Karma: +3/-0
Offline
Posts: 66
|
|
« Reply #20 on: March 02, 2011, 12:05:54 PM »
|
|
|
I finally got to flash my ECU with NefMoto with no errors and the car won't start still =(
I'm going to use Galletto again, maybe it will work this time?
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #21 on: March 02, 2011, 12:17:09 PM »
|
|
|
According to your log file, the flash failed after the ECU did not respond to a message for 9 seconds. I blame your cable, cause it doesn't make sense otherwise.
Do you know what your battery voltage is?
Did you try adjusting the latency in the FTDI device settings?
As for why the car won't start, can you check for error codes?
|
|
|
|
|
Logged
|
|
|
|
GWerks
Full Member
Karma: +3/-0
Offline
Posts: 66
|
|
« Reply #22 on: March 02, 2011, 01:54:58 PM »
|
|
|
According to your log file, the flash failed after the ECU did not respond to a message for 9 seconds. I blame your cable, cause it doesn't make sense otherwise.
Do you know what your battery voltage is?
Did you try adjusting the latency in the FTDI device settings?
As for why the car won't start, can you check for error codes?
Battery Voltage is at 13-13.5V, I tried adjusting the latency. When I flashed with NefMoto this last time (after I sent you the log) the flash was succesful, but it took about 10-15min. Now, the car won't start, and the ECU won't go into boot mode. |
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #23 on: March 02, 2011, 02:04:34 PM »
|
|
|
Did you check for error codes?
You should always be able to get into boot mode. Boot mode is provided by the hardware in the ECU.
|
|
|
|
|
Logged
|
|
|
|
GWerks
Full Member
Karma: +3/-0
Offline
Posts: 66
|
|
« Reply #24 on: March 02, 2011, 02:14:25 PM »
|
|
|
Did you check for error codes?
You should always be able to get into boot mode. Boot mode is provided by the hardware in the ECU.
Update: After a lot of tries I got it to go into boot mode, it flashed, the car won't start though. Just cleared the DTC's and nothing. Here is the log |
|
|
|
« Last Edit: March 02, 2011, 03:52:17 PM by GWerks »
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #25 on: March 02, 2011, 04:18:52 PM »
|
|
|
What were the error codes?
If the first two digits of calibrationEquipmentSoftwareNumber are not zero, the ECU is unhappy. Your calibrationEquipmentSoftwareNumber is 0x80190000, where the 8 in the first digit means the ECU is unhappy.
|
|
|
|
|
Logged
|
|
|
|
GWerks
Full Member
Karma: +3/-0
Offline
Posts: 66
|
|
« Reply #26 on: March 02, 2011, 05:07:18 PM »
|
|
|
What were the error codes?
If the first two digits of calibrationEquipmentSoftwareNumber are not zero, the ECU is unhappy. Your calibrationEquipmentSoftwareNumber is 0x80190000, where the 8 in the first digit means the ECU is unhappy.
I don't know. I gave up, I'm shipping it to a forum member that thinks that can fix it. I flashed it again using NefMoto and still nothing. By the way, the flash took 11 minutes. I'm ordering a new cable tomorrow. |
|
|
|
« Last Edit: March 02, 2011, 05:13:00 PM by GWerks »
|
Logged
|
|
|
|
kls
Full Member
Karma: +12/-0
Offline
Posts: 97
|
|
« Reply #27 on: March 02, 2011, 07:34:57 PM »
|
|
|
were you able to read the ECU after the final flashing to verify the code programmed was 100% correct?
If it was I suspect you have a fault in stored in the serial eeprom that isn't clearing or can't be cleared without manually reading and writing it.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #28 on: March 02, 2011, 07:58:21 PM »
|
|
|
Flashing with the NefMoto ECU flasher should clear any invalid checksum error codes, and the flashing process already validates that all data was written correctly.
All I can think is that you flashed the ECU with a tune that still had invalid checksums.
|
|
|
|
|
Logged
|
|
|
|
GWerks
Full Member
Karma: +3/-0
Offline
Posts: 66
|
|
« Reply #29 on: March 02, 2011, 08:51:56 PM »
|
|
|
Flashing with the NefMoto ECU flasher should clear any invalid checksum error codes, and the flashing process already validates that all data was written correctly.
All I can think is that you flashed the ECU with a tune that still had invalid checksums.
I was flashing the ECU with a stock file. I don't know what else could be |
|
|
|
|
Logged
|
|
|
|
|
