Reply to thread

Hello!


Thanks for your interest, I almost thought this thread was completely dead!


Yes, you are correct. The ostrich is modifying the ROM. The ostrich also has a trace feature that is basically a feedback to a program (tunerpro) of what address in ROM the MCU is currently reading from. The RAM is read from the serial port.


The NSX has 3 ignition maps and 4 fuel maps all contiguous. For N/A purposes they are about as high resolution as you are going to get. 16x20 loadXrpm = 320cells of resolution per map. I also have a logical solution to this when used for tuning for boost, I don't plan on loosing any resolution 0- actually doubling it.


The NSX ROM is really hard pressed for free space - even for small add-on programs - never mind another map - but, I am working on this as we speak. I think I may have found a way to add up to 16K of free space if I can get the chip addressing and enable signals figured out. The Legend, especially the 93-95, have a bit of free space.


I am actually working on getting the (large) portion of code that is inside of the MCU running 100% off chip on a 64K ROM (or the ostrich). From what I'm seeing so far, it's probably not really going to be necessary to run the ECU that way but it would help with the reverse engineering process and I enjoy the challenge.


-Matt


Back
Top