• State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 22 subscribers
  • Views 6568 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Errors and warnings when compiling

Sihan Goi

Hi,
I'm programming for a Cypress EZ-USB FX2 platform, and I'm adding onto the default firmware. I'm having some problems compiling some code, and I'm wondering if I'm running into space limitations already.

First of all, I get warnings when I try to initialize the I2C interface by calling

EZUSB_InitI2C();

I get the warning message

*** WARNING L16: UNCALLED FUNCTION, IGNORED FOR OVERLAY PROCESS
    NAME:    _EZUSB_WAITFOREEPROMWRITE/I2C
*** WARNING L16: UNCALLED FUNCTION, IGNORED FOR OVERLAY PROCESS
    NAME:    _EZUSB_WRITEI2C_?I2C
*** WARNING L16: UNCALLED FUNCTION, IGNORED FOR OVERLAY PROCESS
    NAME:    _EZUSB_READI2C_?I2C
Program Size: data=112.4 xdata=6830 const=216 code=8870

Next, when I try to add in another for loop as below

   for (i=0;i<16;i++)
      EZUSB_ReadI2C(ZTBL_ADDR+i, 0x01, z_table[i]);


I am unable to compile. I get the following error messages on top of the warning message

*** ERROR L107: ADDRESS SPACE OVERFLOW
    SPACE:   CODE
    SEGMENT: ?L?COM001A
    LENGTH:  00000BH
*** ERROR L107: ADDRESS SPACE OVERFLOW
    SPACE:   CODE
    SEGMENT: ?L?COM0022
    LENGTH:  000009H
*** ERROR L138: CODE GENERATION: PROBLEM WHEN PROCESSING INSTRUCTIONS
    CAUSE:   JUMP TARGET OUT OF RANGE
    ADDRESS: 0750H
*** ERROR L138: CODE GENERATION: PROBLEM WHEN PROCESSING INSTRUCTIONS
    CAUSE:   JUMP TARGET OUT OF RANGE
    ADDRESS: 0761H
*** ERROR L138: CODE GENERATION: PROBLEM WHEN PROCESSING INSTRUCTIONS
    CAUSE:   JUMP TARGET OUT OF RANGE
    ADDRESS: 0785H
*** ERROR L138: CODE GENERATION: PROBLEM WHEN PROCESSING INSTRUCTIONS
    CAUSE:   JUMP TARGET OUT OF RANGE
    ADDRESS: 07B0H
Program Size: data=112.4 xdata=6830 const=216 code=8993
Target not created

Have I run out of space already?

Thanks!

Parents
  • 0 in reply to Andy Neil

    OK, I've read the online help regarding code size, and LARGE seems to simply mean that all available space is used, up to 64K, assuming the chip supports 64KB. Since my chip only has 16K, of which only 8K is used for code space, I'm pretty much limited to 8K, which means I pretty much have to find a way to stick within that limit...gonna be tough since the default firmware already takes up 6+K, and just calling the EZUSB_InitI2C() function is already 500 bytes...

    I've looked at the examples, they show how to use the uvision3 IDE. I have uvision2 instead, and while I've not used uvision before, I have used other IDEs, so I'm picking up along the way. I don't think I need a "Hello World" example to learn the IDE.

Reply
  • 0 in reply to Andy Neil

    OK, I've read the online help regarding code size, and LARGE seems to simply mean that all available space is used, up to 64K, assuming the chip supports 64KB. Since my chip only has 16K, of which only 8K is used for code space, I'm pretty much limited to 8K, which means I pretty much have to find a way to stick within that limit...gonna be tough since the default firmware already takes up 6+K, and just calling the EZUSB_InitI2C() function is already 500 bytes...

    I've looked at the examples, they show how to use the uvision3 IDE. I have uvision2 instead, and while I've not used uvision before, I have used other IDEs, so I'm picking up along the way. I don't think I need a "Hello World" example to learn the IDE.

Children