• State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 21 subscribers
  • Views 6525 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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 Sihan Goi

    I've managed to find the Target page, but code rom size is already set to "Large:64K program", while memory model is set to "Small: variable in DATA". I also managed to find the individual file's optimization settings and set them all to optimize for size, but that didn't buy me a lot either...

    One thing I've noticed is that the EZUSB I2C functions take up a lot of memory. Just by commenting out these functions I save a few hundred bytes. When I then try to uncomment the EZUSB_InitI2C(), it adds like 500+ bytes to the code size. I couldn't find the definition to these library functions either. Will I be forced to do the I2C setup/transfer manually by setting the control registers in order to get it down to size?

Reply
  • 0 in reply to Sihan Goi

    I've managed to find the Target page, but code rom size is already set to "Large:64K program", while memory model is set to "Small: variable in DATA". I also managed to find the individual file's optimization settings and set them all to optimize for size, but that didn't buy me a lot either...

    One thing I've noticed is that the EZUSB I2C functions take up a lot of memory. Just by commenting out these functions I save a few hundred bytes. When I then try to uncomment the EZUSB_InitI2C(), it adds like 500+ bytes to the code size. I couldn't find the definition to these library functions either. Will I be forced to do the I2C setup/transfer manually by setting the control registers in order to get it down to size?

Children