Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
Discussion Groups | LPC2000 | UART1 and FIFO Reset (ISSUE)
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
UART1 and FIFO Reset (ISSUE) - genie_23432 - Aug 3 11:04:00 2005
Hello,
After much fustration I appear to have solved most of my stability
issues (although not all of them). I seem to have an undocumented
issue with UART1 on the LPC2119 and was wondering if anyone else ran
into the same problem. At the very least I figure I would warn
people about the potential issue since I couldn't find it in the
current errata.
It appears that using the RX FIFO Reset when running at highspeed
(over 100Kbps) that the behavior of the UART is very unpredictable.
I believe it might also exist at slower speeds although less often.
In my application I wanted to flush the FIFO when any error occured
so that I could try and more quickly resync on the data and avoid
reading corrupted data. As stated using the FIFO reset cause
unpredictable behavior such as: having the THRE interrupt ignored,
having the UART FIFO randomly being disabled, and having a character
time-out indicator interrupt I could not clear even though the
receive data ready bit said no data was in the fifo.
Unfortuantly I do not have too much time to investigate this
behaviour at this time since I wasted well over a week on this
project trying to solve my serial issues. All I know for sure is
that changing nothing in the code except for removing the FIFO reset
line solved over 90% of my issues. I still have some other issues
that may be related to the UART but I have not been able to confirm
this. I will be contacting Phillips in regards to this issue to see
what they have to say.
Pascal
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
After much fustration I appear to have solved most of my stability
issues (although not all of them). I seem to have an undocumented
issue with UART1 on the LPC2119 and was wondering if anyone else ran
into the same problem. At the very least I figure I would warn
people about the potential issue since I couldn't find it in the
current errata.
It appears that using the RX FIFO Reset when running at highspeed
(over 100Kbps) that the behavior of the UART is very unpredictable.
I believe it might also exist at slower speeds although less often.
In my application I wanted to flush the FIFO when any error occured
so that I could try and more quickly resync on the data and avoid
reading corrupted data. As stated using the FIFO reset cause
unpredictable behavior such as: having the THRE interrupt ignored,
having the UART FIFO randomly being disabled, and having a character
time-out indicator interrupt I could not clear even though the
receive data ready bit said no data was in the fifo.
Unfortuantly I do not have too much time to investigate this
behaviour at this time since I wasted well over a week on this
project trying to solve my serial issues. All I know for sure is
that changing nothing in the code except for removing the FIFO reset
line solved over 90% of my issues. I still have some other issues
that may be related to the UART but I have not been able to confirm
this. I will be contacting Phillips in regards to this issue to see
what they have to say.
Pascal
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )