I do have the ISR, and my debugger never reaches that point. Looking at
another project it looks like I have my interrupt enabler in the wrong spot.
this is what is all looks like now.

#include <p33fj256gp710.h>

char message[100] = "TEST";
int messagePosition = 0;

void initUART()
{
    U1STA = 0;
    //U1STAbits.UTXEN = 1;

    U1MODE = 0;
    U1MODEbits.UARTEN = 1;
}


void __attribute__((__interrupt__)) _T1Interrupt( void )
{
    IFS0bits.U1TXIF = 0;
    U1TXREG = message[messagePosition++];
}

void send(char data)
{
    U1STAbits.UTXEN = 0;

    message[0] = data;
    U1TXREG=message[0];
    messagePosition = 0;

    IFS0bits.U1TXIF = 0;
    IEC0bits.U1TXIE = 1;
    U1STAbits.UTXEN = 1;
}

Setting breakpoints I am seeing the following, after UARTEN = 1, I get URXDA
and OERR on U1STA.
After U1STAbits.UTXEN = 0 in send, those bits clear again.


On Sun, Mar 23, 2008 at 8:52 PM, Harold Hallikainen <harold@hallikainen.org>
wrote:

> You do have an interrupt service routine, right? Do you have a debugger?
> If so, I'd set a breakpoint at the first line of your ISR, then see what
> happens. Note that if the debugger does not indicate where the program
> stopped in your source code, try viewing program memory. That will show
> you where the code being executed is. I sometimes find it stuck in an
> invalid address trap.
>
> Good luck!
>
> Harold
>
>
> > Here is my function to setup the uart interrupt
> > void initUART()
> > {
> >     U1BRG = 187;
> >     IFS0 = 0;
> >
> >     U1MODE = 0;
> >     U1MODEbits.UARTEN = 1;
> >     U1MODEbits.ABAUD = 1;
> >
> >     IEC0 = 0;
> >     IEC0bits.U1TXIE = 1;
> >
> >     U1STA = 0;
> >     U1STAbits.UTXEN = 1;
> > }
> >
> > after this, I just loop in my main function, if I comment out the UTXEN
> > line, it will work, otherwise it just bails out here. Do not understand
> > what
> > is happening.
> >
> > --
> > http://morglog.alleycatracing.com
> > Lets make up more accronyms!
> >
> > http://www.alleycatracing.com
> > LTABOTIIOFR! ROFL! ROFL! ROFL!
> > Upcoming alley cats, reviews, touring logs, and a general congregation
> of
> > bike nerdity.
> > --
> > http://www.piclist.com PIC/SX FAQ & list archive
> > View/change your membership options at
> > http://mailman.mit.edu/mailman/listinfo/piclist
> >
>
>
> --
> FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
> opportunities available!
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>



-- 
http://morglog.alleycatracing.com
Lets make up more accronyms!

http://www.alleycatracing.com
LTABOTIIOFR! ROFL! ROFL! ROFL!
Upcoming alley cats, reviews, touring logs, and a general congregation of
bike nerdity.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist