Search found 21 matches

Thanks PCM

I am still a bit confused.

Can you help on these two specific points?

1. // WRT - Program Memory is Write Protected
// WRTB - Boot block memory write protected

Am I cor ...

I would appreciate it if someone could confirm my understanding of the protection bits.

The following background (and assumptions I have made) may be useful in understanding what I am trying to acc ...

A trick you can use if you want to remain in the "floating point domain" is to add .5 * value of the least sig digit to the value operated on by printf.

Ex:

float x;

x = .03;

p ...

Mr. Kennedy,

I don't know how you determine who you trust, but based on my life experience, trust has to be earned.

For those of you that offerered non-sarcastic responses, thanks again for yo ...

Thanks for your responses. If I move the code around, or even change the order of the declartions, the problem will move to another function (or in a few cases, not occur).

CCS is not interested in ...

In a previous post, I discussed a case where it appeared to me that the compiler was generating incorrect addresses for some of the function calls:
http://www.ccsinfo.com/forum/viewtopic.php?t=41396& ...

Thanks PCM Programmer!

If I understand the data sheet for the 18f8722, there are 2 code protection bits that seem to overlap:

bit 6 CPB: Boot Block Code Protection bit
1 = Boot block (000000-0007FFh) not code-protected ...

Hi,

PCM programmer suggested the org patch, and it fixed one problem, and moved it somewhere else.

I too noticed stange behavior but much over 64K. I am using an 18f8722 with 128k and the proble ...

Hi Monsters_inc.

I too have gotten to the point where I check the listing to make sure that all CALL and RCALL addresses are legal values that have corresponding entries in the symbol table. I have ...

I am seeing something very similar - see post:

http://www.ccsinfo.com/forum/viewtopic.php?t=41396&highlight=

Am I missing something? This seems like a serious problem.

Assume that I am w ...

PCM programmer.

even with the three org statements you recommended to prevent functions spanning 32K boundaries, the problem still happens.

The excerpts below show another example that I capture ...

Thanks.

With the three org statements, the function in question now resolves to the same adrs in all 4 calls. As I mentioned earlier, shifting things around sometimes eliminates the problem or mov ...

No - not using anything special that relocates code, blocks out address ranges, etc. I did not see this behavior when the code occupied a smaller percentage of the total rom space.

Thanks PCM programmer. I know there were some major changes introduced in 4.100.

Tried it on 4.099 - same problem.

Based on the LST info that I posted, does my analysis seem to be correct? Two d ...