[newb]Could this be of any use (in the proper hands ofcourse) to us?

dont flame...I dont know much about this ecu programming stuff...[/newb]

http://www.technosquareinc.com/flashecu.htm

 

The product is $$$$ last time somone asked about the price. But even if you have the ability to flash the memory, what data are you going to flash it with? You would need to know how to read machine codes and understand what various codes mean. Way too much of a learning curve unless you are a computer programmer with experience in machine code programming. I'm a programmer but my experiences are in 4th generation programming languages like C, C++, ABAP and VB. I haven't done any practical machine code programming.

 

Yea i figured that, I know a few languages too and very little machine level... thats why I said in the proper hands...


Thanx for the info...

 

are we talking about basic like 0's and 1's?? that would be a b1tch..

 

No..not Binary programming. It's one level higher.

Something like this...

$7D0B LDA A #1 $86 $01
$7D0D .loop INC A $4C
$7D0E CMP A #101 $81 $65

 

so it is assembly language... not that hard..

 

Yeah...it's pretty much assembly langauge. The auto manufactures would protect their codes by throwing in bunch of irrelevant codes. It just makes it even harder to make sense what does what. You would probably have to write you own complier and misc utilities. I think it's hard...but then again my background isn't really CS.

 

No, it won't be in assembly language. It will give you machine code, which is basically just the 1's and 0's. You'll need to find the proper dis-assembler for the chip used in the ECU, which last I've read nobody has discovered what chip that is.

Dissasembled code is VERY hard to work with. Its not like looking at the assembely source, there are no lables, comments, .data or .text sections, or anything like that. You can't look for a variable called rpm_limit or wot_fuel_map. You'll see nothing but the address that reference that area in memory (ie, the rpm_limit may be stores at 0xA83D, or god knows where).

You'll have to spend days or weeks mapping out the entire memory structure, and tracing each line in the application before you'll even know which areas in memory are for storage, let alone what is stored where.

This is why people charge big bux for ECU upgrades! Its a lot of work! It could be done by any competent Computer Engineer or Computer Scientist..but I don't know who'd have that kind of free time.

That being said, I am a "Computer Scientist" and would love to see a "ROM Dump" from our ECU's.

[EDIT]
Worst of all, not all dis-assemblers will map DATA sections of a rom...just the code part which is useless.
[/EDIT]

 

An email I got from Danny Lee of TecnoSquare:


It's the same ole song.

 

Well...My background isn't CS so I was talking out of my azz previously anyway

 

Its a common mis-conception that you can plug a device into a ECU (or other embedded device) and "see" the program that's running.

If I (or any other programmer) could get a copy of the sources that Nissan used we'd all have FREE modified ECU's. If only it were that easy.

 

lets start making some ECU's

 

Make sure to include the buffer overflow. I know. It comes standard.

 

Aren't the 95 - 96 ODBI? That webpage said this 'system' is for ODBII cars. Then again you are talking about an actual ecu upgrade not this programming system..... right?

 

Techtom Japan in English

Flash Writer

Now this looks VERY interesting!
Mighty Map&MT2000

 

This info is on the English site. Thats the ? I was asking....

 

I asked the guy if it worked with the 97 ECU and that was the email I got back.

 

Some people have said that all 4th gens are ODBII, including 95-96. However, I think that earlier 95's are ODBI. JWT recently said that the ECU off of my May 1995 SE is NOT upgradeable by them... maybe that is why.