Page 1 of 4

Processor Datasheets

PostPosted: Wed Dec 29, 2004 9:26 pm
by KGreb
Re-hasing some of the processors discussed on the original NASIOC thread:

'02 2.0L Turbo ECU related
====================================
D151851-3830 160 pin QFP
Suspected Motorola M68HC16 core, possibly MC68HC916 based on usage of the D151851-0710 in the FD3S RX-7 -- see this page. Translation here would be greatly appreciated.
MC68HC916 datasheet
CPU16 core Programmer's Guide

'04+ 2.5L Turbo ECU related - 2 processors
====================================
Renesas 7055 (SH-2 processor) overview and links
Seen in '04 STi, all '04 2.5L?

Renesas 7058 (SH-2 processor) overview and links
Seen in '05 LGT, all '05 2.5L?

SH-2 processor datasheet

D151851-4410 132 pin BQFP
See above. No potential pin for pin equivalent ID'd.

PostPosted: Wed Dec 29, 2004 9:32 pm
by Guest
On the Denso HC916..

For the 2002, 2003 WRX, a quick way to see the CPU part is in the ECU rom at location 0x60000 or so.

There aren't any publicly available datasheets for this chip as far as I can tell

PostPosted: Wed Dec 29, 2004 9:37 pm
by scooby5
Sorry, forgot to post the above while logged in.

In any case, I can't see to be able to attach images , but I have a screenshot of the hex editor, the 0x60000 address in the ROM is very helpful :)

PostPosted: Thu Dec 30, 2004 1:15 am
by mumbles
Send the pics to brendan "AT" brendan-stewart.com i'll host em.

If you can host em, just put [I M G] around it and [/I M G]

PostPosted: Thu Dec 30, 2004 1:17 am
by mumbles
btw how are you seeing the info on the rom? Where are you connecting at? Detailed info would help :)

PostPosted: Thu Dec 30, 2004 8:52 am
by Guest
Image

PostPosted: Thu Dec 30, 2004 8:54 am
by mumbles
Woops i thought cookies kept us logged in.

IN any case there it is. Now what's the next step?

PostPosted: Thu Dec 30, 2004 10:19 am
by Synx
Next step is to find out how they got the EEPROM images and then pull our own images to start disassembeling and figureing out, which by the looks of that picture scooby5 is allready well on his/her way. Im not so sure is a great idea for us to share bin's on this site for legal reasions.

PostPosted: Thu Dec 30, 2004 10:51 am
by mumbles
Well we could pass them around to each other. 8)

PostPosted: Thu Dec 30, 2004 10:55 am
by mumbles
btw how the hell do you get the info from the chip?

Here's a pic of my ECU JDM VER7 AF481;

Image

PostPosted: Thu Dec 30, 2004 11:29 am
by Nemis
other ecu motherboard photo
http://wrx.fc2web.com/ecucover.htm


and look at : http://www.warwickcontrol.com/products/ ... mulink.htm

prodrive logo ?!?

PostPosted: Thu Dec 30, 2004 2:22 pm
by bofh
Only way to really look inside is to develop an interface. I have been looking, but I am WAY out of my depth. I notice there is one other Houston guy. Should we have a shop day? :roll: I still think an Elm based tool can be used with some modification to get just about everything we need... I may be wrong, but I need to see it before I admit it. :)

PS: Can we keep with picture size down? Kinda tough when you are at your Dad's for the holidays, with dial up, and 800x600. <sigh>

PostPosted: Thu Dec 30, 2004 4:23 pm
by Guest
The Elm tool does all the overhead for the OBDII protocol not just the raw line level conversions, so it will not work with the Subaru Select protocol even if it uses the same line levels as OBDII, its totally different packeting and baud. However there are some very easy to make boards that will do the line level conversions if infact the Subaru Select protocol is ISO 9141-2 compatible.

PostPosted: Thu Dec 30, 2004 4:25 pm
by Synx
Yes cookies are a must here, is there something the user has to to or is it a server thing, that last post was me. Actually maby just remove guest posting im sure that would help. ;)

PostPosted: Thu Dec 30, 2004 7:50 pm
by cboles
I'll check out the cookie issue - they are enabled for the board, but maybe something isn't set up right. What do you have to do to recreate the "guest" posting problem?