Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Flash Development Toolkit (FDT) software bug


Guru

Status: Offline
Posts: 963
Date:
Flash Development Toolkit (FDT) software bug


This probably won't happen to most of you but I'm going to document it here so I don't forget the details later.

I build USB cables to flash ECUs and of course I test each one by actually flashing an ECU before I ship them. Because I use a different USB cable everytime Windows XP assigns a new COM port number to each one.

Today I built a cable and it wouldn't work. After some trouble shooting I figured out that it was FDT that was the problem. Apparently FDT can not use comm ports above COM8. FDT would go through all the motions but it would never connect. Once I deleted all the ghosts of USB cables long gone FDT started working again.

What follows is a description of how to delete the accumulated COMs...

Open a command window.

Now set an environment variable by entering the line

"set devmgr_show_nonpresent_devices=1" - without the quotes obviously

then enter

"start devmgmt.msc"

In the box that opens, select "Show hidden devices" in the 'view' menu.

Now if you expand the section on COM ports, all the COM ports that have ever
been created will be displayed, the non present ones being in grey. You can
uninstall away anything that you don't want (right click, select uninstall).


-- Edited by RidgeRacer at 23:57, 2008-10-13

__________________


Guru

Status: Offline
Posts: 741
Date:

that's good to know as i'm on com 6 at the moment...

-- Edited by busa2001 at 02:28, 2008-10-14

__________________


Guru

Status: Offline
Posts: 2338
Date:

Yes - we should get rid of FDT for good. Takes just some time for coding, but dont have time for that.

EDIT - I think need to expand a bit on this. Yes, the first problem we found out was the incapability of FDT being configured for higher number com ports. I have spent several telephone conversations just explaining how FDT must use preferrably com 1-4. FDT is also cumbersome to install for the functionality - making support need of an average user to raise. Then the latest FDT version even has a bug which prevents .bin files being flashed to ecu. I needed to write a conversion subroutine into ECUeditor that sends .mot to FDT instead of .bin.

The protocol that FDT uses for flashing is very easy and well described in the literature. Its just getting over to writing it to visual basic. In ecuexplorer the source for this in .cpp already exists. Also as part of the early hacking experiments we tested the initial flashing subroutines.



-- Edited by PetriK at 06:22, 2008-10-14

__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 74
Date:



-- Edited by ffaspector on Saturday 17th of October 2009 12:31:04 PM

__________________


Guru

Status: Offline
Posts: 963
Date:

Using the USB as COM9 when I would hit connect it would be able to find the port but then give the

Trying 9600
Trying 4800
Trying 2400 etc.

error.

I put it on a scope and it wasn't actually sending any data.

I tried uninstalling and reinstalling FDT with no luck.

When I was able to change it to COM3 it started working.

__________________


Guru

Status: Offline
Posts: 1344
Date:

i had this problem when i first started flashing,i had too many com ports assigned and had to remove alot of them and assigned my re-flashing box on com 4,after that all was ok.

__________________

09 busa.????? now what....still got what it takes.......!

I got what you need...!
www.poweredbyford.com

www.marc@poweredbyford.com

 



Veteran Member

Status: Offline
Posts: 74
Date:



-- Edited by ffaspector on Saturday 17th of October 2009 12:31:12 PM

__________________


Guru

Status: Offline
Posts: 2338
Date:

Renesas may then have resolved the bug - when loading a .bin it did not load correctly, only loaded .mot files. When trying to reflash it did not flash anything to the ecu - did start flashing though. ECU/Bike did not start anymore after flashing as everything seemed to be flashed as zeros.

Took one night to resolve as it was one of the local flashers who found that bug first and its not a first thing you think over a telephone conversation. Only after installing that version by myself figured out the real problem being within FDT.




__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Guru

Status: Offline
Posts: 1247
Date:

RidgeRacer wrote:

Using the USB as COM9 when I would hit connect it would be able to find the port but then give the

Trying 9600
Trying 4800
Trying 2400 etc.

error.

I put it on a scope and it wasn't actually sending any data.

I tried uninstalling and reinstalling FDT with no luck.

When I was able to change it to COM3 it started working.



This same error will arise if you don;t have the correct com port programmed in the fdt setup. Had it happen to me a few times until I realized I goofed on selecting the proper com port in the setup.


-- Edited by sportbikeryder at 19:46, 2008-10-19

__________________


Guru

Status: Offline
Posts: 2338
Date:

Yes, sorry have not kept the FDT instructions here on this general 7052 side. Here you are link to the instructions. Here is an old link how to set up FDT properly.
http://www.activeboard.com/forum.spark?forumID=99460&p=3&topicID=14963290

We initially started on the Hayabusa side on this forum, but then decided to have a separate sh7052 forum as so many bikes have sh7052 processor. Some of the history of how it all come toghether is documented here:
http://www.activeboard.com/forum.spark?forumID=99460&p=3&topicID=14206571
http://www.activeboard.com/forum.spark?forumID=99460&p=3&topicID=14784871
http://www.activeboard.com/forum.spark?forumID=99460&p=3&topicID=14102325

The history is a bit scattered and its sometimes difficult to find what is the latest status.

We really should compile a timeline here - or maybe even add how all this started from the late '80s when it was all about superchips for camaros (thats when first time got involved reflashing an ecu smile.gif, but things have sincerely developed since those days.)




__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Member

Status: Offline
Posts: 22
Date:

When loading a bin file into the FTD software, the user flash shows all zeros. What is going wrong/on? The connection to the ecu works. I am using FTD 4.02 R1.

__________________


Guru

Status: Offline
Posts: 963
Date:

Which bin file are you loading?  Have you tried on of the bins of this site?

__________________


Member

Status: Offline
Posts: 22
Date:

Switching back to version 4.01 works. All bins are from this site.

__________________


Veteran Member

Status: Offline
Posts: 80
Date:

hi all, what format does the binary file need to be in? and how do you load it into FDT?

my binary is just that, all binary, but looking at the help in FDT there's a whole lot of guff about using a format like this ... (see below)

am I missing something obvious here, have only just returned to this work after another prolonged absense (working overseas), so am still not fully up to speed on where you guys are at. There's a lot to read and it's spread all over the place ... so my apologies for asking Qs before I RTFM.

Cheers,
Mark


// config info
...comment line, for information only
format   HEX
...specify formatting for the data section of the file
area     User Flash
...data will be written into the "User Flash" area
address  0xF000
...data will be written at address 0xF000 in "User Flash"
size     6
...data will be read in as 6 byte blocks from the data section below
...empty line (ignored)
// code list
...comment line, for information only
index    data
...header pair for data (denotes start of list)
000001   ABCD24000001
...first index and data - 6 bytes as specified by 'size' above
000002   ABCD24000002
...second index on new line



__________________


Veteran Member

Status: Offline
Posts: 80
Date:

don't worry, I found my error ... i have to label the file with a *.bin extension and load it in as a binary
my error, I didn't have an extension on the file, and loaded it in using the all files (*.*) option
(that doesn't work so well!)

cheers,
Mark

__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.

Tweet this page Post to Digg Post to Del.icio.us


Create your own FREE Forum
Report Abuse
Powered by ActiveBoard