[Efi332] Requirements Design Document for EFI

[Andrei Chichak]

At 07:23 AM 10/10/2005, you wrote:
>Hello,
>
>Has anyone written a requirements and/or design document for EFI or engine
>management that they would care to share?

I've been meaning to send a message about this for a while now. I was 
hoping that someone else would chime in since I think I have either 
discussed this with either you or Jeff off-list.

My position is coming from finishing off a project where I used the '332, 
the TPU, the SPI ADCs, serial switches and an RTOS. It was for a piece of 
medical equipment, but a lot of it is applicable to this project.

I worked with an MPC562 board for a while, but I have to look at where I 
want to spend my money and time. I can see using the '332 again in more 
projects. I have some Axiom CMM332 boards, which make a great off the shelf 
compute core for these projects, working compilers, debugging modules,  and 
a lot of experience in the gotchas of the '332.

For me, the cost of switching to PPC is more that I can justify at this point.

But, you know, this doesn't change the requirements, the algorithms, the 
structure, or what is needed to get a system going. I learned, through 
making lots of mistakes, that the first thing that you need to write is a 
FLASH based error logger. This calls out having the FLASH writers and 
serial comm interpreter in place. I have been playing around with simpler 
interfaces for ignition coil driving, and PWM idle motors. None of this 
stuff is specific to PPC or '332 or Megasquirt or what have you.

SO, yes I have the start of a requirements/design doc that I would be glad 
to share. Is anybody interested?

Andrei