A31 RB20DET '.ent' file

Nistune topics specific to the 6802 cpu

Moderator: Matt

Post Reply
zrated
 

Posts: 41
Joined: Mon Nov 05, 2007 10:04 pm
Location: Western Australia
Contact:

A31 RB20DET '.ent' file

Post by zrated »

I'm having problems trying to get a type 1 rev 3b board working in an A31 rb20det.

The ECU works fine with an OEM eprom installed however when installing the nistune board we can't connect via the USB consult. The car still runs OK, it's just a matter of being unable to connect to the ECU.

The ECU is a 23710 94L10 (MEC-R113) however the only *.ent file we could find to program the board with is the "A31_RB20DET_73L10_MEC-R103D_AT.ent"

Is this where I am going wrong?
louiswun
 

Posts: 256
Joined: Tue Apr 07, 2009 1:11 am
Location: Hong Kong

Re: A31 RB20DET '.ent' file

Post by louiswun »

zrated wrote:I'm having problems trying to get a type 1 rev 3b board working in an A31 rb20det.

The ECU works fine with an OEM eprom installed however when installing the nistune board we can't connect via the USB consult. The car still runs OK, it's just a matter of being unable to connect to the ECU.

The ECU is a 23710 94L10 (MEC-R113) however the only *.ent file we could find to program the board with is the "A31_RB20DET_73L10_MEC-R103D_AT.ent"

Is this where I am going wrong?
I have just check your ECU parts numbers,
your ECU is from C32 Laurel RB20DET AT FR 23710-94L10 MEC-R113,
it is using 27C128 rom, this is early model of RB20DET,
I guess early model RB20DET ECU does not have full consult function.
try to use a rom reader reader your get your stock rom image,
send it to Matt, me might know how to help.

Or try to use the address for C33 RB20DET 27C128,
I'm not sure, most 27C128 A31 RB20DET in Hong Kong does not have consult plug.

OR, just change to another 27C256 RB20DET ECU, with full consult function.
Matt
Site Admin
 

Posts: 9005
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Post by Matt »

see attached

some of the ECUs (A31 and J30 require special Xilinx programming since the normal memory area we use for USB comms has ROM code there). So I have to adjust the location of USB access somewhere else in the ROM to use it.

F700 is a common unused location (needs to be 0x0100 bytes memory mapped area) for most ECUs apart from these
Attachments
Nistune Technical Bulletin 001.pdf
Type 1 board - blank boards ordering
(15.47 KiB) Downloaded 239 times
Matt
Site Admin
 

Posts: 9005
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Post by Matt »

also we cannot do the 94Lxx series boards (use the 73Lxx ENT instead in these)

this is because there is no spare area of 0x100 (256) bytes to memory map in the USB functionality since the ROM image takes up the entire space available
Post Reply