Search found 1343 matches

if you are crafty and very very careful, you can setup a timer interrupt, then in the ISR handler inspect the stack to figure out where the interrupt occurred in the main code. If you are running a d ...

So, as I said, you need to show us the first few lines of this file,

functions.c

void Blink_Led (void);
void Blink_CO_Led(void ...

The C standard doesn't have an rtc_time_t type, so I wouldn't compare them. In general, it would really come down to how the PIC implements the RTC registers as to what the time base is, so I would r ...

Thanks, the manual still doesn't clearly explain how the function works. I tested it with the ICD and understand how it functions now.

I would definitely suggest you give that feedback to CCS via t ...

you might also be able to predefine string constants and just pass them into printf using "%s" and a tertiary operator to select which one is passed in.

However, I don't understand why this works! atol() is supposed to return a signed int16, and looking at the internal code for atol() in stdlib.h, it definitely does all its calculations with signed ...

Thanks. It just seems odd since the include file is supplied by CCS.

Well they are human. Sometimes they make mistakes. It's easy to do when microchip is putting out so many new chips and chip va ...

I confirmed that there is an SFR named CM1CON0 so what gives?

Thanks.
Glenn

did you confirm it in the device database in CCS or in the datasheet? Sometimes the device database has errors, ...

OK.
As Jeriemiah says, you can use priorities, but these generally only change
the order the interrupts are serviced. On DsPIC's interrupts can interrupt
each other (if you enable nested interrupt ...

Depending on the PIC you are using you can potentially set the timer interrupt to a higher priority than the serial interrupt, allowing it to interrupt the interrupt. Just don't share variables betwe ...

Your printf takes time (lots of time) so by the time you are finished printing, the hardware buffer has filled up and overflowed, which means you just "miss" any characters that come after t ...

There really shouldn't be any ASM associated with output_X and set_tris_x that hangs up. Those don't usually poll any registers (you can check your ASM to verify though). My guess is something else ...

So is either using UART1, or specifying the pins (e.g. xmit=PIN_C6,rcv=PIN_C7), both do the same thing?

I'm guessing that specifying the pins is superfluous since you can't pick and choose the pins ...

thanx all!
#use delay(internal=8000000)

#PIN_SELECT U1RX=PIN_B7
#PIN_SELECT U1TX=PIN_B6
#use RS232(stream=debug, UART1, Baud=38400, ERRORS)
Works, but doesn't raise a warning. ...

If I use puts() instead, then it works without any problems.

gaugeguy already provided a solution, but wanted to address this part for your understanding.

the puts() function is much much qu ...