Search found 2333 matches

I do NOT trust so called 'standards'

If you can't rely on a C compiler's basic compliance with the C standard, you are lost. CCS C does generally comply with the ANSI C standard, but there are a fe ...

Of course there can be other than software related problems. But not reading back the written RTC values refers to software issue.

As a workaround for the said built-in function bug, you can set RT ...

The generated code of V4.135 is
.................... setup_rtc(RTC_ENABLE | RTC_OUTPUT_SECONDS, 0x00);
044A: MOV #0,W1
044C: MOV #55,W2
044E: MOV W2,[W1 ...

Built-in rtcc functions of V4.135 are apparently faulty. At least the unlock function in setup_rtc() and rtc_write() uses a wrong NVMKEY address.

Manual unlock before calling the functions might w ...

It's all about understanding C language and how a C compiler works.

Due to fact that the size of the referenced memory can't be derived from a pointer, you have string functions
with an addition ...

And, for the record, supporting different baud rates on the same modbus is a crazy thing to do.
And surely beyond the scope of the specification.

Regarding the problem in the original post, I unde ...

Missing pull-up/-down resistors on RS485?

The problem behind "recursion not allowed" is that CCS C allocates storage for local variables and function
arguments globally, analyzing the call tree to avoid memory conflicts.

Functi ...

1. I'm convinced that address errors can be traced down to the primary cause, at least if they occur repeatedly.

As Ttelmah mentioned, it might be a silicon bug.

2. I think, the guesses about a ...

Often decimal fixed point numbers with one or two fractional digits are a solution, particularly if they fit a 16 bit variable.

Otherwise rounding and respective format control with float numbers.

total confusion!

- fgetc() result is char not pointer type
- Receivednot printing new[10] or new[0]

Suggestion: Learn quite a bit about C data types, characters, strings, pointers and string fu ...

There's a better way by progamming two input capture modules to use the respective pins, provided
you have it still available in your application.

Firstly I feel tempted to remember that according to previous forum posts, CCS promised to customers
three years ago, that a PIC24 OTG stack would be soon available.

Secondly, if you are working ...

To avoid any overhead, define #BYTE registers

#byte __P1DTCON1L = getenv("SFR:P1DTCON1")
#byte __P1DTCON1H = getenv("SFR:P1DTCON1")+1

Specifying #device ccs4 does not change the behaviour.