[Diy_efi] Continuing the chip switcher "problem"
WSCowell at aol.com
WSCowell at aol.com
Tue Feb 15 07:34:53 GMT 2005
--===============67359263005149195==
Content-Type: multipart/alternative;
boundary="-----------------------------1108452778"
-------------------------------1108452778
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Marcello,
I'm not experienced with the MCU's in use in your ECU, but widely
experienced in the old 8-bit families from various manufacturers, and particularly
those used in the old 8 and early 16-bit computers. In all of these, the
E(E)PROM OE bar line was derived from logic circuitry designed to sense when that
particular part of the memory map was being accessed, often in conjunction with
the "READ" signal. So not only did you have to be looking at that part of
the memory map, you had to be trying to read it also.
With your OKI MCU however, because most of the accessing of the memory map
is inside the chip, there is a possibility that OE bar is driven from one of
the chip's output ports. You will just have to trace it back patiently I
think. Good luck.
Will
-------------------------------1108452778
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DUS-ASCII">
<META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>Marcello,</DIV>
<DIV> </DIV>
<DIV>I'm not experienced with the MCU's in use in your ECU, but widely=20
experienced in the old 8-bit families from various manufacturers, and=20
particularly those used in the old 8 and early 16-bit computers. In al=
l of=20
these, the E(E)PROM OE bar line was derived from logic circuitry designed to=
=20
sense when that particular part of the memory map was being accessed, often=20=
in=20
conjunction with the "READ" signal. So not only did you have to be loo=
king=20
at that part of the memory map, you had to be trying to read it also.</DIV>
<DIV> </DIV>
<DIV>With your OKI MCU however, because most of the accessing of the memory=20=
map=20
is inside the chip, there is a possibility that OE bar is driven from one of=
the=20
chip's output ports. You will just have to trace it back patiently I=20
think. Good luck.</DIV>
<DIV> </DIV>
<DIV>Will</DIV>
<DIV> </DIV></FONT></BODY></HTML>
-------------------------------1108452778--
--===============67359263005149195==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
diy_efi mailing list
diy_efi at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/diy_efi
--===============67359263005149195==--
More information about the Diy_efi
mailing list