ECUProject.com

Heres a quick guide how to create a bootable USB flash key for the german deltawave (or simlar) bdm interface

http://cgi.ebay.com/BDM-Interface-f-Nokia-DBOX1-Mediamaster-9x00-DVB2000_W0QQitemZ360082233446QQihZ023QQcategoryZ29741QQssPageNameZWDVWQQrdZ1QQcmdZViewItem

http://search.ebay.com/_W0QQsassZdeltawave_computer

You need
FlashT7 1.1 http://www.xendus.se/bdm/flasht7_1.1.zip
bd32 software http://www.xendus.se/bdm/bd32-122.zip
USB Key (any size)
Win98 boot files http://files.extremeoverclocking.com/file.php?f=196
HP USB key format utility http://files.extremeoverclocking.com/file.php?f=197

Install the HP utility. Format the USB key with it, selecting the folder containing the extracted Win98 boot files and ticking the "Create a DOS startup disk" box.

Copy the extracted BD32 files to the newly formatted usb key along with the extracted initialization commands found in "flashT71.1.zip" reboot with the key inserted and don't forget to edit your bd32 config ("BD32.cfg") file found in the root of the USB key, changing the Delay and choosing the correct parallel port (Delay of 2500 worked for me)

Mini T7 Power Guide

You need to power the T7 unit as per this image


I created a wire harness from an old psu and some alligator clips.


Overview, NOTE the correct position and orientation of the red tape


Mini Flashing guide

Restart with USB key inserted (don't forget to modify boot priority and enable the parallel port in BIOS)

Tune BD32 with this guide http://www.xendus.se/index.php?option=com_content&view=article&catid=34:bdm-category&id=48:howto-install-bd32&Itemid=44

Should look like this output if connected correctly. (except full screen... DOS Style)


Image Copied from xendus.se (Can I use this image?)

At the flashing prompt type "BD32"
Power up the ECU and connect the BDM

IMPORTANT! You must prepare the ECU once before Reading and Writing...
This Enables registers, Disables the watchdog and allows writing to the ECU
Type do "prept7.do"

BD32 Should confirm that ECU is ready to program and that it is "STOPPED" with the following.
"ECU is now prepared for flash programming or erasing."



To Dump Flash type "dumpt7 finename.bin"
This process should take about 20 minutes...
Restart into windows and copy the original bin file to your hard disk, in-case the USB key gets corrupted.

To Erase flash
MAKE SURE YOU HAVE SUCCESSFULLY BACKED UP FLASH FIRST!
The erasing step should not be necessary, but if you experience errors in the flashing stage, come back and try this.

Type "do eraset7.do"
Then type "md 0x0 128". This is done to verify that the flash is erased.
You should read 0xFFFF on every address from 0x0 to 0x80000.

Restart into windows and edit the "Origional.bin" however you like, ensuring you make a backup of the original, only ever edit a copy of the file. If you wish to change VIN and IMMOBILIZER numbers use the freeware T7tool http://xendus.se/t7tool/T7Tool.1.0.0.17.rar

You must convert your edited bin file to a Motorola "src" file to flash it back to the ECU
Use bin2srec in a windows command prompt to convert to the src format
Type "bin2srec modified.bin > output.src"

To Write flash
Restart again using the flash key you created previously (with the previously created "output.src" copied to its root directory) and type

"do prept7.do" To prepare the ECU for writing.
"flasht7 output.src" To flash the ECU

This will take approx three times as long as reading the flash did. You will see a series of dots increasing in number, until completed.

If you run into problem when you are flashing try this:

- Double the delay parameter.
- If you didn't erase the flash - do it, and then try flashing again.
- The bottom field in BD32 should report "MCU: STOPPED" while you are using flashT7. If you for some reason have given the reset command you need to run the prept7.do script again in order to setup the registers and stop the MCU.
- You can ignore a "2: Type of S-Record is invalid" error as the ECU will still function.[/quote]

Thank you for this contribution!!

You need a Wiki...

sandy_rus wrote:

matthewm wrote:Overview, NOTE the correct position and orientation of the red tape

IMG_1814.jpg

RED STRIPE OF THE BDM CABLE ON THIS PHOTO PLACED INCORRECTLY!

As long as its incorrectly on both sides its ok I run it like this and it works fine. Its easy to remember that the cable should point away from the board on both boards.

That's the orientation I used correctly, I believe it is correct for the deltawave BDM interface.

Just a note. That very first picture is upside down and that confused the heck out of me today when flashing a T7 for the first time.

Yeah! I also put wires also opposite at first time. Almost shit my pants. So firstimers - be observant

The way you can tell is by looking at the connector. It's not symmetric up/down so make sure you check that before connecting your power to it.

So,

You only connect power/ground and no can hi/lo?

In the computer powercable, is + ther outer and - the nearest one?
Will of course measure it.

/Henrik

What CAN HI/LO ??
Guys you realize you are writing in the BDM thread,right?

Cheers,
Stoyan

Figured that, only power supply through that one.

/Henrik

Hi guys.
Thanks for the great guide!
I did experience some trouble when trying to flash on a spare T7 ECU.
I never could prept the ECU (gives me error 99), and when doing the MD 0x0 128 command in BD32, I recieved back a lot of Zero's and "F", not data.
I have flashed a lot of T5 ECU's, and did a test of my BD32-flasher afterwards on a T5, works without a glitz, so my hardware is ok.
Do you guys have any ideas as to what I'm doing wrong?
I have dumped the flash via T7suite on this specific ECU via canbus on the desk with succes(soldered in a connection that fits to my normal cable which has a resistor soldered in to "finish" the canbus system, like on T5), but now I can't get in contact with the ECU anymore, after trying to flash a new software to the ECU via T7suite. T7-tool has been tried as well, the program just breaks down once I try to hit connect...
Do any of you have an ideas as to what has gone wrong?
Thanks a lot for your input!
Daniel.

Hello.
Sorry, but then there this is the correct connection of BDM and ECU or this red stripe is incorrect?

Actually - testing is not dangerous, at least did not prove to be in my experience.

matthewm wrote: - You can ignore a "2: Type of S-Record is invalid" error as the ECU will still function.

Okay.. I managed to get it working for 75%.

When I try to flash a file after a certain number of rules with dots the program says: "4: unexpected blabla"

Does anybody know's what the problem is in this matter? The file I tried to flash is a *.s19 file.. perhaps this is the wrong format?

Thanks in advance for all your help!

saabtuners wrote:When I try to flash a file after a certain number of rules with dots the program says: "4: unexpected blabla"

Does anybody know's what the problem is in this matter? The file I tried to flash is a *.s19 file.. perhaps this is the wrong format?

Thanks in advance for all your help!

Unexpected file end?

It is normal.

J.K Nilsson

J.K Nilsson wrote:

saabtuners wrote:When I try to flash a file after a certain number of rules with dots the program says: "4: unexpected blabla"

Does anybody know's what the problem is in this matter? The file I tried to flash is a *.s19 file.. perhaps this is the wrong format?

Thanks in advance for all your help!

Unexpected file end?

It is normal.

J.K Nilsson

Nope it was different than 'unexpected file end' It was a failure number 4, but I will check tonight what it is exact. But it happened after 4 rules of dot's, that's about 5 minutes...

I dont understand this "boot-questions".

(First of all, my English is not that god...so please bare that in mind)

There is no need for any "boot", as far i´m concerned.

I might be missing substantial information, (due to the fact that i´ve not read all preuvios threads).
However, ... me (and my friend) easely managed to get the BDM-software (32-bit), working (together with the ECU-interface) with a parallell
connection creating/preparing an "empty" ECU with only FFFF´s.

Of course, you still need to use the interface-adapter: "lpt->bdm"

The computer connected was an old Pentium 133 with Win 98.

/Lufto

Lufto wrote:I dont understand this "boot-questions".

(First of all, my English is not that god...so please bare that in mind)

There is no need for any "boot", as far i´m concerned.

I might be missing substantial information, (due to the fact that i´ve not read all preuvios threads).
However, ... me (and my friend) easely managed to get the BDM-software (32-bit), working (together with the ECU-interface) with a parallell
connection creating/preparing an "empty" ECU with only FFFF´s.

Of course, you still need the the interface-adapter "lpt->bdm"

The computer connected was an old Pentium 133 with Win 98.

/Lufto

The problem is with WinXP/Vista because LPT port access is very restricted in those. So, advice is boot in DOS or Win98 to get it working