• State
  • Replies 7 replies
  • Subscribers 79 subscribers
  • Views 152 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

CCS/MSP430FR2633: Warning: compression "lzss" is ignored

MSP430FR2532: warning during compilation: output section ".data" refers to load symbol "$C$SL1"

Zhiyong Li (FT)
Expert 2920 points
Part Number: MSP430FR2532
Other Parts Discussed in Thread: MSP430FR2433, UNIFLASH

Tool/software:

Hi,

I am trying to revise a project that has not been touched for a few years, and noticed a warning/error after compilation with TI v21.6.1 LTS in CCS12.8.1:

warning #10229-D: output section ".data" refers to load symbol "$C$SL1" and hence cannot be compressed; compression "lzss" is ignored

If I try to check the memory allocation, I see the following, that indicates compilation has failed.

If I try to compile with TI v16.9.11 LTS, I get the same warning messing, but the compiled binary file can be loaded into MCU and run.

I recently worked on a very similar project that uses MSP430FR2433, didn't run into such issues. I also read several related posts on the forum but unfortunately I still don't have a clue how to use TI v21.6.1 LTS to successfully compile the project.

Update: it seems only CCS v7.x can reliably compile a running image with the code base. In newer CCS like v12.8, if I ever try to change compiler version to a newer version then switch back to v16.9.11, compilation will fail.

Thanks,

ZL

  • 0
    TI__Genius 15732 points

    Hi ZL,
    Can you try compiling the code using the latest CCS release, i.e., CCS  20.3.0, and see if the error persists? Also, can you check if you can check the device's memory using UNIFLASH?
    Best Regards,
    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Expert 2920 points

    Hi Mr. Abad,

    I just tried to compile the project in CCS v20.3.0, either let compiler fall back to v21.6.1 and explicitly choose it. I was able to successfully compile and then load the binary image into MCU with Uniflash. The image also seems to run as expected.

    I still see the warning message in CCS v20.3.0:

    [168]<Linking>
[169]warning #10229-D: output section ".data" refers to load symbol "$C$SL1" and hence cannot be compressed; compression "lzss" is ignored

    Regarding memory, I can see memory allocation in CCS that almost all FRAM is being used, 7526/8064 to be exact. I thought that could be the issue, but I get the same warning if I switch the target to MSP430FR2433 which has 16KB FRAM.

    Regards,

    ZL

  • 0 in reply to Zhiyong Li (FT)
    TI__Genius 15732 points

    Hi ZL,
    I found this E2E thread that should explain a little in detail on what this error means.

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Expert 2920 points

    Hi Mr. Abad,

    The closest to _nop() in our code base is __delay_cycles(). But I am still getting the warning message after commenting out those lines of __delay_cycles().

    My question is, should I be concerned about such warning message? Some warning messages in the past did reveal other more serious, sometimes possible fatal, issues. I want to make this one is not among those if I cannot completely get rid of it.

    Thanks,

    ZL

  • 0 in reply to Zhiyong Li (FT)
    TI__Genius 15732 points

    Hi ZL,
    The error itself shouldn't generate an issue since it only mentions that compression is not happening. Maybe modifying the linker file could help, but I don't think should affect functionality.

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Expert 2920 points

    Hi Mr. Abad,

    Since I have your attention, could you please explain why CCS v12.8 failed to compile with TI v21.6.1 compiler? This is what alarmed me. I can live with the warning message as long as it doesn't affect functionality. But I want to rule out more serious issues.

    Thanks,

    ZL

  • 0 in reply to Zhiyong Li (FT)
    TI__Genius 15732 points

    Hi ZL,
    Since CCS v12.8 is based on the Eclipse IDE, it is likely that TI V21.6.1 may not be fully supported, as we are transitioning to the Theia IDE. The previous could lead to some behaviors like the one you are seeing.
    Best Regards,
    Diego Abad

**Attention** This is a public forum