Hi,
I am migrating a serial communications interface (Modbus) to a LPC2138
processor. The Modbus spec defines that an end of message has occurred
when a period equal to 3.5 characters has passed since the last
character has been received.
The LPC uart can generate an interrupt if the receive buffer has
characters in it and no character has been received for a period of 3.5
- 4.5 characters.
I would like to use this feature for detecting the end of a received
message. The problem I have is that if I service an interrupt due the
the buffer being filled, and it also happens that that last character in
the buffer was the last character for the received message, the receive
time-out interrupt will not occur, resulting in the end of message not
being detected.
Is there a solution, other than using a buffer length of 1 and using a
timer to measure the inter message gap?
Cheers,
Peter.
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
Uart receive timeout Interrupt?
Started by ●November 9, 2005
Reply by ●November 9, 20052005-11-09
--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
> Hi,
>
> I am migrating a serial communications interface (Modbus) to a
LPC2138
> processor. The Modbus spec defines that an end of message has
occurred
> when a period equal to 3.5 characters has passed since the last
> character has been received.
>
> The LPC uart can generate an interrupt if the receive buffer has
> characters in it and no character has been received for a period of
3.5
> - 4.5 characters.
>
> I would like to use this feature for detecting the end of a received
> message. The problem I have is that if I service an interrupt due
the
> the buffer being filled, and it also happens that that last
character in
> the buffer was the last character for the received message, the
receive
> time-out interrupt will not occur, resulting in the end of message
not
> being detected.
>
> Is there a solution, other than using a buffer length of 1 and using
a
> timer to measure the inter message gap?
>
> Cheers,
>
> Peter.
>
> --
> ------------------------------
> Web: www.homanndesigns.com
> email: homann@h...
> Phone: +61 421 601 665
> www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>
If you are interested in MODBUS slave for LPC213X email me
and I can send you some code fot it
Radim design@desi...
>
> Hi,
>
> I am migrating a serial communications interface (Modbus) to a
LPC2138
> processor. The Modbus spec defines that an end of message has
occurred
> when a period equal to 3.5 characters has passed since the last
> character has been received.
>
> The LPC uart can generate an interrupt if the receive buffer has
> characters in it and no character has been received for a period of
3.5
> - 4.5 characters.
>
> I would like to use this feature for detecting the end of a received
> message. The problem I have is that if I service an interrupt due
the
> the buffer being filled, and it also happens that that last
character in
> the buffer was the last character for the received message, the
receive
> time-out interrupt will not occur, resulting in the end of message
not
> being detected.
>
> Is there a solution, other than using a buffer length of 1 and using
a
> timer to measure the inter message gap?
>
> Cheers,
>
> Peter.
>
> --
> ------------------------------
> Web: www.homanndesigns.com
> email: homann@h...
> Phone: +61 421 601 665
> www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>
If you are interested in MODBUS slave for LPC213X email me
and I can send you some code fot it
Radim design@desi...
Reply by ●November 9, 20052005-11-09
Hi,
Thanks for the offer. I'd be interested in learning how to implement
Modbus on the LPC. Anything you can send will be a big help as I'm new
to the Arm processor.
Now my LPC2138 processor has locked up and not talking to the Philips
flash utility. Hopefully I can get it working again.
Cheers,
Peter.
radim100 wrote:
> --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
>>Hi,
>>
>>I am migrating a serial communications interface (Modbus) to a
>
> LPC2138
>
>>processor. The Modbus spec defines that an end of message has
>
> occurred
>
>>when a period equal to 3.5 characters has passed since the last
>>character has been received.
>>
>>The LPC uart can generate an interrupt if the receive buffer has
>>characters in it and no character has been received for a period of
>
> 3.5
>
>>- 4.5 characters.
>>
>>I would like to use this feature for detecting the end of a received
>>message. The problem I have is that if I service an interrupt due
>
> the
>
>>the buffer being filled, and it also happens that that last
>
> character in
>
>>the buffer was the last character for the received message, the
>
> receive
>
>>time-out interrupt will not occur, resulting in the end of message
>
> not
>
>>being detected.
>>
>>Is there a solution, other than using a buffer length of 1 and using
>
> a
>
>>timer to measure the inter message gap?
>>
>>Cheers,
>>
>>Peter.
>>
>>--
>>------------------------------
>>Web: www.homanndesigns.com
>>email: homann@h...
>>Phone: +61 421 601 665
>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>
>
> If you are interested in MODBUS slave for LPC213X email me
> and I can send you some code fot it
> Radim design@desi...
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
Thanks for the offer. I'd be interested in learning how to implement
Modbus on the LPC. Anything you can send will be a big help as I'm new
to the Arm processor.
Now my LPC2138 processor has locked up and not talking to the Philips
flash utility. Hopefully I can get it working again.
Cheers,
Peter.
radim100 wrote:
> --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
>>Hi,
>>
>>I am migrating a serial communications interface (Modbus) to a
>
> LPC2138
>
>>processor. The Modbus spec defines that an end of message has
>
> occurred
>
>>when a period equal to 3.5 characters has passed since the last
>>character has been received.
>>
>>The LPC uart can generate an interrupt if the receive buffer has
>>characters in it and no character has been received for a period of
>
> 3.5
>
>>- 4.5 characters.
>>
>>I would like to use this feature for detecting the end of a received
>>message. The problem I have is that if I service an interrupt due
>
> the
>
>>the buffer being filled, and it also happens that that last
>
> character in
>
>>the buffer was the last character for the received message, the
>
> receive
>
>>time-out interrupt will not occur, resulting in the end of message
>
> not
>
>>being detected.
>>
>>Is there a solution, other than using a buffer length of 1 and using
>
> a
>
>>timer to measure the inter message gap?
>>
>>Cheers,
>>
>>Peter.
>>
>>--
>>------------------------------
>>Web: www.homanndesigns.com
>>email: homann@h...
>>Phone: +61 421 601 665
>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>
>
> If you are interested in MODBUS slave for LPC213X email me
> and I can send you some code fot it
> Radim design@desi...
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
Reply by ●November 9, 20052005-11-09
Peter Homann wrote:
> Hi,
>
> I am migrating a serial communications interface (Modbus) to a LPC2138
> processor. The Modbus spec defines that an end of message has occurred
> when a period equal to 3.5 characters has passed since the last
> character has been received.
>
> The LPC uart can generate an interrupt if the receive buffer has
> characters in it and no character has been received for a period of 3.5
> - 4.5 characters.
>
> I would like to use this feature for detecting the end of a received
> message. The problem I have is that if I service an interrupt due the
> the buffer being filled, and it also happens that that last character in
> the buffer was the last character for the received message, the receive
> time-out interrupt will not occur, resulting in the end of message not
> being detected.
>
> Is there a solution, other than using a buffer length of 1 and using a
> timer to measure the inter message gap?
>
> Cheers,
>
> Peter.
>
Hello Peter,
this interrupt was not designed for your needs. It should prevent a
communication from being stalled if some characters are trapped in queue
which is not full.
Just an idea: every time you receive a character reset a timer. If a
timer interrupt occure prior a line idle interrupt, you have not
received any characters for a certain time. It's ugly but should solve
your problem.
Sten
--
/************************************************
Do you need a tiny and efficient real time
operating system (RTOS) with a preemtive
multitasking for LPC2000 or AT91SAM7?
http://nanortos.net-attack.de/
Or some open-source tools and code for LPC2000?
http://www.net-attack.de/
************************************************/
> Hi,
>
> I am migrating a serial communications interface (Modbus) to a LPC2138
> processor. The Modbus spec defines that an end of message has occurred
> when a period equal to 3.5 characters has passed since the last
> character has been received.
>
> The LPC uart can generate an interrupt if the receive buffer has
> characters in it and no character has been received for a period of 3.5
> - 4.5 characters.
>
> I would like to use this feature for detecting the end of a received
> message. The problem I have is that if I service an interrupt due the
> the buffer being filled, and it also happens that that last character in
> the buffer was the last character for the received message, the receive
> time-out interrupt will not occur, resulting in the end of message not
> being detected.
>
> Is there a solution, other than using a buffer length of 1 and using a
> timer to measure the inter message gap?
>
> Cheers,
>
> Peter.
>
Hello Peter,
this interrupt was not designed for your needs. It should prevent a
communication from being stalled if some characters are trapped in queue
which is not full.
Just an idea: every time you receive a character reset a timer. If a
timer interrupt occure prior a line idle interrupt, you have not
received any characters for a certain time. It's ugly but should solve
your problem.
Sten
--
/************************************************
Do you need a tiny and efficient real time
operating system (RTOS) with a preemtive
multitasking for LPC2000 or AT91SAM7?
http://nanortos.net-attack.de/
Or some open-source tools and code for LPC2000?
http://www.net-attack.de/
************************************************/
Reply by ●November 9, 20052005-11-09
Hi Sten,
Thanks for your reply. Yes, this is what I'm doing now with the PIC chip
and was expecting to have to do on the Arm. As I'm new to it, I wasn't
sure if there was a neater way to do it. I moving (Trying to) to the Arm
for more Grunt.
Cheers,
peter
Sten wrote:
> Peter Homann wrote:
>
>>Hi,
>>
>>I am migrating a serial communications interface (Modbus) to a LPC2138
>>processor. The Modbus spec defines that an end of message has occurred
>>when a period equal to 3.5 characters has passed since the last
>>character has been received.
>>
>>The LPC uart can generate an interrupt if the receive buffer has
>>characters in it and no character has been received for a period of 3.5
>>- 4.5 characters.
>>
>>I would like to use this feature for detecting the end of a received
>>message. The problem I have is that if I service an interrupt due the
>>the buffer being filled, and it also happens that that last character in
>>the buffer was the last character for the received message, the receive
>>time-out interrupt will not occur, resulting in the end of message not
>>being detected.
>>
>>Is there a solution, other than using a buffer length of 1 and using a
>>timer to measure the inter message gap?
>>
>>Cheers,
>>
>>Peter.
> > Hello Peter,
>
> this interrupt was not designed for your needs. It should prevent a
> communication from being stalled if some characters are trapped in queue
> which is not full.
> Just an idea: every time you receive a character reset a timer. If a
> timer interrupt occure prior a line idle interrupt, you have not
> received any characters for a certain time. It's ugly but should solve
> your problem.
>
> Sten
>
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
Thanks for your reply. Yes, this is what I'm doing now with the PIC chip
and was expecting to have to do on the Arm. As I'm new to it, I wasn't
sure if there was a neater way to do it. I moving (Trying to) to the Arm
for more Grunt.
Cheers,
peter
Sten wrote:
> Peter Homann wrote:
>
>>Hi,
>>
>>I am migrating a serial communications interface (Modbus) to a LPC2138
>>processor. The Modbus spec defines that an end of message has occurred
>>when a period equal to 3.5 characters has passed since the last
>>character has been received.
>>
>>The LPC uart can generate an interrupt if the receive buffer has
>>characters in it and no character has been received for a period of 3.5
>>- 4.5 characters.
>>
>>I would like to use this feature for detecting the end of a received
>>message. The problem I have is that if I service an interrupt due the
>>the buffer being filled, and it also happens that that last character in
>>the buffer was the last character for the received message, the receive
>>time-out interrupt will not occur, resulting in the end of message not
>>being detected.
>>
>>Is there a solution, other than using a buffer length of 1 and using a
>>timer to measure the inter message gap?
>>
>>Cheers,
>>
>>Peter.
> > Hello Peter,
>
> this interrupt was not designed for your needs. It should prevent a
> communication from being stalled if some characters are trapped in queue
> which is not full.
> Just an idea: every time you receive a character reset a timer. If a
> timer interrupt occure prior a line idle interrupt, you have not
> received any characters for a certain time. It's ugly but should solve
> your problem.
>
> Sten
>
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
Reply by ●November 9, 20052005-11-09
Hi, Peter. Have you verified your P0.14 is low during reset? It is
required to automatically enter ISP if the ROM checksum is good
(i.e., the ROM is not blank).
Guille
--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
> Hi,
>
> Thanks for the offer. I'd be interested in learning how to
implement
> Modbus on the LPC. Anything you can send will be a big help as I'm
new
> to the Arm processor.
>
> Now my LPC2138 processor has locked up and not talking to the
Philips
> flash utility. Hopefully I can get it working again.
>
> Cheers,
>
> Peter.
>
>
>
> radim100 wrote:
> > --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
> >
> >>Hi,
> >>
> >>I am migrating a serial communications interface (Modbus) to a
> >
> > LPC2138
> >
> >>processor. The Modbus spec defines that an end of message has
> >
> > occurred
> >
> >>when a period equal to 3.5 characters has passed since the last
> >>character has been received.
> >>
> >>The LPC uart can generate an interrupt if the receive buffer has
> >>characters in it and no character has been received for a period
of
> >
> > 3.5
> >
> >>- 4.5 characters.
> >>
> >>I would like to use this feature for detecting the end of a
received
> >>message. The problem I have is that if I service an interrupt due
> >
> > the
> >
> >>the buffer being filled, and it also happens that that last
> >
> > character in
> >
> >>the buffer was the last character for the received message, the
> >
> > receive
> >
> >>time-out interrupt will not occur, resulting in the end of
message
> >
> > not
> >
> >>being detected.
> >>
> >>Is there a solution, other than using a buffer length of 1 and
using
> >
> > a
> >
> >>timer to measure the inter message gap?
> >>
> >>Cheers,
> >>
> >>Peter.
> >>
> >>--
> >>------------------------------
> >>Web: www.homanndesigns.com
> >>email: homann@h...
> >>Phone: +61 421 601 665
> >>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> >>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> >>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
> >>
> >
> > If you are interested in MODBUS slave for LPC213X email me
> > and I can send you some code fot it
> > Radim design@m...
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> ------------------------------
> Web: www.homanndesigns.com
> email: homann@h...
> Phone: +61 421 601 665
> www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>
required to automatically enter ISP if the ROM checksum is good
(i.e., the ROM is not blank).
Guille
--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
> Hi,
>
> Thanks for the offer. I'd be interested in learning how to
implement
> Modbus on the LPC. Anything you can send will be a big help as I'm
new
> to the Arm processor.
>
> Now my LPC2138 processor has locked up and not talking to the
Philips
> flash utility. Hopefully I can get it working again.
>
> Cheers,
>
> Peter.
>
>
>
> radim100 wrote:
> > --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
> >
> >>Hi,
> >>
> >>I am migrating a serial communications interface (Modbus) to a
> >
> > LPC2138
> >
> >>processor. The Modbus spec defines that an end of message has
> >
> > occurred
> >
> >>when a period equal to 3.5 characters has passed since the last
> >>character has been received.
> >>
> >>The LPC uart can generate an interrupt if the receive buffer has
> >>characters in it and no character has been received for a period
of
> >
> > 3.5
> >
> >>- 4.5 characters.
> >>
> >>I would like to use this feature for detecting the end of a
received
> >>message. The problem I have is that if I service an interrupt due
> >
> > the
> >
> >>the buffer being filled, and it also happens that that last
> >
> > character in
> >
> >>the buffer was the last character for the received message, the
> >
> > receive
> >
> >>time-out interrupt will not occur, resulting in the end of
message
> >
> > not
> >
> >>being detected.
> >>
> >>Is there a solution, other than using a buffer length of 1 and
using
> >
> > a
> >
> >>timer to measure the inter message gap?
> >>
> >>Cheers,
> >>
> >>Peter.
> >>
> >>--
> >>------------------------------
> >>Web: www.homanndesigns.com
> >>email: homann@h...
> >>Phone: +61 421 601 665
> >>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> >>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> >>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
> >>
> >
> > If you are interested in MODBUS slave for LPC213X email me
> > and I can send you some code fot it
> > Radim design@m...
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> ------------------------------
> Web: www.homanndesigns.com
> email: homann@h...
> Phone: +61 421 601 665
> www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>
Reply by ●November 9, 20052005-11-09
Hi Guille,
From the schematic, P014 should by pulled low by the Philips utility
via pin 7 of com port 0?
Cheers,
Peter.
Guillermo Prandi wrote:
> Hi, Peter. Have you verified your P0.14 is low during reset? It is
> required to automatically enter ISP if the ROM checksum is good
> (i.e., the ROM is not blank).
>
> Guille
>
> --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
>>Hi,
>>
>>Thanks for the offer. I'd be interested in learning how to
>
> implement
>
>>Modbus on the LPC. Anything you can send will be a big help as I'm
>
> new
>
>>to the Arm processor.
>>
>>Now my LPC2138 processor has locked up and not talking to the
>
> Philips
>
>>flash utility. Hopefully I can get it working again.
>>
>>Cheers,
>>
>>Peter.
>>
>>
>>
>>radim100 wrote:
>>
>>>--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>I am migrating a serial communications interface (Modbus) to a
>>>
>>>LPC2138
>>>
>>>
>>>>processor. The Modbus spec defines that an end of message has
>>>
>>>occurred
>>>
>>>
>>>>when a period equal to 3.5 characters has passed since the last
>>>>character has been received.
>>>>
>>>>The LPC uart can generate an interrupt if the receive buffer has
>>>>characters in it and no character has been received for a period
>
> of
>
>>>3.5
>>>
>>>
>>>>- 4.5 characters.
>>>>
>>>>I would like to use this feature for detecting the end of a
>
> received
>
>>>>message. The problem I have is that if I service an interrupt due
>>>
>>>the
>>>
>>>
>>>>the buffer being filled, and it also happens that that last
>>>
>>>character in
>>>
>>>
>>>>the buffer was the last character for the received message, the
>>>
>>>receive
>>>
>>>
>>>>time-out interrupt will not occur, resulting in the end of
>
> message
>
>>>not
>>>
>>>
>>>>being detected.
>>>>
>>>>Is there a solution, other than using a buffer length of 1 and
>
> using
>
>>>a
>>>
>>>
>>>>timer to measure the inter message gap?
>>>>
>>>>Cheers,
>>>>
>>>>Peter.
>>>>
>>>>--
>>>>------------------------------
>>>>Web: www.homanndesigns.com
>>>>email: homann@h...
>>>>Phone: +61 421 601 665
>>>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>>>
>>>
>>>If you are interested in MODBUS slave for LPC213X email me
>>>and I can send you some code fot it
>>>Radim design@m...
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>--
>>------------------------------
>>Web: www.homanndesigns.com
>>email: homann@h...
>>Phone: +61 421 601 665
>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
From the schematic, P014 should by pulled low by the Philips utility
via pin 7 of com port 0?
Cheers,
Peter.
Guillermo Prandi wrote:
> Hi, Peter. Have you verified your P0.14 is low during reset? It is
> required to automatically enter ISP if the ROM checksum is good
> (i.e., the ROM is not blank).
>
> Guille
>
> --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
>>Hi,
>>
>>Thanks for the offer. I'd be interested in learning how to
>
> implement
>
>>Modbus on the LPC. Anything you can send will be a big help as I'm
>
> new
>
>>to the Arm processor.
>>
>>Now my LPC2138 processor has locked up and not talking to the
>
> Philips
>
>>flash utility. Hopefully I can get it working again.
>>
>>Cheers,
>>
>>Peter.
>>
>>
>>
>>radim100 wrote:
>>
>>>--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>I am migrating a serial communications interface (Modbus) to a
>>>
>>>LPC2138
>>>
>>>
>>>>processor. The Modbus spec defines that an end of message has
>>>
>>>occurred
>>>
>>>
>>>>when a period equal to 3.5 characters has passed since the last
>>>>character has been received.
>>>>
>>>>The LPC uart can generate an interrupt if the receive buffer has
>>>>characters in it and no character has been received for a period
>
> of
>
>>>3.5
>>>
>>>
>>>>- 4.5 characters.
>>>>
>>>>I would like to use this feature for detecting the end of a
>
> received
>
>>>>message. The problem I have is that if I service an interrupt due
>>>
>>>the
>>>
>>>
>>>>the buffer being filled, and it also happens that that last
>>>
>>>character in
>>>
>>>
>>>>the buffer was the last character for the received message, the
>>>
>>>receive
>>>
>>>
>>>>time-out interrupt will not occur, resulting in the end of
>
> message
>
>>>not
>>>
>>>
>>>>being detected.
>>>>
>>>>Is there a solution, other than using a buffer length of 1 and
>
> using
>
>>>a
>>>
>>>
>>>>timer to measure the inter message gap?
>>>>
>>>>Cheers,
>>>>
>>>>Peter.
>>>>
>>>>--
>>>>------------------------------
>>>>Web: www.homanndesigns.com
>>>>email: homann@h...
>>>>Phone: +61 421 601 665
>>>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>>>
>>>
>>>If you are interested in MODBUS slave for LPC213X email me
>>>and I can send you some code fot it
>>>Radim design@m...
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>--
>>------------------------------
>>Web: www.homanndesigns.com
>>email: homann@h...
>>Phone: +61 421 601 665
>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
Reply by ●November 9, 20052005-11-09
--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
> From the schematic, P014 should by pulled low by the Philips utility
> via pin 7 of com port 0?
>
It should be ... but maybe it's not. Check it as Guillermo suggested.
Try to do it manual.
> From the schematic, P014 should by pulled low by the Philips utility
> via pin 7 of com port 0?
>
It should be ... but maybe it's not. Check it as Guillermo suggested.
Try to do it manual.
Reply by ●November 9, 20052005-11-09
Peter, whether or not the Philips utility turns P0.14 low is entirely
dependent of your hardware connections!
In LPC2138, P0.14 is pin 41. For the LPC2138 to talk to the Philips
utility, one of three things must happen:
1) You boot with a blank or invalid ROM.
2) You boot with P0.14 low (less than 0.8 volts on pin 41 during
boot).
3) You intentionally call the Phillips boot loader from your LPC code.
In order to turn pin P0.14 low, you must get to know what is that pin
connected to. For example, in the New Micros' Tini213/38 controller
interface board, there's a jumper (J11) to set P0.14 to low/high. If
you have the Tini2138 module alone, then it's pin 19 of the module
that must be connected to GND. I know nothing about other development
kits (or your hardware), but there's normally some mechanism allowing
this kind of set up. I'm not aware of the RS-232 signal management of
the Philips utility, but anyway in order to produce any effect on the
P0.14 pin of the chip from the utility, some RS-232 signal (most
likely RTS or DTR) must be connected through proper interfacing to
pin P0.14 of the LPC.
Guille
--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
> Hi Guille,
>
> From the schematic, P014 should by pulled low by the Philips
utility
> via pin 7 of com port 0?
>
> Cheers,
>
> Peter.
>
> Guillermo Prandi wrote:
> > Hi, Peter. Have you verified your P0.14 is low during reset? It
is
> > required to automatically enter ISP if the ROM checksum is good
> > (i.e., the ROM is not blank).
> >
> > Guille
> >
> > --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
> >
> >>Hi,
> >>
> >>Thanks for the offer. I'd be interested in learning how to
> >
> > implement
> >
> >>Modbus on the LPC. Anything you can send will be a big help as
I'm
> >
> > new
> >
> >>to the Arm processor.
> >>
> >>Now my LPC2138 processor has locked up and not talking to the
> >
> > Philips
> >
> >>flash utility. Hopefully I can get it working again.
> >>
> >>Cheers,
> >>
> >>Peter.
> >>
> >>
> >>
> >>radim100 wrote:
> >>
> >>>--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>I am migrating a serial communications interface (Modbus) to a
> >>>
> >>>LPC2138
> >>>
> >>>
> >>>>processor. The Modbus spec defines that an end of message has
> >>>
> >>>occurred
> >>>
> >>>
> >>>>when a period equal to 3.5 characters has passed since the last
> >>>>character has been received.
> >>>>
> >>>>The LPC uart can generate an interrupt if the receive buffer
has
> >>>>characters in it and no character has been received for a
period
> >
> > of
> >
> >>>3.5
> >>>
> >>>
> >>>>- 4.5 characters.
> >>>>
> >>>>I would like to use this feature for detecting the end of a
> >
> > received
> >
> >>>>message. The problem I have is that if I service an interrupt
due
> >>>
> >>>the
> >>>
> >>>
> >>>>the buffer being filled, and it also happens that that last
> >>>
> >>>character in
> >>>
> >>>
> >>>>the buffer was the last character for the received message, the
> >>>
> >>>receive
> >>>
> >>>
> >>>>time-out interrupt will not occur, resulting in the end of
> >
> > message
> >
> >>>not
> >>>
> >>>
> >>>>being detected.
> >>>>
> >>>>Is there a solution, other than using a buffer length of 1 and
> >
> > using
> >
> >>>a
> >>>
> >>>
> >>>>timer to measure the inter message gap?
> >>>>
> >>>>Cheers,
> >>>>
> >>>>Peter.
> >>>>
> >>>>--
> >>>>----------------------------
--
> >>>>Web: www.homanndesigns.com
> >>>>email: homann@h...
> >>>>Phone: +61 421 601 665
> >>>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> >>>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> >>>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade
board
> >>>>
> >>>
> >>>If you are interested in MODBUS slave for LPC213X email me
> >>>and I can send you some code fot it
> >>>Radim design@m...
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>Yahoo! Groups Links
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>--
> >>------------------------------
> >>Web: www.homanndesigns.com
> >>email: homann@h...
> >>Phone: +61 421 601 665
> >>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> >>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> >>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
> >>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> ------------------------------
> Web: www.homanndesigns.com
> email: homann@h...
> Phone: +61 421 601 665
> www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>
dependent of your hardware connections!
In LPC2138, P0.14 is pin 41. For the LPC2138 to talk to the Philips
utility, one of three things must happen:
1) You boot with a blank or invalid ROM.
2) You boot with P0.14 low (less than 0.8 volts on pin 41 during
boot).
3) You intentionally call the Phillips boot loader from your LPC code.
In order to turn pin P0.14 low, you must get to know what is that pin
connected to. For example, in the New Micros' Tini213/38 controller
interface board, there's a jumper (J11) to set P0.14 to low/high. If
you have the Tini2138 module alone, then it's pin 19 of the module
that must be connected to GND. I know nothing about other development
kits (or your hardware), but there's normally some mechanism allowing
this kind of set up. I'm not aware of the RS-232 signal management of
the Philips utility, but anyway in order to produce any effect on the
P0.14 pin of the chip from the utility, some RS-232 signal (most
likely RTS or DTR) must be connected through proper interfacing to
pin P0.14 of the LPC.
Guille
--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
> Hi Guille,
>
> From the schematic, P014 should by pulled low by the Philips
utility
> via pin 7 of com port 0?
>
> Cheers,
>
> Peter.
>
> Guillermo Prandi wrote:
> > Hi, Peter. Have you verified your P0.14 is low during reset? It
is
> > required to automatically enter ISP if the ROM checksum is good
> > (i.e., the ROM is not blank).
> >
> > Guille
> >
> > --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
> >
> >>Hi,
> >>
> >>Thanks for the offer. I'd be interested in learning how to
> >
> > implement
> >
> >>Modbus on the LPC. Anything you can send will be a big help as
I'm
> >
> > new
> >
> >>to the Arm processor.
> >>
> >>Now my LPC2138 processor has locked up and not talking to the
> >
> > Philips
> >
> >>flash utility. Hopefully I can get it working again.
> >>
> >>Cheers,
> >>
> >>Peter.
> >>
> >>
> >>
> >>radim100 wrote:
> >>
> >>>--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>I am migrating a serial communications interface (Modbus) to a
> >>>
> >>>LPC2138
> >>>
> >>>
> >>>>processor. The Modbus spec defines that an end of message has
> >>>
> >>>occurred
> >>>
> >>>
> >>>>when a period equal to 3.5 characters has passed since the last
> >>>>character has been received.
> >>>>
> >>>>The LPC uart can generate an interrupt if the receive buffer
has
> >>>>characters in it and no character has been received for a
period
> >
> > of
> >
> >>>3.5
> >>>
> >>>
> >>>>- 4.5 characters.
> >>>>
> >>>>I would like to use this feature for detecting the end of a
> >
> > received
> >
> >>>>message. The problem I have is that if I service an interrupt
due
> >>>
> >>>the
> >>>
> >>>
> >>>>the buffer being filled, and it also happens that that last
> >>>
> >>>character in
> >>>
> >>>
> >>>>the buffer was the last character for the received message, the
> >>>
> >>>receive
> >>>
> >>>
> >>>>time-out interrupt will not occur, resulting in the end of
> >
> > message
> >
> >>>not
> >>>
> >>>
> >>>>being detected.
> >>>>
> >>>>Is there a solution, other than using a buffer length of 1 and
> >
> > using
> >
> >>>a
> >>>
> >>>
> >>>>timer to measure the inter message gap?
> >>>>
> >>>>Cheers,
> >>>>
> >>>>Peter.
> >>>>
> >>>>--
> >>>>----------------------------
--
> >>>>Web: www.homanndesigns.com
> >>>>email: homann@h...
> >>>>Phone: +61 421 601 665
> >>>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> >>>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> >>>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade
board
> >>>>
> >>>
> >>>If you are interested in MODBUS slave for LPC213X email me
> >>>and I can send you some code fot it
> >>>Radim design@m...
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>Yahoo! Groups Links
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>--
> >>------------------------------
> >>Web: www.homanndesigns.com
> >>email: homann@h...
> >>Phone: +61 421 601 665
> >>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> >>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> >>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
> >>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> ------------------------------
> Web: www.homanndesigns.com
> email: homann@h...
> Phone: +61 421 601 665
> www.homanndesigns.com/ModIO.html - Modbus Interface Unit
> www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
> www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>
Reply by ●November 9, 20052005-11-09
Hi Guillermo,
THanks for the reply. As P0.14 is connected to the serial port, I am
assuming it is controlled by the Philips utility. I will verify that,
but also control it manually.
Is it possible to erase the bootloader? Also, is the bootloader serial
protocol documented somewhere?
Cheers,
Peter.
Guillermo Prandi wrote:
> Peter, whether or not the Philips utility turns P0.14 low is entirely
> dependent of your hardware connections!
>
> In LPC2138, P0.14 is pin 41. For the LPC2138 to talk to the Philips
> utility, one of three things must happen:
>
> 1) You boot with a blank or invalid ROM.
> 2) You boot with P0.14 low (less than 0.8 volts on pin 41 during
> boot).
> 3) You intentionally call the Phillips boot loader from your LPC code.
>
> In order to turn pin P0.14 low, you must get to know what is that pin
> connected to. For example, in the New Micros' Tini213/38 controller
> interface board, there's a jumper (J11) to set P0.14 to low/high. If
> you have the Tini2138 module alone, then it's pin 19 of the module
> that must be connected to GND. I know nothing about other development
> kits (or your hardware), but there's normally some mechanism allowing
> this kind of set up. I'm not aware of the RS-232 signal management of
> the Philips utility, but anyway in order to produce any effect on the
> P0.14 pin of the chip from the utility, some RS-232 signal (most
> likely RTS or DTR) must be connected through proper interfacing to
> pin P0.14 of the LPC.
>
> Guille
>
> --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
>>Hi Guille,
>>
>> From the schematic, P014 should by pulled low by the Philips
>
> utility
>
>>via pin 7 of com port 0?
>>
>>Cheers,
>>
>>Peter.
>>
>>Guillermo Prandi wrote:
>>
>>>Hi, Peter. Have you verified your P0.14 is low during reset? It
>
> is
>
>>>required to automatically enter ISP if the ROM checksum is good
>>>(i.e., the ROM is not blank).
>>>
>>>Guille
>>>
>>>--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>Thanks for the offer. I'd be interested in learning how to
>>>
>>>implement
>>>
>>>
>>>>Modbus on the LPC. Anything you can send will be a big help as
>
> I'm
>
>>>new
>>>
>>>
>>>>to the Arm processor.
>>>>
>>>>Now my LPC2138 processor has locked up and not talking to the
>>>
>>>Philips
>>>
>>>
>>>>flash utility. Hopefully I can get it working again.
>>>>
>>>>Cheers,
>>>>
>>>>Peter.
>>>>
>>>>
>>>>
>>>>radim100 wrote:
>>>>
>>>>
>>>>>--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I am migrating a serial communications interface (Modbus) to a
>>>>>
>>>>>LPC2138
>>>>>
>>>>>
>>>>>
>>>>>>processor. The Modbus spec defines that an end of message has
>>>>>
>>>>>occurred
>>>>>
>>>>>
>>>>>
>>>>>>when a period equal to 3.5 characters has passed since the last
>>>>>>character has been received.
>>>>>>
>>>>>>The LPC uart can generate an interrupt if the receive buffer
>
> has
>
>>>>>>characters in it and no character has been received for a
>
> period
>
>>>of
>>>
>>>
>>>>>3.5
>>>>>
>>>>>
>>>>>
>>>>>>- 4.5 characters.
>>>>>>
>>>>>>I would like to use this feature for detecting the end of a
>>>
>>>received
>>>
>>>
>>>>>>message. The problem I have is that if I service an interrupt
>
> due
>
>>>>>the
>>>>>
>>>>>
>>>>>
>>>>>>the buffer being filled, and it also happens that that last
>>>>>
>>>>>character in
>>>>>
>>>>>
>>>>>
>>>>>>the buffer was the last character for the received message, the
>>>>>
>>>>>receive
>>>>>
>>>>>
>>>>>
>>>>>>time-out interrupt will not occur, resulting in the end of
>>>
>>>message
>>>
>>>
>>>>>not
>>>>>
>>>>>
>>>>>
>>>>>>being detected.
>>>>>>
>>>>>>Is there a solution, other than using a buffer length of 1 and
>>>
>>>using
>>>
>>>
>>>>>a
>>>>>
>>>>>
>>>>>
>>>>>>timer to measure the inter message gap?
>>>>>>
>>>>>>Cheers,
>>>>>>
>>>>>>Peter.
>>>>>>
>>>>>>--
>>>>>>----------------------------
>
> --
>
>>>>>>Web: www.homanndesigns.com
>>>>>>email: homann@h...
>>>>>>Phone: +61 421 601 665
>>>>>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>>>>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>>>>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade
>
> board
>
>>>>>If you are interested in MODBUS slave for LPC213X email me
>>>>>and I can send you some code fot it
>>>>>Radim design@m...
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>Yahoo! Groups Links
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>--
>>>>------------------------------
>>>>Web: www.homanndesigns.com
>>>>email: homann@h...
>>>>Phone: +61 421 601 665
>>>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>--
>>------------------------------
>>Web: www.homanndesigns.com
>>email: homann@h...
>>Phone: +61 421 601 665
>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
THanks for the reply. As P0.14 is connected to the serial port, I am
assuming it is controlled by the Philips utility. I will verify that,
but also control it manually.
Is it possible to erase the bootloader? Also, is the bootloader serial
protocol documented somewhere?
Cheers,
Peter.
Guillermo Prandi wrote:
> Peter, whether or not the Philips utility turns P0.14 low is entirely
> dependent of your hardware connections!
>
> In LPC2138, P0.14 is pin 41. For the LPC2138 to talk to the Philips
> utility, one of three things must happen:
>
> 1) You boot with a blank or invalid ROM.
> 2) You boot with P0.14 low (less than 0.8 volts on pin 41 during
> boot).
> 3) You intentionally call the Phillips boot loader from your LPC code.
>
> In order to turn pin P0.14 low, you must get to know what is that pin
> connected to. For example, in the New Micros' Tini213/38 controller
> interface board, there's a jumper (J11) to set P0.14 to low/high. If
> you have the Tini2138 module alone, then it's pin 19 of the module
> that must be connected to GND. I know nothing about other development
> kits (or your hardware), but there's normally some mechanism allowing
> this kind of set up. I'm not aware of the RS-232 signal management of
> the Philips utility, but anyway in order to produce any effect on the
> P0.14 pin of the chip from the utility, some RS-232 signal (most
> likely RTS or DTR) must be connected through proper interfacing to
> pin P0.14 of the LPC.
>
> Guille
>
> --- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>
>>Hi Guille,
>>
>> From the schematic, P014 should by pulled low by the Philips
>
> utility
>
>>via pin 7 of com port 0?
>>
>>Cheers,
>>
>>Peter.
>>
>>Guillermo Prandi wrote:
>>
>>>Hi, Peter. Have you verified your P0.14 is low during reset? It
>
> is
>
>>>required to automatically enter ISP if the ROM checksum is good
>>>(i.e., the ROM is not blank).
>>>
>>>Guille
>>>
>>>--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>Thanks for the offer. I'd be interested in learning how to
>>>
>>>implement
>>>
>>>
>>>>Modbus on the LPC. Anything you can send will be a big help as
>
> I'm
>
>>>new
>>>
>>>
>>>>to the Arm processor.
>>>>
>>>>Now my LPC2138 processor has locked up and not talking to the
>>>
>>>Philips
>>>
>>>
>>>>flash utility. Hopefully I can get it working again.
>>>>
>>>>Cheers,
>>>>
>>>>Peter.
>>>>
>>>>
>>>>
>>>>radim100 wrote:
>>>>
>>>>
>>>>>--- In lpc2000@lpc2..., Peter Homann <groups@h...> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I am migrating a serial communications interface (Modbus) to a
>>>>>
>>>>>LPC2138
>>>>>
>>>>>
>>>>>
>>>>>>processor. The Modbus spec defines that an end of message has
>>>>>
>>>>>occurred
>>>>>
>>>>>
>>>>>
>>>>>>when a period equal to 3.5 characters has passed since the last
>>>>>>character has been received.
>>>>>>
>>>>>>The LPC uart can generate an interrupt if the receive buffer
>
> has
>
>>>>>>characters in it and no character has been received for a
>
> period
>
>>>of
>>>
>>>
>>>>>3.5
>>>>>
>>>>>
>>>>>
>>>>>>- 4.5 characters.
>>>>>>
>>>>>>I would like to use this feature for detecting the end of a
>>>
>>>received
>>>
>>>
>>>>>>message. The problem I have is that if I service an interrupt
>
> due
>
>>>>>the
>>>>>
>>>>>
>>>>>
>>>>>>the buffer being filled, and it also happens that that last
>>>>>
>>>>>character in
>>>>>
>>>>>
>>>>>
>>>>>>the buffer was the last character for the received message, the
>>>>>
>>>>>receive
>>>>>
>>>>>
>>>>>
>>>>>>time-out interrupt will not occur, resulting in the end of
>>>
>>>message
>>>
>>>
>>>>>not
>>>>>
>>>>>
>>>>>
>>>>>>being detected.
>>>>>>
>>>>>>Is there a solution, other than using a buffer length of 1 and
>>>
>>>using
>>>
>>>
>>>>>a
>>>>>
>>>>>
>>>>>
>>>>>>timer to measure the inter message gap?
>>>>>>
>>>>>>Cheers,
>>>>>>
>>>>>>Peter.
>>>>>>
>>>>>>--
>>>>>>----------------------------
>
> --
>
>>>>>>Web: www.homanndesigns.com
>>>>>>email: homann@h...
>>>>>>Phone: +61 421 601 665
>>>>>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>>>>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>>>>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade
>
> board
>
>>>>>If you are interested in MODBUS slave for LPC213X email me
>>>>>and I can send you some code fot it
>>>>>Radim design@m...
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>Yahoo! Groups Links
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>--
>>>>------------------------------
>>>>Web: www.homanndesigns.com
>>>>email: homann@h...
>>>>Phone: +61 421 601 665
>>>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>--
>>------------------------------
>>Web: www.homanndesigns.com
>>email: homann@h...
>>Phone: +61 421 601 665
>>www.homanndesigns.com/ModIO.html - Modbus Interface Unit
>>www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
>>www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
>>
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
--
------------------------------
Web: www.homanndesigns.com
email: homann@homa...
Phone: +61 421 601 665
www.homanndesigns.com/ModIO.html - Modbus Interface Unit
www.homanndesigns.com/DigiSpeedDeal.html - DC Spindle control
www.homanndesigns.com/TurboTaig.html - Taig Mill Upgrade board
