shane bigler wrote:This is very intriguing. Why is possible to burn chips for so many other makes of vehicles but not for the SR20det? I have friends that get maps and burn their own chips and tune their own ecu's at home but from the research Im doing on tuning my ecu this cannot be done. I mean whats Jim wolf doing that we cant do at home? I really dont want to mail off my ecu but getting E-manage or S-AFC doenst have the same versatility as my friends are getting with burning their own chips. I dont have any experience with this so whats the dilly yo?
Some of the earlier ECUs for the SR20DET are really easy to reprogram the EPROM. The difference between the older ECUs and new ECUs is that the older models have an external, generic EPROM (external from the MPU). You can easily pull it off the board and get an image of whats programmed on it. A replacement chip with a new program loaded on it cost a few dollars. The MPUs used are generic, off the shelf chips, with the programming manuals readily available (Nissan uses Hitachi).
As time progressed, Hitachi started farming the work out to a subsidiary called JECS. They started introducing propriatary chips, combining the MPU and EPROM together, and basically making it near impossible to reverse engineer what was done. The newer ECUs don't have external EPROMS, but do have an exteral data and address bus that you can hook up an EPROM to mounted on a separate board. The programming from the factory for the ECU now lives in the MPU which is a little (or alot) more difficult to get out. Jim Wolf managed to get it out, and the rest was easy.
If you cruise some of the Japanese and Australian web sites about the SR20DET, you can find lots of info on the older ECUs. As soon as the ECU code moved onboard to the MPU, there's not a lot of info available.
Oh, and the comment that C/C++ is too slow, that's just not true. There are many excellent compilers for embedded systems out there that can generate some amazingly efficient compiled code. Anyone who programs in assembly by choice today is not doing themselves any favors. I think assembly is still important to know (it teaches you a hell of a lot about how memory works), but developing in it is just not practical anymore considering development time, maintainability, debugging, and interfacing to the millions of provided software device libraries that usually accompany the hardware you buy.
Chris.