Thread: I think i've bricked my ecu. Help!

[QUOTE=OffTrack;1823331]Td5Inside maps are not VIN locked.[/

Even with no reference to vin, from our own experience we know that maps with wrong firmware to the Ecu have twice the chance to brick the ecus...

There can also be small "marks" on the map which can make the upload process go wrong IF your map file is being load to a different car or Ecu... As you all understand we have to protect ourselves from people o copy our maps and then share them.

So, if you have a map from us and for some reason swap your Ecu, don't just go out and try to upload the old map in to the new Ecu. Get in touch with us and we are more than glad to help you.

Happy new year to all!

[quote=td5inside;1824805]

Originally Posted by OffTrack

Td5Inside maps are not VIN locked.[/

Even with no reference to vin, from our own experience we know that maps with wrong firmware to the Ecu have twice the chance to brick the ecus...

There can also be small "marks" on the map which can make the upload process go wrong IF your map file is being load to a different car or Ecu... As you all understand we have to protect ourselves from people o copy our maps and then share them.

So, if you have a map from us and for some reason swap your Ecu, don't just go out and try to upload the old map in to the new Ecu. Get in touch with us and we are more than glad to help you.

Happy new year to all!

José, glad to hear that you are able to provide this support to your customers. I always find it a bit odd that a vendor would not be able to assist a customer by modifying a map to suit a replacement ECU.

To clarify your comments about "marks" in the context of this thread - is reloading firmware to a bricked ECU going to cause problems?

cheers
Paul

[quote=OffTrack;1824833]

Originally Posted by td5inside

José, glad to hear that you are able to provide this support to your customers. I always find it a bit odd that a vendor would not be able to assist a customer by modifying a map to suit a replacement ECU.

To clarify your comments about "marks" in the context of this thread - is reloading firmware to a bricked ECU going to cause problems?

cheers
Paul

Hi Paul,

We know that some vendors demand for more money for a new map to a replacemente ecu. We also now that some of them charge extra for new maps when you just want to upgrade your old one with a bit more power!!
We have nothing against it, bur prefer to work in a diferent way,!

As for your question, just make sure you load the correct firmware for the ECU and the firmware in wich the map file is based and there should not be a problem because all the other components from the ECU are still the same, apart from the 256kb you load to the 29f200 or 400!

Take care!

Originally Posted by OffTrack

Sounds like it's cactus. The inability to communicate is a sure sign that the firmware is corrupted.

Why did it happen? It seems to be an issue related to reading from the SDCard. Will it happen again? If you install the Nanocom firmware update that was released on the 19/12/2012 then it's fairly unlikely (unless you are using a BAS encrypted map and then all bets are off). The update changes the map upload process by loading the map into memory before the write stage. This eliminates the SDCard as a variable in the write process. I was testing this prior to release and found once the map loaded and verified successfully (which was a bit hit and miss) the write stage was 100% successful. I know one member still had issues with the BAS protected maps. I was uploading Td5Inside maps without any dramas.

I'm able to revive bricked ECU's but wouldn't be able to do so in time for the New Year at this stage.

cheers
Paul

BAS files require BAS firmware to load their .map files.

Originally Posted by Benny_IIA

BAS files require BAS firmware to load their .map files.

I think you'll find that is not the case. BAS released a "read-all" firmware for the Nanocom One, but I'm not aware that any alternate firmware exists for the Evo. Tombie - who was reselling BAS remaps in .AU - recently gave me two BAS files to evaluate and made no mention of special firmware. The only question was MSV or Nanocom format for the files.

Originally Posted by djam1

Unusual that the corruption occurred at that early point every time that happened to me I could recover it by trying again.
I wouldn't blame the Nanocom exclusively for any instability the TD5 Ecus are pretty flaky at times.
Unplugging of the red plug stops the glow plugs and fuel pump and other electrics from running during the write process
I presume the SD card was formatted as FAT not FAT32 I found issues when I did testing with FAT32 (BBS say FAT)

I agree it is unusual. I read the memory chip prior to restoring the firmware on Matts ECU and the whole of the first memory sector had been written successfully but the remainder of sectors which the Nanocom writes to had been erased.

Anyway, Matt's ECU has been revived successfully with correct VIN maintained and the Td5Inside remap uploaded.

cheers
Paul