Search found 211 matches

Thanks very muchly.

Same here.

Unless you are using multiple compilation units, "static" outside of a function does nothing I believe.

The CCS ported code is flaky with DSPIC. I believe it doesn't respect some of the spi timing correctly.

Our solution was to rewrite the low level code using CCS spi functions entirely.

Now it wo ...

Hi all,

Does anyone have timing comparisons for 32 vs 64 bit floating point on DSPIC?

(yeah, I know I could try it myself, but this may be quicker)

Be thankful it's not i = i + (int8)1;

:D

Sorry I forget to mention mplabX IPE v 3.65. Yes PCM programmer is right. I'm just using it to write to chip and mainly I am using ccs IDE to write the code and can never it to hex. I cannot understan ...

Gotta leave something for the student to do ;)

School project ?

How is the font defined?

I define my fonts as

const unsigned int8 font7x5[99][5] =
{
// char 32 == ' '
0x00, 0x00, 0x00, 0x00, 0x00,

etc...

const puts it in ROM i ...

Either

sprintf(temp_value, "%c", MENU);

or

sprintf(temp_value, "%c", &MENU[0]);

several thousand projects

Shocked

Superman.

Can confirm, that at least as far as the address for the I2C2 command register, 5.074 does fix things.

Can also confirm that a problem that was introduced by 5.072, and not fixed in 5.073 (again on ...

Oh sure, I do that, but using the CCS IDE selector.

Trouble is they may break something which has already been tested and may not show up for a while, so I stick with 5.070 until we ship Smile

I informed CCS of this problem a few weeks ago.

The latest update, 5.074 says they have fixed it. I have not tried it yet - usually CCS updates break something else and I'm at a tight part of the p ...

Thanks, thats what I suspected Smile