NTProgCE now available...
Posted: Wed Jan 31, 2007 10:55 pm
hey guys
I am finally putting up the NIStune programmer software install package. Will be doing documentation shortly
It is available from the usual download directory. It will take Encoded NIStune Files (.ENT) which contain the standard ROM binary and the USBConsult/eXtended Consult firmware code
ENT files will be available currently only on request with a need to program. Eventually they will be made available for all ECU types
Boards are reprogrammable by soldering the program jumper and then using an adaptor board with the Willem programmer. Currently this supports
Type 1 (6802/6303 legacy) - Rev3/3A
Type 2 (6303 consult)
Type 3 (CPLD Rev B/F)
Type 4 (CPLD Rev B/F)
Type1/2 have a simple adaptor board consisting of two diodes and a resistor.
Type 3/4 have an 8->16 bit adaptor board with additional parts on it. All of these boards take 64K ENT files even if the ROM image is 32K this is because we put code outside the 32K area because there is just not enough free space
Eventually we will have a dedicated willem based programmer which will take both boards, schematics done just needs to be layed out and prototyped
I am finally putting up the NIStune programmer software install package. Will be doing documentation shortly
It is available from the usual download directory. It will take Encoded NIStune Files (.ENT) which contain the standard ROM binary and the USBConsult/eXtended Consult firmware code
ENT files will be available currently only on request with a need to program. Eventually they will be made available for all ECU types
Boards are reprogrammable by soldering the program jumper and then using an adaptor board with the Willem programmer. Currently this supports
Type 1 (6802/6303 legacy) - Rev3/3A
Type 2 (6303 consult)
Type 3 (CPLD Rev B/F)
Type 4 (CPLD Rev B/F)
Type1/2 have a simple adaptor board consisting of two diodes and a resistor.
Type 3/4 have an 8->16 bit adaptor board with additional parts on it. All of these boards take 64K ENT files even if the ROM image is 32K this is because we put code outside the 32K area because there is just not enough free space
Eventually we will have a dedicated willem based programmer which will take both boards, schematics done just needs to be layed out and prototyped