Thread: DeBricking the NNN - an easier way?

I've finally got the BDM reprogramming working using a different, usb based, interface. I decided to change approach mainly because a dos/parallel port "solution" is insanely inconvenient when your main platform is a Macbook Pro.

Since my last attempt I've partially disassembled the ECU firmware which has meant I could see how the ECU was being configured at boot, which has made it far easier to proceed.

I finally decided to get stuck in this morning and put together config files for the factory eeprom chip and the ECU as a whole.

This afternoon I hooked up the ECU out of my Td5 and after a bit of tweaking the config I was able to read the contents of the EEPROM.



The named tabs will make sense if you have a look at this page: http://www.discotd5.com/diagnostics/...irmware-layout

So I got brave - after all there isn't much point if you can't write to the eeprom is there?!?

As proof of concept I decided I may as well change the VIN from the one that was in the firmware I used to restore the ECU when I initially bricked it to the correct one for the D2.

Before:


After:


Looks like it worked

And this is the interface hooked up to the ECU.




cheers
Paul

Just posted up a video on youtube showing my current debricking process. The ECU is hooked up as shown in the previous post.

[ame=http://www.youtube.com/watch?v=I4bUKhrvH-g]Debricking Td5 ECU's - YouTube[/ame]

Originally Posted by OffTrack

I've finally got the BDM reprogramming working using a different, usb based, interface. I decided to change approach mainly because a dos/parallel port "solution" is insanely inconvenient when your main platform is a Macbook Pro.

Since my last attempt I've partially disassembled the ECU firmware which has meant I could see how the ECU was being configured at boot, which has made it far easier to proceed.

I finally decided to get stuck in this morning and put together config files for the factory eeprom chip and the ECU as a whole.

This afternoon I hooked up the ECU out of my Td5 and after a bit of tweaking the config I was able to read the contents of the EEPROM.



The named tabs will make sense if you have a look at this page: Td5 ECU Firmware layout | DiscoTD5.com

So I got brave - after all there isn't much point if you can't write to the eeprom is there?!?

As proof of concept I decided I may as well change the VIN from the one that was in the firmware I used to restore the ECU when I initially bricked it to the correct one for the D2.

Before:


After:


Looks like it worked

And this is the interface hooked up to the ECU.




cheers
Paul

Great work there paul, Had to larf though, seeing the static mat and everything and right next to it is a mobile phone....hope it was switched off



JC

Originally Posted by justinc

Great work there paul, Had to larf though, seeing the static mat and everything and right next to it is a mobile phone....hope it was switched off



JC

It's just a cutting mat that I was using to protect the table

Ahh, ok , don't I feel an idiot....

You are a very rare breed then, in my 'youth' I have been known to assemble 4 cylinder jap engines on a kitchen table...without any kind of protection...and lived to tell the tale.


Are you close to/ going to be providing chipped NNN ecu's for outright or exchange sale at some point in the future?

JC

Paul did you use pogo pins or did you solder pins on the board?

For the ECU's I play with on a regular basis I solder headers in. Once the lid is off you can separate the bottom of the case off to access the underside. I use fresh solder and solder wick to clean out the through holes.

The pogo pins are better if you are doing a one off intervention. At the moment I just have them pressed into a 10 position IDC socket but it can be a bit tricky to get everything lined up. When I did Mike's ECU I actually hand held the pogo pin setup in place. Running the software is quick enough that this works ok. I'll look at making up a better solution for this.

I'm putting together a package with the modified flash config file which adds support for the chip used on the ECU, the Td5ECU config file, and the script for doing the fuel and variant map uploads.

I've been tidying up the script and have added some checks that the flash chip is accessible before the programming phase starts. I still need to add in a menu item for download/uploading VIN information. I'll have some more information about this up on my blog/website in the next few days.

cheers
Paul

Paul I used a bench setup last night on a spare ECU and found that even my new Nanocom was freezing up.

Will have to look further into my setup