Search found 62 matches

PIC's store a copy of the FUSES at the "very end" of program memory. PROGRAM_MEMORY returns the start of where those fuses are (so that you don't overwrite them by mistake)

Thanks - for ...

Hex files are in bytes. The program memory words are 14-bits in that PIC and take 2 bytes per word.

Thank you, that makes sense.

I have however, as an experiment, written to the top of program ...

I'm using a PIC16F18445 at the moment. I've used many 18F parts with CCS but I'm struggling to understand the program memory usage with the 16F part.

The 16F18445 has 8k of program memory so up to ...

Thought I would post on the outcome of my optimisation efforts.

Having followed the suggestions from Ttelmah and ckielstra, I managed to save over 20% code space! Shocked

Particular thanks to ckie ...

Ages ago, I posted here, a 'demo' routine showing a more efficient way of doing the arithmetic for this. Cannot remember what the thread was about!. Basically, when you perform an /10, the remainder, ...

A lot of folks here disagree with me on this, but I use floats a lot - makes code much simpler and more readable (maintainable). Yes, there are instances where the speed penalty comes into play, but . ...

138 variations on the same theme sounds like an opportunity for optimization. Take note that pointer arithmetic is using a lot of code space in the PIC processor, so try to avoid passing variables as ...

Here an example on the difference in code size between sprintf and manual coding:

void main()
{
snip
}

Wow Shocked

Thank you very much for doing that - it is like a slap i ...

Thanks ckielstra,

The 32 bit division + multiply requires a lot of code space but this is about as good as it gets. The assembly code you show us is mostly for storing and retrieving the 32-bit par ...

Thanks Ttelmah,

The reason for the small improvement, is that the compiler is already using a generic 'divide' routine in the original code.

Is it likely that I could improve over the generic di ...

Thanks for your reply Pret

With some versions of CCS, (*calib_parameters).oil_flow_rate is better than calib_parameters->oil_flow_rate

I was not aware there was any difference there b ...

I am using a PIC18F4685 but I have a very large program and am short on code space! I'm therefore trying to optimise things a bit.

I have quite a lot of int32 multiplies followed by divides to do ...

For my solution,.. I move my target boards VID/PID to 0856/AC01. while doing test and debug.
Then change it to my assinged VID/PID when in production.

Cracking idea Treitmey Very Happy

- now why di ...

Sergio, did you get anywhere with this?

It is true, CCS does not play nicely when other FTDI devices are plugges in - it is pretty poor really - I have been putting up with it for over a year now and just checked on here today to see if the ...