CPU's

[Bruce Plecan]

If the table lines up then you can have a high level of confidence that they
are right.
If the table looks really strange the there is something wrong.
Tuner cat spits it out if the wrong mask, from what I've seen
You can always try it, if you aren't sure make a small change and see what
happens if your that worried about it.
Or wire up an ecm bench, and run diacom with it and reafirm things.
Bruce


> now i am getting paranoid.  i am not a programmer (nor am i going to
> pretend to be), i fight my way around & make it happen but a lot of this
is
> above my head.  If there might be two of Masks for what i think my
> application is (I have what i think are certain knowns, that i am making
> assumptions from) , how am i going to know for certain when i plug it into
> Tuner cat or WinBin that I am going to be editing the right things for
what
> i think is a certain value in a table?  i have plugged my bin into the
> WinBin & it looks right. that is to say that the tables are what i would
> expect to be reasonable & do not have any large numbers where i would not
> think they ought to be.  but that is not to say that this is not the right
> things.
>
> thanks again for the help.  THIS, is why i am hanging around, soaking up
as
> much as i can.  this , as far as i am concerned, is what helping fellow
> enthusiasts, is all about.
>
> BW
>
>
> > [Original Message]
> > From: Ludis Langens <ludis at cruzers.com>
> > To: <gmecm at diy-efi.org>
> > Date: 12/5/00 2:29:08 AM
> > Subject: Re: CPU's
> >
> > Bob Wooten wrote:
> > >
> > > So let me see if i have this straight.  the BCC is not in the
firmware,
> > > though the prom ID is.  the prom ID has the detailed information
> specific
> > > to the application & it can lead one to the BCC.
> >
> > The scan id in the chip does not have detailed info.  If you are lucky,
> > the scan id by itself is enough to figure out the matching BCC.  Usually
> > you have to use the context (what mask byte, what year, what engine,
> > etc.) to get from the scan id to BCC.  If you are unlucky, one
> > ECM+mask+application will have duplicated scan ids.  Someone posted such
> > a chip on incoming.  Its one of two possible BCCs, I don't know which.
> >
> > > here is what i am not following, you said that the Mask byte (not two
> bits,
> > > forgot the Basic EE from school), "might not have the same table
> layout".
> > > so, this means that there really is not a simple rule here.  i was
> thinking
> > > (assuming i suppose), that this being the truth would make it rather
> easy
> > > to write stuff like Win Bin & Tuner Cat for that Mask byte.  it
appears
> > > not.
> >
> > There at least two-each of masks 32, 6E, and 8D.  The changes might be
> > bug fixes with unchanged table layouts, or an extra table or constant
> > might have been added.  The paranoid chip editor should be checking
> > either the program code or perhaps some of the table headers.
> >
> > --
> > Ludis Langens                               ludis (at) cruzers (dot) com
> > Mac, Fiero, & engine controller goodies:  http://www.cruzers.com/~ludis/
> >
> >
> >
> --------------------------------------------------------------------------
--
> > To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
> > in the body of a message (not the subject) to
majordomo at lists.diy-efi.org
> >
>
>
>
> --- Bob Wooten
> --- r71chevy at earthlink.net
> --- 71-91 Camaro
>
>
> --------------------------------------------------------------------------
--
> To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
> in the body of a message (not the subject) to majordomo at lists.diy-efi.org
>
>

----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org