[Efi332] Hey guys - what's up? (plain int vs que)

Mon Feb 6 02:19:11 UTC 2006

The queued stuff is a definite improvement on the SCI for continous streams. On the receive side though, where you have intermittent short messages, the SCI is better so you may want to use a hybrid solution . YMMV.

If you can, would you send me a pic of your hardware off list (the list won't take attachments)? I'd like to see your setup.

-----Original Message-----
From: Paul Helmuth <PaulHelmuth at SprintMail.com>
To: efi332 at diy-efi.org
Sent: Sun, 5 Feb 2006 16:21:19 -0600
Subject: Re: [Efi332] Hey guys - what's up? (plain int vs que)

Jeff,

Yes - I'm with you on the two different flavors. I think it makes sense to go ahead and implement the queued stuff (if possible).

-Paul
----- Original Message ----- 
From: BowTieVette at aol.com 
To: efi332 at diy-efi.org 
Sent: Sunday, February 05, 2006 2:44 PM
Subject: Re: [Efi332] Hey guys - what's up?

Hey Paul,
When you refer to interrupt driven serial comm, there are two flavors of course, and I'm not sure which you mean. There is the regular byte by byte SCI, and there is the 16 byte queue QSCI layer. 
The interrupt driven SCI code has been around for a long while having been adapted from a Motorola app note years ago. You can find that in the now somewhat dated efi332 software archives at SourceForge. 
If you're after QSCI, then you'll need Dave's edition which works quite well.
jc

In a message dated 2/5/2006 12:41:59 P.M. Eastern Standard Time, sailors3 at comcast.net writes:
Hi Paul,

Nice to hear from you! I know what you mean about side projects, my car project get set aside for 2 1/2 years while I built a large addition on the back of our house. I had just bought a 1998  LS1 from a wrecked Camaro (in 1999) and by the time I get that thing running in my 64 Impala it will be obsolete!

Yes, I finally managed to get the QSCI running on the transmit side, using interrupts. I just used the bottom half empty interrupt, it seems to be working very good. There are errors in the Freescale documentation, and omissions that make it very hard to figure out how to use it, but time and determination won. We are now thinking we need to go interrupt driven on the receive side too, but have not implemented that yet.

regards,

dave

-------------- Original message -------------- 
From: "Paul Helmuth" <PaulHelmuth at SprintMail.com> 

Jeff, Dave, et.al,

Guys - it's been a long time since I have checked in with the group. 

Unfortunately some major remodeling has been sucking up all of my spare time since sometime in October. Perhaps even more unfortunate, I'm still not done. On the bright side, only the master bathroom is left - so I will start sneaking some time in on the ECU development.

I have actually done a little work recently on a related sub-project. That is, development of a Windows Mobile application for tuning. I'm new to development in Windows Mobile, so it's going to take some time before I have it as functional as my standard Windows app, but I have got some of the basic serial communication stuff working. Which is what prompts me to check in and see what the current status is on interrupt driven serial I/O from the MPC555.

I read Dave's last post and that sounds like there are mixed results.

Hopefully I can get back to working on the serial i/o on the ECU side within the next several weeks.

Hope all had safe and happy holidays,

-

_______________________________________________
Efi332 mailing list
Efi332 at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/efi332

_______________________________________________
Efi332 mailing list
Efi332 at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/efi332
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20060205/40fcfee4/attachment.html 