[Diy_efi] new EFI controller

[Greg Hermann]

At 6:48 PM 3/11/03, Bevan Weiss wrote:
>I don't think I'd want to run a full fledged linux kernel on it, especially
>with the added execution cost of real time scheduling.
>I agree that the cost of the MPC565 isn't ideal, especially in low volumes.
>However the level on integration removes any extra costs that would
>otherwise be required.  All that's really left for the hardware design is
>connecting up some filtering components and some protection for the inputs.
>Outputs just require the driver hardware to be sorted, which shouldn't cost
>much.  It should easily come in under $500 for the entire unit.

Little question that the 565/6 will DO the job, and do it well. Price isn't
ideal, but within reason, and, as Bevan says, because of the level of
integration, there are cost savings in other areas. Not to mention that the
integration produces reliability gains for a number of reasons.

IF we could quit quibbling over which processor might cost $5 less and get
some hardware under way, then we might be able to get after the REAL
problem, which, in my mind, is HOW to set about operating a capable,
REASONABLY priced, controller in ways which might IMPROVE engine
performance significantly above what an oem controller is capable of !

There ARE controllers out there, commercially available (sort of), which
will do this, but they START at about $15 to $20K !!!

Greg
>
>----- Original Message -----
From: "Perry Harrington" <pedward at apsoft.com>
>To: "List for general do-it-yourself EFI talk" <diy_efi at diy-efi.org>
>Sent: Tuesday, March 11, 2003 6:07 PM
>Subject: Re: [Diy_efi] new EFI controller
>
>
>> I remember looking at the 565 a while ago and thinking of running Linux on
>it.
>> The ~$100 per chip was a detractor though.  Linux as the underlying OS for
>an
>> ECU could do a lot for you I think.
>>
>> --Perry
>>
>> On Tue, Mar 11, 2003 at 05:18:52PM +1300, Bevan Weiss wrote:
>> > Depends on lots of things, remember that there's much more computing to
>a
>> > car than just the engine.
>> > ie one of the 32bit processors might be the engine, the other one might
>take
>> > care of such things as the indicators, the door light, windsheild
>wipers,
>> > central locking, etc.
>> > Or it might be just dedicated to traction control (ie abs), or it may be
>> > used in 4WS (4 wheel steering).  Then again it might be used to adjust
>the
>> > drivers seat via electronics :)
>> > Ya just never really know what they're using for what application.
>> >
>> > The important thing for us to pick up is, Motorola has designed the
>> > MPC555/565/566 as automotive engine control devices.  This means that
>> > there's no fussing around trying to get something simple like an engine
>> > position reference.  It's a simple two instruction kinda thing (damn I
>love
>> > the TPU :) )
>> > Just think about how hard that would be to code using a TriCore chip or
>> > such.
>> > All the onchip FLASH and RAM are added bonuses, no 'need' for an
>external
>> > bus interface.  (However I think I'll still put one on the board).
>> > It's just a great little chip family.
>> >
>> > Thanks for the comments,
>> > Bevan Weiss
>
>_______________________________________________
>Diy_efi mailing list
>Diy_efi at diy-efi.org
>http://www.diy-efi.org/mailman/listinfo/diy_efi



_______________________________________________
Diy_efi mailing list
Diy_efi at diy-efi.org
http://www.diy-efi.org/mailman/listinfo/diy_efi