[Diy_efi] Mopar PCM
David Cooley
n5xmt at bellsouth.net
Wed Oct 27 21:15:26 GMT 2004
--===============30937039691171808==
Content-Type: Multipart/Alternative;
boundary="------------Boundary-00=_7IH9QL80000000000000"
--------------Boundary-00=_7IH9QL80000000000000
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hmm... I do have a disassembler for windows programs! =0D
=0D
-------Original Message-------=0D
=0D
From: A list for Do-It-Yourself EFI=0D
Date: 10/27/04 16:02:24=0D
To: A list for Do-It-Yourself EFI=0D
Subject: Re: Re: [Diy_efi] Mopar PCM=0D
=0D
Anyway to reverse engineer the application I sent you to see how Chrysler
accesses the flash via SCI? Data logger maybe?=0D
>=0D
> From: "David Cooley" <n5xmt at bellsouth.net>=0D
> Date: 2004/10/27 Wed PM 12:52:31 GMT=0D
> To: <diy_efi at diy-efi.org>=0D
> Subject: Re: [Diy_efi] Mopar PCM=0D
>=0D
> As I said, even the factory flash file looks identical to what is in t=
he=0D
> flash proms... it is both flash concatenated into a single file with a=0D
> checksum so the DRB can check for file corruption before it applies the=
=0D
> flash. The flash appears to be strictly data, and no code at all. I
ihave=0D
> to set up SCI direct to the CPU's to see if I can dump the ROM. Once I=
do=0D
> that I will have a better idea what is going on... and the info I have=
is=0D
> not speculation... I have received it from a person that works for a=0D
> company that assembles, programs, reworks and tests the PCM's for Chrys=
ler
=0D
> 96 and newer Chrysler PCM's are a totally different animal than the 95 =
and=0D
> earlier units.=0D
>=0D
>=0D
>=0D
> -------Original Message-------=0D
>=0D
>=0D
>=0D
> From: A list for Do-It-Yourself EFI=0D
>=0D
> Date: 10/26/04 22:42:52=0D
>=0D
> To: diy_efi at diy-efi.org=0D
>=0D
> Subject: Re: [Diy_efi] Mopar PCM=0D
>=0D
>=0D
>=0D
> again a dump wont do you any good. every piece of chyrsler code ive eve=
r=0D
> seen has a copyright in asccii test at the bottom of the rom. these do =
not
=0D
> the only clear reasoning is that the adress line are muxed or something=
=0D
> during programming. this is not even remotely beyond the capability of =
the=0D
> 68hc vriants running in these ecms.=0D
>=0D
>=0D
>=0D
=0D
=20
--------------Boundary-00=_7IH9QL80000000000000
Content-Type: Text/HTML;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"IncrediMail 1.0" name=3DGENERATOR></HEAD>
<BODY style=3D"BACKGROUND-POSITION: 0px 0px; FONT-SIZE: 12pt; MARGIN: 5px=
10px 10px; FONT-FAMILY: Arial" bgColor=3D#ffffff background=3D"" scroll=3D=
yes ORGYPOS=3D"0">
<TABLE id=3DINCREDIMAINTABLE cellSpacing=3D0 cellPadding=3D2 width=3D"100=
%" border=3D0>
<TBODY>
<TR>
<TD id=3DINCREDITEXTREGION style=3D"FONT-SIZE: 12pt; CURSOR: auto; FONT-F=
AMILY: Arial" width=3D"100%">
<DIV>Hmm... I do have a disassembler for windows programs! </DIV>
<DIV> </DIV>
<DIV id=3DIncrediOriginalMessage><I>-------Original Message-------</I></D=
IV>
<DIV> </DIV>
<DIV id=3Dreceivestrings>
<DIV dir=3Dltr style=3D"FONT-SIZE: 11pt" <i><B>From:</B></I> <A href=3D"m=
ailto:diy_efi at diy-efi.org">A list for Do-It-Yourself EFI</A></DIV>
<DIV dir=3Dltr style=3D"FONT-SIZE: 11pt" <i><B>Date:</B></I> 10/27/04 16:=
02:24</DIV>
<DIV dir=3Dltr style=3D"FONT-SIZE: 11pt" <i><B>To:</B></I> <A href=3D"mai=
lto:diy_efi at diy-efi.org">A list for Do-It-Yourself EFI</A></DIV>
<DIV dir=3Dltr style=3D"FONT-SIZE: 11pt" <i><B>Subject:</B></I> Re: Re: [=
Diy_efi] Mopar PCM</DIV></DIV>
<DIV> </DIV>
<DIV>Anyway to reverse engineer the application I sent you to see how Chr=
ysler accesses the flash via SCI? Data logger maybe?</DIV>
<DIV>></DIV>
<DIV>> From: "David Cooley" <<A href=3D"mailto:n5xmt at bellsouth.net"=
>n5xmt at bellsouth.net</A>></DIV>
<DIV>> Date: 2004/10/27 Wed PM 12:52:31 GMT</DIV>
<DIV>> To: <<A href=3D"mailto:diy_efi at diy-efi.org">diy_efi at diy-efi.=
org</A>></DIV>
<DIV>> Subject: Re: [Diy_efi] Mopar PCM</DIV>
<DIV>></DIV>
<DIV>> As I said, even the factory flash file looks identic=
al to what is in the</DIV>
<DIV>> flash proms... it is both flash concatenated into a single file=
with a</DIV>
<DIV>> checksum so the DRB can check for file corruption before it app=
lies the</DIV>
<DIV>> flash. The flash appears to be strictly data, and no=
code at all. I ihave</DIV>
<DIV>> to set up SCI direct to the CPU's to see if I can dump the ROM.=
Once I do</DIV>
<DIV>> that I will have a better idea what is going on... a=
nd the info I have is</DIV>
<DIV>> not speculation... I have received it from a person =
that works for a</DIV>
<DIV>> company that assembles, programs, reworks and tests the PCM's f=
or Chrysler.</DIV>
<DIV>> 96 and newer Chrysler PCM's are a totally different animal than=
the 95 and</DIV>
<DIV>> earlier units.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> -------Original Message-------</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> From: A list for Do-It-Yourself EFI</DIV>
<DIV>></DIV>
<DIV>> Date: 10/26/04 22:42:52</DIV>
<DIV>></DIV>
<DIV>> To: <A href=3D"mailto:diy_efi at diy-efi.org">diy_efi at diy-efi.org<=
/A></DIV>
<DIV>></DIV>
<DIV>> Subject: Re: [Diy_efi] Mopar PCM</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> again a dump wont do you any good. every piece of chyrsler code=
ive ever</DIV>
<DIV>> seen has a copyright in asccii test at the bottom of the rom. t=
hese do not.</DIV>
<DIV>> the only clear reasoning is that the adress line are muxed or s=
omething</DIV>
<DIV>> during programming. this is not even remotely beyond the capabi=
lity of the</DIV>
<DIV>> 68hc vriants running in these ecms.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV></TD></TR>
<TR>
<TD id=3DINCREDIFOOTER width=3D"100%">
<TABLE cellSpacing=3D0 cellPadding=3D0 width=3D"100%">
<TBODY>
<TR>
<TD width=3D"100%"></TD>
<TD id=3DINCREDISOUND vAlign=3Dbottom align=3Dmiddle></TD>
<TD id=3DINCREDIANIM vAlign=3Dbottom align=3Dmiddle></TD></TR></TBODY></T=
ABLE></TD></TR></TBODY></TABLE></BODY></HTML>
--------------Boundary-00=_7IH9QL80000000000000--
--===============30937039691171808==
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
--===============30937039691171808==--
More information about the Diy_efi
mailing list