hi...

i am using PSoC3 Cy8Ckit-030 kit....when i am trying to compile my code, i am getting an error as "ADDRESS SPACE OVERFLOW".....can any one please tell me how to rectify it.......

here i am attaching the screen shot of my project workspace showing it..

 looks like RAM issues. Better upload your project for others to check.

yes ....I uploaded my project here.....

If I  make  Line.905 in "EEPROM_Access.c" file as comment then it is working correctly..................If i uncomment it, it is giving error....

When I changed the settings for optimization for your Project I was able to compile it.

BUT

The usage-output of the linker was

Flash used: 41439 of 65536 bytes (63,2%).

which shows that you are VERY near the end of your memory resource.

I did not (yet) go through your code to evolve where some bytes might be saved, but I assure you to do that instantly.

Bob

Check your font.c, all is put into xdata instead of code segment.

Just a suggestion, you have a lot of "M0121:unterminated conditional"

warnings, you might consider cleaning these up first.

Found it out.

You are using "const" to define your data in flash, but this works for PSoC1. Use "CYCODE" instead (to be compatible with PSoC5) and your tables will go into flash.

Happy coding

Bob

I could reduce SRam usage to

SRAM used: 1528 of 8192 bytes (18,7%).

Keil manual shows - 

const 

In ANSI C, the const type qualifier is used to define and access objects that are constant and that may not be changed. A variable that is declared with const may not be assigned to in the program. 

The Cx51 Compiler conforms to the ANSI definition of const objects. 

• Variables declared with the const type qualifier alone are stored in the memory area (data, idata, xdata, and so on) associated with their definition.
  
• Variables you want to locate in ROM must be declared with the code memory type. For example:
  

  
  code char test[] = "This is a text string";
  
      
      
  Variables declared with const far are stored in the HCONST  memory area. This area is typically allocated to ROM memory.
      
  Finally, the STRING compiler directive  specifies where string constants are stored. This directive allows you to place  strings in CODE memory, HCONST memory, or in XCONST memory  (constant space in XDATA).
  

Constant objects are typically initialized when they are defined (in your source files). The following variable definitions show different ways to create constant objects:

Regards, Dana.

 @Bob, @Danaa...

Thank you....SRAM usage is reducing with "CYCODE" data type...

@Danaa.

   I am unable to adress the warnings given by my compiler.....In fact, i am not able to understand what does the warning "Unterminated conditionals" means.......can you please elaborate it.

"Unterminated Conditionals" refer to #if - #endif preprocessor statemens where the #endif is missing, but the included file (normally this is the case) ends.

Bob

I did not see where the typing in the .h file was in error, unless Bob

can find error consider posting a tech case at -

www.cypress.com

“Support”

“Technical Support”

“Create a Case”

Regards, Dana.

I found 3-4 .h files that started as usual with an #ifndef - instruction but where the final #endif was missing.

Easy to see when looking at the very last line of that file where the usual comment is indicated to be part of a block.

Bob

Oh, yes, and inserting a few "return (0);" lines at the appropiate places killed the last 3 warnings.

Happy coding

Bob

If these are Cypress generated poster should file a case to

make sure Cypress fixes.

Regards, Dana.

No, not Cypress's fault, it are Sivananda's .h-files

Bob

 @Bob..

yes, it is absolutely my fault...as you mentioned, i forgot to write "#endif" in 3-4 .h files......Now, it is okay...i Killed all the warnings including return path issues....

@Bob, Danaa....

Thank you..

You are always welcome!

Bob

hi...

     As i mentioned earlier, i am using PSOC3 -CY8C38XX chip which consists of 64 KB flash.....

Now the available 64 KB flash in my chip  is almost full, but still my application code is not completed (still it may need approximately 10 KB)...so, can any one suggest what to do....

Is it possible to interface an external memory to store my application program? If it is, which is the best way to do... so that my code should not break....

here is the current status of my flash

Flash used: 65442 of 65536 bytes (99.9 %).

SRAM used: 1650 of 8192 bytes (20.1 %).