Search found 43 matches

It's still 0xEF. It's likely promoting it to a signed 16-bit value, which is 0xFFEF.
Try doing the following, shown in bold below:
if (rs232MsgInBuff2(int8)0xEF){
}

I don't have PCD so I can' ...

1) I'm on a PIC24FV32KA302
2) I am on an older CCS version V4.132

What about this item in the CCS versions list ?
4.141 Various chip specific built in functions fixes have been made
4.141 ...

/*Globals*/
#define BUFFER_DATA_SIZE 25
unsigned int8 rs232MsgInBuff[BUFFER_DATA_SIZE]; // change 1
unsigned int8 rs232MsgInBuff2[BUFFER_DATA_SIZE]; // change 2 - do these fi ...

EDIT: That said, if you aren't going to be sending exclusively ascii (values less than 0x80), then you should probably make your arrays unsigned chars instead of signed chars.

You might have som ...

The pic24 series is a 16bit chip (hence the sign extension to FFEF...while leading zeros are defaulted to discarded so 0030 shows up as just 30). Try %02X instead and see if that keeps it down to 2 ...

Also, you should have told us the following in your post:
1. Your PIC.
2. Your CCS compiler version.
3. Name of your terminal program
4. #use rs232 statement.
5. Preferably a full test p ...

Hi All,

I've got a strange issue with (possibly?) typing and I'm hoping I can have some light shed on it. I'm finding that my char array I'm using to process serial is showing extra bits for certa ...

Okay I resolved my issues I was having. The issue was in the layout of my ISR. The function I posted does seem to be a suitable port of the convenience function.

However I did turn the I2C_ISR_St ...

Hi all,

I've got an interesting situation on my hands and I'm hoping someone here might be familiar enough with the CCS built in functions to shed some light on it.

I'm working on some I2C code ...

Problem is that it won't do a getc, unless kbhit is set. Now the getc, is what triggers the error clearing code. As such there is the potential to sit looping, depending on how the CCS code sets thing ...

heh, as far at the fast IO is concerned, I have no idea why that's there. I inherited a bunch of PIC code that all have their RDA ISRs configured in this way and the way the guy did things I'm decent ...

Also, realise that the RDA interrupt means _one_ character is ready to be read. The ISR should read just this character. Look at ex_sisr.
As it stands _your_ handler could receive hundreds of charact ...

Hi all,

I've got a bit of a strange situation that I'm not entirely sure how to handle.
I am using PCWHD v4.132
the PIC is a PIC24FV32KA304

What I'm looking to do is to "protect" my ...

As some comments:

1) You are setting up streams in the I2C setup, but not then using this. Stick with either:
a) Use streams throughout - so the I2C write should also be using a stream name, or
...

Look at the .LST file to see if the compiler is using software i2c.
For 18F PICs, this thread shows what the ASM code will look like:
http://www.ccsinfo.com/forum/viewtopic.php?t=31547&highlight ...