Robert, thanks for your ideas.
Alas... "Houston..we have a problem". :-)
I have found out that I can service only INT of TIMER0, and not TIMER1
and UART0_THRE. It appears, the problem might be somewhere else
(ivt.s -> linking?).
In the polled Tx_ing there is no problem, I got 115200 out okay.
FIFO is okay, but I want to buffer it w/128 bytes and INT.
Is it foolish?
Page 89 looks (Oct 02, '03 specs) great, I have not study it until
today on a train.
I think FIFO/U0THR needs to be "primed", as you have hinted y'day.
Summary:
my_debug_ability = 0;
JTAG_access=0;
ddd_or_insight=0;
GNUARM+=cygwin;
Olimex = 0x01;
Does this snippet look okay (for IRQ ints)?
NOP
LDR PC, [PC, #-0xFF0] <---- what happens here?
LDR PC, FIQ_Addr
Undefined_Addr: .word Undefined_Handler
SWI_Addr: .word SWI_Handler
Prefetch_Addr: .word Prefetch_Handler
Abort_Addr: .word Abort_Handler
FIQ_Addr: .word FIQ_Handler
Happy SW trails!
--roger
--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> wrote:
> I'm going to take a deeper look at this in a bit (when I get a
break) but
> initially it looks OK. In the meantime, however, a couple of
> questions/suggestions.
>
> - Is anything happening at the receive side (Is the transmit looped
back,
> is the receive getting info from somewhere) or is it transmit only?
> - How about putting in a check in the main body (IE non-interrupt)
or the
> timer to check the THRE flag and set an LED if it is set? That
way you
> should be able to tell if the flag has gone up but the interrupt has
> disappeared. Maybe you've found a way to harden what I've seen.
>
> At 02:40 PM 7/28/04 +0000, you wrote:
> >void tx(char c)
> >{
> > UART0_THR = c;
> >}
> >
> >..and then I expect INT (after the 8th bit is out).
>
> I figured it was probably something like that. Just wanted to be
sure of
> the obvious :)
>
> Robert
>
>
> " 'Freedom' has no meaning of itself. There are always restrictions,
> be they legal, genetic, or physical. If you don't believe me, try to
> chew a radio signal. "
>
> Kelvin Throop, IIIMessage
Re: TX FIFO
2004-07-29 by roger_lynx
Attachments
- No local attachments were found for this message.