Interesting problem here...

[dc_eng]

Hi,

Here is what happened.

I move the KILLBILL variable to bottom of declarations... works.

Than I move back the KILLBILL variable to middle.... NOT to working.

Than I move KILLBILL variable to top of my declarations... works.

Than I increase KILLBILL variable to array of 50... NOT working.

Than I move increased number of KILLBILLs to bottom... NOT working.

the sym file below NOT working

[dc_eng]

I was keep working on the receiver side since adding just a variable when the transmitter side is fixed causes problems.

One thing come to my mind. What if Receiver can't cope with the data rate when the program length increases.

I do the following I decrease the data rate than the function that does not work starts to work. So, I guess increasing my code by means of functions or variables makes PIC to go different page block. And it makes a slower execution.

But as I remember CCS C do not include variables and functions that doesn't used in code in order to save space.

My sym output file says opposite.

[Wayne_]

Right!
Put KILLBILL as an int in a place it doesn't work.
Change it to an int16, does it work ?
Change it to an int32 does it work ?
Place KILLBILL as an int in a place it works.
Change it to an int16, does it work ?
Change it to an int32 does it work ?

Do not make t an array of 50 chars!
Do not put it at the top or bottom just for the sake of it.

As you move the variable around and change it's size it changes the location and boundary of other vars.
I am trying to find out if the boundary makes a difference.
Also if you move it 1 line at a time you may find out what variable is being moved that causes the problem.

You can start at a place where it works and start moving it up or down until it fails. When it fails you coninue to move it to see if it starts working again. It may work in several places it may not, all this is helpfull info if you show where it works and doesn't work. I don't mean to keep listing the .lst file or complete code each time but just make a note of it and then post the code with comments.

These are just simple ways to try and trace the problem.

If you just move it arbitarily then it doesn't help!

It may not be anything to do with the location of the var at all and this is just a waste of time Have fun.

[dc_eng]

Problem definitely solved.

1) If you have time critical jobs for PIC declare all related variables close each other.

2) Local variables can share same address with other variables that are not related so global declaration (static) helps to organize location of your related variables. Keeps them in same Memory Bank.

With these I can run my code without reducing data rate.

dc

[Wayne_]

Bad practise to rely on your variables being placed in the same memory locations each time you compile.

You should use globals where required and not just because it makes your life easier. Use locals when the info is not required in the calling program and you cannot pass the values back OR you can get a speed increase by using globals.

If your program/pic is struggling at the speed you are using then you should consider a different pic/approach!

It sounds like you have not fixed the problem just hidden it.

[Gabriel]

[Wayne_]