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.
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.
To me an external EEPROM is the way to go to store Lookup tables.
As long as your value range<127, you could also use MPASM da
If you're using tons of Text string in your code, there's different way to shrink it as well.
Post your code here, maybe we can see something to improve.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi,
I guess that this is a commercial project and you cannot post it publicly. However without the code it is difficult to give any pointer's. May be Steve's crystal ball can do something!![]()
Regards
Sougata
Hi, Runningman
Something interesting would be co compile with 4 tables and have a look to the MPLAB Program Window, to find WHERE the tables are located / pages beginnings in the Hex file ...
That could enlighten the reason Why ....
Just a small idea ... !!!
Alain ... Great "RTLW" user ( in assembler only !!! )
PS: "RTLW" is your solution also ...
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Bookmarks