PIC16F690 Lookup Error

[sougata]

Hi,

Please post the compilation errors you are getting.

[RunningMan]

here you go

[sougata]

Hi,

It seems that the code is compiling past the maximum available memory. The warnings should not cause panic. Have you tried using MPASM ?

As large files are compiled and then
assembled, they may start to use more than the first page. As each
page is used, PM, the assembler, will issue a message that the code is
crossing a particular boundary. This is normal and no cause for alarm.
PBP will make sure to take care of most of the issues for you.

However a look at your entire code may give some insight as to why it is crossing the maximum usable prog mem or if it is just a warning.

[RunningMan]

I am compiling using MPASM in Microcode Studio with PBP 2.47

[sougata]

Hi,

I can try compile and tweak if you post your code. What happens if you remove some code (say a subroutine) to test if it compiles okay.

[RunningMan]

Any additional thoughts here? MElabs told me that the tables were basically gobbling up code space and I should try moving stuff around...I tried a couple things and that was to no avail.

[skimask]

Any additional thoughts here? MElabs told me that the tables were basically gobbling up code space and I should try moving stuff around...I tried a couple things and that was to no avail.

Post the code...let's have a look-see...maybe some of us more experienced types might be able to show you something to save some code space or something...