From sailors3 at comcast.net  Wed Dec  7 07:21:15 2005
From: sailors3 at comcast.net (David Eicher)
Date: Wed, 7 Dec 2005 05:21:15 -0800
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
Message-ID: <mailman.51.1311919743.4788.efi332@diy-efi.org>

Hello,

Anyone have any experience with the subject matter? I've followed the
examples in the demo code in the quickstart package, the top half and bottom
half interrupts/flags just don't seem to work they way they suggest. The
users manual for MPC555 doesn't give a lot of detail, but I have not
succeeded in transmitting a string of bytes using interrupts yet. Using a
polling method I was able to get transmit working using the transmission
queue.

Thanks for any help you might be able to offer,

Dave




From jmhonnold4862 at yahoo.com  Wed Dec  7 15:31:18 2005
From: jmhonnold4862 at yahoo.com (John Honnold)
Date: Wed, 7 Dec 2005 13:31:18 -0800 (PST)
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
Message-ID: <20051207213118.11770.qmail@web34611.mail.mud.yahoo.com>

David:

   What seems to be the problem?  I work for Freescale
with the MCUs, so I may be able to help.  Let me know
some specifics.

Regards,

John Honnold

--- David Eicher <sailors3 at comcast.net> wrote:

> Hello,
> 
> Anyone have any experience with the subject matter?
> I've followed the
> examples in the demo code in the quickstart package,
> the top half and bottom
> half interrupts/flags just don't seem to work they
> way they suggest. The
> users manual for MPC555 doesn't give a lot of
> detail, but I have not
> succeeded in transmitting a string of bytes using
> interrupts yet. Using a
> polling method I was able to get transmit working
> using the transmission
> queue.
> 
> Thanks for any help you might be able to offer,
> 
> Dave
> 
> 
> _______________________________________________
> Efi332 mailing list
> Efi332 at diy-efi.org
> http://lists.diy-efi.org/mailman/listinfo/efi332
> 



From sailors3 at comcast.net  Wed Dec  7 23:25:09 2005
From: sailors3 at comcast.net (David Eicher)
Date: Wed, 7 Dec 2005 21:25:09 -0800
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
In-Reply-To: <20051207213118.11770.qmail@web34611.mail.mud.yahoo.com>
Message-ID: <mailman.52.1311919743.4788.efi332@diy-efi.org>

Hi John,

Thanks for your response. Yep, I'm trying to get the QSCI to work on the
MPC555 for transmit. I've just got a block of data I need to transmit.

I've implemented the code per the demo code in the quickstart package, it
just flat does not work for me. I've tried both use the two interrupts (QBHE
and QTHE), and tried just using the QBHE interrupt alone (filling queue with
16 bytes each time), and had no success for many hours.

Just earlier tonight I finally managed to get one approach to the point it
appears it is working (more testing required yet though). I'm using just the
QBHE interrupt and flag, filling the queue with 16 bytes each time. The demo
code does not include a "set QTE and TE" in the ISR after the queue is
loaded, but it doesn't seem to transmit without it. There is nothing I've
found in the users manual for MPC555 that indicates that this is required,
but I've had to keep turning the queue on over and over again to keep it
transmitting. 

Is this correct? Or am I just bandaiding some error in my code with the
setting of QTE and TE?

I"ll include the code I've found that works, I'd appreciate your comments on
it:

Thanks much,

Dave

--------------------------------------------------------- start transmit
-----------------------------------------------------------------

 

            for (i=0;i<16;i++) scratch[i] = 'a';

            

            ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP, SCI_ENABLE); 

            ioctl(QSMCM_QSCI1, QSCI_WRITE_QUEUE_TX_SIZE, 16);

            

            /* read SR with TC set */

            while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS, SCI_TX_COMPLETE))) {;}


            

 

              /* fill the whole buffer */  

              write(QSMCM_QSCI1, QUEUE_TOP_HALF, scratch, 16);

 

              /* Clear top half and bottom half flags QTHE/QBHE */

              ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_TOP_HALF);

              ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_BOT_HALF);

            

              /* Set queued enable flag in control register QTE */


              ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_ENABLE);

              /* Set QSCI transmit enable flag in control register TE */

              ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_ENABLE);

 

 

--------------------------------------------------------- ISR
----------------------------------------------------------------------------
---

 

  if (ioctl(QSMCM_QSCI1, QSCI_GET_QUEUE_FLAGS, QSCI_TX_BOT_HALF))

  {

      ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP, SCI_ENABLE); 
      ioctl(QSMCM_QSCI1, QSCI_WRITE_QUEUE_TX_SIZE, 16);

       /* read SR with TC set */
      while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS, SCI_TX_COMPLETE))) {;}  

      for (i=0;i<14;i++) scratch[i] = 'c';
      scratch[14] = (u_char)13;
      scratch[15] = (u_char)10;
      write(QSMCM_QSCI1, QUEUE_TOP_HALF, scratch, 16);

      ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_TOP_HALF);
      ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_BOT_HALF);

      if (data[0]< 6)  /* stop after 5 interrupts */
      {
         ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_ENABLE);
         ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_ENABLE);
      }
      else
      {
         ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_DISABLE);
         ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_DISABLE);
      }
   }

 


-----Original Message-----
From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of John Honnold
Sent: Wednesday, December 07, 2005 1:31 PM
To: efi332 at diy-efi.org
Subject: Re: [Efi332] Queued SCI transmit with interrupts on MPC555

David:

   What seems to be the problem?  I work for Freescale
with the MCUs, so I may be able to help.  Let me know
some specifics.

Regards,

John Honnold

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20051207/527e2d87/attachment.html 

From sailors3 at comcast.net  Thu Dec  8 08:52:57 2005
From: sailors3 at comcast.net (David Eicher)
Date: Thu, 8 Dec 2005 06:52:57 -0800
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
Message-ID: <mailman.53.1311919743.4788.efi332@diy-efi.org>

Hi John,

 

This morning I got up, fired up the machine, and ran this again. Now it does
not work..., it ran several times last night but after being powered down
all night, it does not. I must have had the hardware in some state that
allowed it to work, which I can't duplicate this morning. So, I'm still
trying to figure out a combination of "start transmit" code and ISR that
will keep the queue transmitting reliably. Does you or anyone have an
suggestions about what is wrong/missing from this code?

 

Thanks,

 

Dave

 

 

 

  _____  

From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of David Eicher
Sent: Wednesday, December 07, 2005 9:25 PM
To: efi332 at diy-efi.org
Subject: RE: [Efi332] Queued SCI transmit with interrupts on MPC555

 

Hi John,

Thanks for your response. Yep, I'm trying to get the QSCI to work on the
MPC555 for transmit. I've just got a block of data I need to transmit.

I've implemented the code per the demo code in the quickstart package, it
just flat does not work for me. I've tried both use the two interrupts (QBHE
and QTHE), and tried just using the QBHE interrupt alone (filling queue with
16 bytes each time), and had no success for many hours.

Just earlier tonight I finally managed to get one approach to the point it
appears it is working (more testing required yet though). I'm using just the
QBHE interrupt and flag, filling the queue with 16 bytes each time. The demo
code does not include a "set QTE and TE" in the ISR after the queue is
loaded, but it doesn't seem to transmit without it. There is nothing I've
found in the users manual for MPC555 that indicates that this is required,
but I've had to keep turning the queue on over and over again to keep it
transmitting. 

Is this correct? Or am I just bandaiding some error in my code with the
setting of QTE and TE?

I"ll include the code I've found that works, I'd appreciate your comments on
it:

Thanks much,

Dave

--------------------------------------------------------- start transmit
-----------------------------------------------------------------

 

            for (i=0;i<16;i++) scratch[i] = 'a';

            

            ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP, SCI_ENABLE); 

            ioctl(QSMCM_QSCI1, QSCI_WRITE_QUEUE_TX_SIZE, 16);

            

            /* read SR with TC set */

            while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS, SCI_TX_COMPLETE))) {;}


            

 

              /* fill the whole buffer */  

              write(QSMCM_QSCI1, QUEUE_TOP_HALF, scratch, 16);

 

              /* Clear top half and bottom half flags QTHE/QBHE */

              ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_TOP_HALF);

              ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_BOT_HALF);

            

              /* Set queued enable flag in control register QTE */


              ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_ENABLE);

              /* Set QSCI transmit enable flag in control register TE */

              ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_ENABLE);

 

 

--------------------------------------------------------- ISR
----------------------------------------------------------------------------
---

 

  if (ioctl(QSMCM_QSCI1, QSCI_GET_QUEUE_FLAGS, QSCI_TX_BOT_HALF))

  {

      ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP, SCI_ENABLE); 

      ioctl(QSMCM_QSCI1, QSCI_WRITE_QUEUE_TX_SIZE, 16);

       /* read SR with TC set */

      while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS, SCI_TX_COMPLETE))) {;}  

      for (i=0;i<14;i++) scratch[i] = 'c';

      scratch[14] = (u_char)13;

      scratch[15] = (u_char)10;

      write(QSMCM_QSCI1, QUEUE_TOP_HALF, scratch, 16);

      ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_TOP_HALF);

      ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_BOT_HALF);

      if (data[0]< 6)  /* stop after 5 interrupts */

      {

         ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_ENABLE);

         ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_ENABLE);

      }

      else

      {

         ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_DISABLE);

         ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_DISABLE);

      }

   }

 

 

-----Original Message-----
From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of John Honnold
Sent: Wednesday, December 07, 2005 1:31 PM
To: efi332 at diy-efi.org
Subject: Re: [Efi332] Queued SCI transmit with interrupts on MPC555

David:

   What seems to be the problem?  I work for Freescale

with the MCUs, so I may be able to help.  Let me know

some specifics.

Regards,

John Honnold

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20051208/4accfb45/attachment.html 

From sailors3 at comcast.net  Thu Dec  8 09:11:22 2005
From: sailors3 at comcast.net (David Eicher)
Date: Thu, 8 Dec 2005 07:11:22 -0800
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
Message-ID: <mailman.54.1311919743.4788.efi332@diy-efi.org>

Hmmm, okay, it works if I take the test  out that checks to see if I've
gotten 5 interrupts       if (data[0]< 6)  /* stop after 5 interrupts */

With that removed and just setting QTE and TE it transmits reliably and
continuously. I'm beginning to think my intermittent behaviour could be
related to not saving context and restoring context. The CW pragma interrupt
is suppose to get that done for me. I don't know how to check and see if it
is working. Does anyone know how to make CW save intermediate files so I can
see the assembly source it is generating?

 

Thanks,

 

Dave

 

  _____  

From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of David Eicher
Sent: Thursday, December 08, 2005 6:53 AM
To: efi332 at diy-efi.org
Subject: RE: [Efi332] Queued SCI transmit with interrupts on MPC555

 

Hi John,

 

This morning I got up, fired up the machine, and ran this again. Now it does
not work..., it ran several times last night but after being powered down
all night, it does not. I must have had the hardware in some state that
allowed it to work, which I can't duplicate this morning. So, I'm still
trying to figure out a combination of "start transmit" code and ISR that
will keep the queue transmitting reliably. Does you or anyone have an
suggestions about what is wrong/missing from this code?

 

Thanks,

 

Dave

 

 

 

  _____  

From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of David Eicher
Sent: Wednesday, December 07, 2005 9:25 PM
To: efi332 at diy-efi.org
Subject: RE: [Efi332] Queued SCI transmit with interrupts on MPC555

 

Hi John,

Thanks for your response. Yep, I'm trying to get the QSCI to work on the
MPC555 for transmit. I've just got a block of data I need to transmit.

I've implemented the code per the demo code in the quickstart package, it
just flat does not work for me. I've tried both use the two interrupts (QBHE
and QTHE), and tried just using the QBHE interrupt alone (filling queue with
16 bytes each time), and had no success for many hours.

Just earlier tonight I finally managed to get one approach to the point it
appears it is working (more testing required yet though). I'm using just the
QBHE interrupt and flag, filling the queue with 16 bytes each time. The demo
code does not include a "set QTE and TE" in the ISR after the queue is
loaded, but it doesn't seem to transmit without it. There is nothing I've
found in the users manual for MPC555 that indicates that this is required,
but I've had to keep turning the queue on over and over again to keep it
transmitting. 

Is this correct? Or am I just bandaiding some error in my code with the
setting of QTE and TE?

I"ll include the code I've found that works, I'd appreciate your comments on
it:

Thanks much,

Dave

--------------------------------------------------------- start transmit
-----------------------------------------------------------------

 

            for (i=0;i<16;i++) scratch[i] = 'a';

            

            ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP, SCI_ENABLE); 

            ioctl(QSMCM_QSCI1, QSCI_WRITE_QUEUE_TX_SIZE, 16);

            

            /* read SR with TC set */

            while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS, SCI_TX_COMPLETE))) {;}


            

 

              /* fill the whole buffer */  

              write(QSMCM_QSCI1, QUEUE_TOP_HALF, scratch, 16);

 

              /* Clear top half and bottom half flags QTHE/QBHE */

              ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_TOP_HALF);

              ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_BOT_HALF);

            

              /* Set queued enable flag in control register QTE */


              ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_ENABLE);

              /* Set QSCI transmit enable flag in control register TE */

              ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_ENABLE);

 

 

--------------------------------------------------------- ISR
----------------------------------------------------------------------------
---

 

  if (ioctl(QSMCM_QSCI1, QSCI_GET_QUEUE_FLAGS, QSCI_TX_BOT_HALF))

  {

      ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP, SCI_ENABLE); 

      ioctl(QSMCM_QSCI1, QSCI_WRITE_QUEUE_TX_SIZE, 16);

       /* read SR with TC set */

      while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS, SCI_TX_COMPLETE))) {;}  

      for (i=0;i<14;i++) scratch[i] = 'c';

      scratch[14] = (u_char)13;

      scratch[15] = (u_char)10;

      write(QSMCM_QSCI1, QUEUE_TOP_HALF, scratch, 16);

      ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_TOP_HALF);

      ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_BOT_HALF);

      if (data[0]< 6)  /* stop after 5 interrupts */

      {

         ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_ENABLE);

         ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_ENABLE);

      }

      else

      {

         ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX, SCI_DISABLE);

         ioctl(QSMCM_SCI1, SCI_TRANSMITTER, SCI_DISABLE);

      }

   }

 

 

-----Original Message-----
From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of John Honnold
Sent: Wednesday, December 07, 2005 1:31 PM
To: efi332 at diy-efi.org
Subject: Re: [Efi332] Queued SCI transmit with interrupts on MPC555

David:

   What seems to be the problem?  I work for Freescale

with the MCUs, so I may be able to help.  Let me know

some specifics.

Regards,

John Honnold

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20051208/3b5347b2/attachment.html 

From tmechanic at yahoo.com  Thu Dec  8 09:13:02 2005
From: tmechanic at yahoo.com (Brian Toberman)
Date: Thu, 8 Dec 2005 07:13:02 -0800 (PST)
Subject: [Efi332] board purchase
Message-ID: <20051208151302.35623.qmail@web35612.mail.mud.yahoo.com>

Who do I contact to purchase a 4 layer board, or will
I need to make my own brd.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From sailors3 at comcast.net  Thu Dec  8 09:31:16 2005
From: sailors3 at comcast.net (David Eicher)
Date: Thu, 8 Dec 2005 07:31:16 -0800
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
In-Reply-To: <20051207213118.11770.qmail@web34611.mail.mud.yahoo.com>
Message-ID: <mailman.55.1311919743.4788.efi332@diy-efi.org>

Hi John,

Could you email me at my office email: deeicher at rockwellcollins.com please?

I've had a request into Freescale for about 72 hours now and no response.
Maybe you could spare a few minutes to talk if I call you? I'd love to get a
little of your insight on how QSCI works for transmit.

Thanks,

Dave Eicher


-----Original Message-----
From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of John Honnold
Sent: Wednesday, December 07, 2005 1:31 PM
To: efi332 at diy-efi.org
Subject: Re: [Efi332] Queued SCI transmit with interrupts on MPC555

David:

   What seems to be the problem?  I work for Freescale
with the MCUs, so I may be able to help.  Let me know
some specifics.

Regards,

John Honnold

--- David Eicher <sailors3 at comcast.net> wrote:

> Hello,
> 
> Anyone have any experience with the subject matter?
> I've followed the
> examples in the demo code in the quickstart package,
> the top half and bottom
> half interrupts/flags just don't seem to work they
> way they suggest. The
> users manual for MPC555 doesn't give a lot of
> detail, but I have not
> succeeded in transmitting a string of bytes using
> interrupts yet. Using a
> polling method I was able to get transmit working
> using the transmission
> queue.
> 
> Thanks for any help you might be able to offer,
> 
> Dave
> 
> 
> _______________________________________________
> 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



From jmhonnold4862 at yahoo.com  Thu Dec  8 13:27:15 2005
From: jmhonnold4862 at yahoo.com (John Honnold)
Date: Thu, 8 Dec 2005 11:27:15 -0800 (PST)
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
Message-ID: <20051208192716.46334.qmail@web34610.mail.mud.yahoo.com>

David:

   I am swamped today.  I will call you tomorrow.

Regards,

John Honnold

--- David Eicher <sailors3 at comcast.net> wrote:

> Hi John,
> 
>  
> 
> This morning I got up, fired up the machine, and ran
> this again. Now it does
> not work..., it ran several times last night but
> after being powered down
> all night, it does not. I must have had the hardware
> in some state that
> allowed it to work, which I can't duplicate this
> morning. So, I'm still
> trying to figure out a combination of "start
> transmit" code and ISR that
> will keep the queue transmitting reliably. Does you
> or anyone have an
> suggestions about what is wrong/missing from this
> code?
> 
>  
> 
> Thanks,
> 
>  
> 
> Dave
> 
>  
> 
>  
> 
>  
> 
>   _____  
> 
> From: efi332-bounces at diy-efi.org
> [mailto:efi332-bounces at diy-efi.org] On
> Behalf Of David Eicher
> Sent: Wednesday, December 07, 2005 9:25 PM
> To: efi332 at diy-efi.org
> Subject: RE: [Efi332] Queued SCI transmit with
> interrupts on MPC555
> 
>  
> 
> Hi John,
> 
> Thanks for your response. Yep, I'm trying to get the
> QSCI to work on the
> MPC555 for transmit. I've just got a block of data I
> need to transmit.
> 
> I've implemented the code per the demo code in the
> quickstart package, it
> just flat does not work for me. I've tried both use
> the two interrupts (QBHE
> and QTHE), and tried just using the QBHE interrupt
> alone (filling queue with
> 16 bytes each time), and had no success for many
> hours.
> 
> Just earlier tonight I finally managed to get one
> approach to the point it
> appears it is working (more testing required yet
> though). I'm using just the
> QBHE interrupt and flag, filling the queue with 16
> bytes each time. The demo
> code does not include a "set QTE and TE" in the ISR
> after the queue is
> loaded, but it doesn't seem to transmit without it.
> There is nothing I've
> found in the users manual for MPC555 that indicates
> that this is required,
> but I've had to keep turning the queue on over and
> over again to keep it
> transmitting. 
> 
> Is this correct? Or am I just bandaiding some error
> in my code with the
> setting of QTE and TE?
> 
> I"ll include the code I've found that works, I'd
> appreciate your comments on
> it:
> 
> Thanks much,
> 
> Dave
> 
>
---------------------------------------------------------
> start transmit
>
-----------------------------------------------------------------
> 
>  
> 
>             for (i=0;i<16;i++) scratch[i] = 'a';
> 
>             
> 
>             ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP,
> SCI_ENABLE); 
> 
>             ioctl(QSMCM_QSCI1,
> QSCI_WRITE_QUEUE_TX_SIZE, 16);
> 
>             
> 
>             /* read SR with TC set */
> 
>             while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS,
> SCI_TX_COMPLETE))) {;}
> 
> 
>             
> 
>  
> 
>               /* fill the whole buffer */  
> 
>               write(QSMCM_QSCI1, QUEUE_TOP_HALF,
> scratch, 16);
> 
>  
> 
>               /* Clear top half and bottom half
> flags QTHE/QBHE */
> 
>               ioctl(QSMCM_QSCI1,
> QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_TOP_HALF);
> 
>               ioctl(QSMCM_QSCI1,
> QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_BOT_HALF);
> 
>             
> 
>               /* Set queued enable flag in control
> register QTE */
> 
> 
>               ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX,
> SCI_ENABLE);
> 
>               /* Set QSCI transmit enable flag in
> control register TE */
> 
>               ioctl(QSMCM_SCI1, SCI_TRANSMITTER,
> SCI_ENABLE);
> 
>  
> 
>  
> 
>
---------------------------------------------------------
> ISR
>
----------------------------------------------------------------------------
> ---
> 
>  
> 
>   if (ioctl(QSMCM_QSCI1, QSCI_GET_QUEUE_FLAGS,
> QSCI_TX_BOT_HALF))
> 
>   {
> 
>       ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP,
> SCI_ENABLE); 
> 
>       ioctl(QSMCM_QSCI1, QSCI_WRITE_QUEUE_TX_SIZE,
> 16);
> 
>        /* read SR with TC set */
> 
>       while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS,
> SCI_TX_COMPLETE))) {;}  
> 
>       for (i=0;i<14;i++) scratch[i] = 'c';
> 
>       scratch[14] = (u_char)13;
> 
>       scratch[15] = (u_char)10;
> 
>       write(QSMCM_QSCI1, QUEUE_TOP_HALF, scratch,
> 16);
> 
>       ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS,
> QSCI_TX_TOP_HALF);
> 
>       ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS,
> QSCI_TX_BOT_HALF);
> 
>       if (data[0]< 6)  /* stop after 5 interrupts */
> 
>       {
> 
>          ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX,
> SCI_ENABLE);
> 
>          ioctl(QSMCM_SCI1, SCI_TRANSMITTER,
> SCI_ENABLE);
> 
>       }
> 
>       else
> 
>       {
> 
>          ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX,
> SCI_DISABLE);
> 
>          ioctl(QSMCM_SCI1, SCI_TRANSMITTER,
> SCI_DISABLE);
> 
>       }
> 
>    }
> 
>  
> 
>  
> 
> -----Original Message-----
> From: efi332-bounces at diy-efi.org
> [mailto:efi332-bounces at diy-efi.org] On
> Behalf Of John Honnold
> Sent: Wednesday, December 07, 2005 1:31 PM
> To: efi332 at diy-efi.org
> Subject: Re: [Efi332] Queued SCI transmit with
> interrupts on MPC555
> 
> David:
> 
>    What seems to be the problem?  I work for
> Freescale
> 
> with the MCUs, so I may be able to help.  Let me
> know
> 
> some specifics.
> 
> Regards,
> 
> John Honnold
> 
> > _______________________________________________
> Efi332 mailing list
> Efi332 at diy-efi.org
> http://lists.diy-efi.org/mailman/listinfo/efi332
> 



From sailors3 at comcast.net  Thu Dec  8 19:22:39 2005
From: sailors3 at comcast.net (David Eicher)
Date: Thu, 8 Dec 2005 17:22:39 -0800
Subject: [Efi332] board purchase
In-Reply-To: <20051208151302.35623.qmail@web35612.mail.mud.yahoo.com>
Message-ID: <mailman.56.1311919743.4788.efi332@diy-efi.org>

Hi Brian,

I don't know what to tell you. I sold my board about a year ago. It's being
used in a race car. I don't know of any for sale. Sorry I can't help.

Regards,

Dave


-----Original Message-----
From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of Brian Toberman
Sent: Thursday, December 08, 2005 7:13 AM
To: efi332 at diy-efi.org
Subject: [Efi332] board purchase

Who do I contact to purchase a 4 layer board, or will
I need to make my own brd.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
Efi332 mailing list
Efi332 at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/efi332



From BowTieVette at aol.com  Thu Dec  8 19:37:39 2005
From: BowTieVette at aol.com (BowTieVette at aol.com)
Date: Thu, 8 Dec 2005 20:37:39 EST
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
Message-ID: <da.32bbd6e3.30ca39e3@aol.com>

 
In a message dated 12/8/2005 9:53:59 A.M. Eastern Standard Time,  
sailors3 at comcast.net writes:

Hi  John, 
This morning I got  up, fired up the machine, and ran this again. Now it does 
not work?.., it ran  several times last night but after being powered down 
all night, it does not.  I must have had the hardware in some state that allowed 
it to work, which I  can?t duplicate this morning. So, I?m still trying to 
figure out a combination  of ?start transmit? code and ISR that will keep the 
queue transmitting  reliably. Does you or anyone have an suggestions about 
what is wrong/missing  from this code? 
Thanks, 
Dave


Dave,
I think something that was mentioned on the mpc500 list may be at the root  
of the variability you are seeing. Could a SCI error be hanging the 
transmission  on you? You might check all the SCI flags in your ISR to be sure an error  
did not occur there as well. Since the QSCI is really appears to be a macro on 
 top of the SCI, I think you are still subject to having to handle all the 
SCI  errors. There could well be something in your QSCI implementation that  
makes SCI more prone to errors. If this turns out to be the(an) issue  you may be 
able to take the handling of these right from my 332  code SCI interrupt 
handler.
jc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20051208/ee80d784/attachment.html 

From BowTieVette at aol.com  Thu Dec  8 19:40:07 2005
From: BowTieVette at aol.com (BowTieVette at aol.com)
Date: Thu, 8 Dec 2005 20:40:07 EST
Subject: [Efi332] board purchase
Message-ID: <258.3270e60.30ca3a77@aol.com>

 
In a message dated 12/8/2005 10:15:20 A.M. Eastern Standard Time,  
tmechanic at yahoo.com writes:

Who do I  contact to purchase a 4 layer board, or will
I need to make my own  brd.


Hey tmech,
These days 4 layer boards are only available second hand from list  members 
since there was only a limited quantity made during a substantial group  buy 
years ago. Since not many were completed, there should be plenty gathering  
dust. My advice is to keep asking, one will surface.
jc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20051208/c14af03a/attachment.html 

From sailors3 at comcast.net  Thu Dec  8 20:04:51 2005
From: sailors3 at comcast.net (David Eicher)
Date: Thu, 8 Dec 2005 18:04:51 -0800
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
In-Reply-To: <da.32bbd6e3.30ca39e3@aol.com>
Message-ID: <mailman.57.1311919743.4788.efi332@diy-efi.org>

Good idea, thanks Jeff, I'll check on it.

 

Regards,

 

Dave

 

 

  _____  

From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of BowTieVette at aol.com
Sent: Thursday, December 08, 2005 5:38 PM
To: efi332 at diy-efi.org
Subject: Re: [Efi332] Queued SCI transmit with interrupts on MPC555

 

In a message dated 12/8/2005 9:53:59 A.M. Eastern Standard Time,
sailors3 at comcast.net writes:

Hi John,

 

This morning I got up, fired up the machine, and ran this again. Now it does
not work..., it ran several times last night but after being powered down
all night, it does not. I must have had the hardware in some state that
allowed it to work, which I can't duplicate this morning. So, I'm still
trying to figure out a combination of "start transmit" code and ISR that
will keep the queue transmitting reliably. Does you or anyone have an
suggestions about what is wrong/missing from this code?

 

Thanks,

 

Dave

Dave,

I think something that was mentioned on the mpc500 list may be at the root
of the variability you are seeing. Could a SCI error be hanging the
transmission on you? You might check all the SCI flags in your ISR to be
sure an error did not occur there as well. Since the QSCI is really appears
to be a macro on top of the SCI, I think you are still subject to having to
handle all the SCI errors. There could well be something in your QSCI
implementation that makes SCI more prone to errors. If this turns out to be
the(an) issue you may be able to take the handling of these right from my
332 code SCI interrupt handler.

jc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20051208/6269f6b4/attachment.html 

From efi332 at sbcglobal.net  Thu Dec  8 20:44:01 2005
From: efi332 at sbcglobal.net (Robert)
Date: Thu, 08 Dec 2005 18:44:01 -0800
Subject: [Efi332] board purchase
In-Reply-To: <20051208151302.35623.qmail@web35612.mail.mud.yahoo.com>
References: <20051208151302.35623.qmail@web35612.mail.mud.yahoo.com>
Message-ID: <4398EF71.4040205@sbcglobal.net>

Brian Toberman wrote:

>Who do I contact to purchase a 4 layer board, or will
>I need to make my own brd.
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam?  Yahoo! Mail has the best spam protection around 
>http://mail.yahoo.com 
>_______________________________________________
>Efi332 mailing list
>Efi332 at diy-efi.org
>http://lists.diy-efi.org/mailman/listinfo/efi332
>
>  
>
As JC stated, there are 4 layer boards collecting dust.  I know because 
a have a couple.  The first one was part of the original group buy.  It 
was supposed to be assembled by Charles, but he ran into problems and 
never completed the assembly.  It is missing 8 of the ICs.  U1 & U2 
(MC145051), U3 (MC33298P), U6 (UDN2916B) U7 & U8 (LM1815N) U9 & 10 
(74HCT125N).  It is also missing the dip switch, the jumper posts and 
some caps and resistors.  The other board, which I bought through and 
online auction, is complete but has a piece of masking tape indicating 
"NO BDM MODE."  I bought this later board as a spare and for the parts.  
I do not have the ability to test or troubleshoot either board.  
However, the incomplete board purportedly passed the CPU test when it 
was being assembled by Charles.  At least that is what the tag says.  If 
you are interested let me know.

Robert



From tmechanic at yahoo.com  Thu Dec  8 21:58:25 2005
From: tmechanic at yahoo.com (Brian Toberman)
Date: Thu, 8 Dec 2005 19:58:25 -0800 (PST)
Subject: [Efi332] board purchase
Message-ID: <20051209035825.60174.qmail@web35610.mail.mud.yahoo.com>

Thanks guys, I'll keep asking.
Maybe I'll try my hand at etching a 2 layer brd in the
mean time.

Brian T.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


From wmcdonal at optushome.com.au  Thu Dec  8 22:12:18 2005
From: wmcdonal at optushome.com.au (Wayne Macdonald)
Date: Fri, 9 Dec 2005 15:12:18 +1100
Subject: [Efi332] board purchase
References: <200512090123.jB91NV1P005820@mail13.syd.optusnet.com.au>
Message-ID: <115101c5fc76$bf24af00$6401a8c0@wayne2k>

I have a complete 4-layer board and parts kit that has never been built, let
me know if you are interested.

Wayne

----- Original Message -----
From: "David Eicher" <sailors3 at comcast.net>
To: <efi332 at diy-efi.org>
Sent: Friday, December 09, 2005 12:22 PM
Subject: RE: [Efi332] board purchase


> Hi Brian,
>
> I don't know what to tell you. I sold my board about a year ago. It's
being
> used in a race car. I don't know of any for sale. Sorry I can't help.
>
> Regards,
>
> Dave
>
>
> -----Original Message-----
> From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
> Behalf Of Brian Toberman
> Sent: Thursday, December 08, 2005 7:13 AM
> To: efi332 at diy-efi.org
> Subject: [Efi332] board purchase
>
> Who do I contact to purchase a 4 layer board, or will
> I need to make my own brd.
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> 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



From sailors3 at comcast.net  Fri Dec  9 07:58:16 2005
From: sailors3 at comcast.net (David Eicher)
Date: Fri, 9 Dec 2005 05:58:16 -0800
Subject: [Efi332] Queued SCI transmit with interrupts on MPC555
In-Reply-To: <20051208192716.46334.qmail@web34610.mail.mud.yahoo.com>
Message-ID: <mailman.58.1311919743.4788.efi332@diy-efi.org>

Hi John,

Okay, I'll watch for an email from you today (Friday 12/9), then we can
hookup by phone.

Appreciate the help,

Dave


-----Original Message-----
From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of John Honnold
Sent: Thursday, December 08, 2005 11:27 AM
To: efi332 at diy-efi.org
Subject: RE: [Efi332] Queued SCI transmit with interrupts on MPC555

David:

   I am swamped today.  I will call you tomorrow.

Regards,

John Honnold

--- David Eicher <sailors3 at comcast.net> wrote:

> Hi John,
> 
>  
> 
> This morning I got up, fired up the machine, and ran
> this again. Now it does
> not work..., it ran several times last night but
> after being powered down
> all night, it does not. I must have had the hardware
> in some state that
> allowed it to work, which I can't duplicate this
> morning. So, I'm still
> trying to figure out a combination of "start
> transmit" code and ISR that
> will keep the queue transmitting reliably. Does you
> or anyone have an
> suggestions about what is wrong/missing from this
> code?
> 
>  
> 
> Thanks,
> 
>  
> 
> Dave
> 
>  
> 
>  
> 
>  
> 
>   _____  
> 
> From: efi332-bounces at diy-efi.org
> [mailto:efi332-bounces at diy-efi.org] On
> Behalf Of David Eicher
> Sent: Wednesday, December 07, 2005 9:25 PM
> To: efi332 at diy-efi.org
> Subject: RE: [Efi332] Queued SCI transmit with
> interrupts on MPC555
> 
>  
> 
> Hi John,
> 
> Thanks for your response. Yep, I'm trying to get the
> QSCI to work on the
> MPC555 for transmit. I've just got a block of data I
> need to transmit.
> 
> I've implemented the code per the demo code in the
> quickstart package, it
> just flat does not work for me. I've tried both use
> the two interrupts (QBHE
> and QTHE), and tried just using the QBHE interrupt
> alone (filling queue with
> 16 bytes each time), and had no success for many
> hours.
> 
> Just earlier tonight I finally managed to get one
> approach to the point it
> appears it is working (more testing required yet
> though). I'm using just the
> QBHE interrupt and flag, filling the queue with 16
> bytes each time. The demo
> code does not include a "set QTE and TE" in the ISR
> after the queue is
> loaded, but it doesn't seem to transmit without it.
> There is nothing I've
> found in the users manual for MPC555 that indicates
> that this is required,
> but I've had to keep turning the queue on over and
> over again to keep it
> transmitting. 
> 
> Is this correct? Or am I just bandaiding some error
> in my code with the
> setting of QTE and TE?
> 
> I"ll include the code I've found that works, I'd
> appreciate your comments on
> it:
> 
> Thanks much,
> 
> Dave
> 
>
---------------------------------------------------------
> start transmit
>
-----------------------------------------------------------------
> 
>  
> 
>             for (i=0;i<16;i++) scratch[i] = 'a';
> 
>             
> 
>             ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP,
> SCI_ENABLE); 
> 
>             ioctl(QSMCM_QSCI1,
> QSCI_WRITE_QUEUE_TX_SIZE, 16);
> 
>             
> 
>             /* read SR with TC set */
> 
>             while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS,
> SCI_TX_COMPLETE))) {;}
> 
> 
>             
> 
>  
> 
>               /* fill the whole buffer */  
> 
>               write(QSMCM_QSCI1, QUEUE_TOP_HALF,
> scratch, 16);
> 
>  
> 
>               /* Clear top half and bottom half
> flags QTHE/QBHE */
> 
>               ioctl(QSMCM_QSCI1,
> QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_TOP_HALF);
> 
>               ioctl(QSMCM_QSCI1,
> QSCI_CLEAR_QUEUE_FLAGS, QSCI_TX_BOT_HALF);
> 
>             
> 
>               /* Set queued enable flag in control
> register QTE */
> 
> 
>               ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX,
> SCI_ENABLE);
> 
>               /* Set QSCI transmit enable flag in
> control register TE */
> 
>               ioctl(QSMCM_SCI1, SCI_TRANSMITTER,
> SCI_ENABLE);
> 
>  
> 
>  
> 
>
---------------------------------------------------------
> ISR
>
----------------------------------------------------------------------------
> ---
> 
>  
> 
>   if (ioctl(QSMCM_QSCI1, QSCI_GET_QUEUE_FLAGS,
> QSCI_TX_BOT_HALF))
> 
>   {
> 
>       ioctl(QSMCM_QSCI1, QSCI_ENABLE_TX_WRAP,
> SCI_ENABLE); 
> 
>       ioctl(QSMCM_QSCI1, QSCI_WRITE_QUEUE_TX_SIZE,
> 16);
> 
>        /* read SR with TC set */
> 
>       while(!(ioctl(QSMCM_SCI1, SCI_GET_FLAGS,
> SCI_TX_COMPLETE))) {;}  
> 
>       for (i=0;i<14;i++) scratch[i] = 'c';
> 
>       scratch[14] = (u_char)13;
> 
>       scratch[15] = (u_char)10;
> 
>       write(QSMCM_QSCI1, QUEUE_TOP_HALF, scratch,
> 16);
> 
>       ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS,
> QSCI_TX_TOP_HALF);
> 
>       ioctl(QSMCM_QSCI1, QSCI_CLEAR_QUEUE_FLAGS,
> QSCI_TX_BOT_HALF);
> 
>       if (data[0]< 6)  /* stop after 5 interrupts */
> 
>       {
> 
>          ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX,
> SCI_ENABLE);
> 
>          ioctl(QSMCM_SCI1, SCI_TRANSMITTER,
> SCI_ENABLE);
> 
>       }
> 
>       else
> 
>       {
> 
>          ioctl(QSMCM_QSCI1, QSCI_QUEUE_TX,
> SCI_DISABLE);
> 
>          ioctl(QSMCM_SCI1, SCI_TRANSMITTER,
> SCI_DISABLE);
> 
>       }
> 
>    }
> 
>  
> 
>  
> 
> -----Original Message-----
> From: efi332-bounces at diy-efi.org
> [mailto:efi332-bounces at diy-efi.org] On
> Behalf Of John Honnold
> Sent: Wednesday, December 07, 2005 1:31 PM
> To: efi332 at diy-efi.org
> Subject: Re: [Efi332] Queued SCI transmit with
> interrupts on MPC555
> 
> David:
> 
>    What seems to be the problem?  I work for
> Freescale
> 
> with the MCUs, so I may be able to help.  Let me
> know
> 
> some specifics.
> 
> Regards,
> 
> John Honnold
> 
> > _______________________________________________
> 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



From john.hoyenga at comcast.net  Sat Dec 31 08:50:29 2005
From: john.hoyenga at comcast.net (john.hoyenga at comcast.net)
Date: Sat, 31 Dec 2005 14:50:29 +0000
Subject: [Efi332] board purchase
Message-ID: <123120051450.9247.43B69AB5000C82530000241F22070215730E09020A970108D202080106@comcast.net>


Hello, sorry it took so long to get back to you, I forgot about this e-mail address. How much is the complete set with a 4 layer board? is the parts kit you have complete?

thanks
-John-
-------------- Original message -------------- 
From: "Wayne Macdonald" <wmcdonal at optushome.com.au> 

> I have a complete 4-layer board and parts kit that has never been built, let 
> me know if you are interested. 
> 
> Wayne 
> 
> ----- Original Message ----- 
> From: "David Eicher" 
> To: 
> Sent: Friday, December 09, 2005 12:22 PM 
> Subject: RE: [Efi332] board purchase 
> 
> 
> > Hi Brian, 
> > 
> > I don't know what to tell you. I sold my board about a year ago. It's 
> being 
> > used in a race car. I don't know of any for sale. Sorry I can't help. 
> > 
> > Regards, 
> > 
> > Dave 
> > 
> > 
> > -----Original Message----- 
> > From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On 
> > Behalf Of Brian Toberman 
> > Sent: Thursday, December 08, 2005 7:13 AM 
> > To: efi332 at diy-efi.org 
> > Subject: [Efi332] board purchase 
> > 
> > Who do I contact to purchase a 4 layer board, or will 
> > I need to make my own brd. 
> > 
> > __________________________________________________ 
> > Do You Yahoo!? 
> > Tired of spam? Yahoo! Mail has the best spam protection around 
> > http://mail.yahoo.com 
> > _______________________________________________ 
> > 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 
> 
> _______________________________________________ 
> 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/20051231/dfcb294a/attachment.html