• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 4530 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS: Warning : ignoring #pragma PERSISTENT [-Wunknown-pragmas]

seogje cho
Prodigy 110 points
Other Parts Discussed in Thread: MSP430FR6989

Tool/software: Code Composer Studio

Hello!

My program worked in CCSV6 with TI compiler option(TI v15.12.3.LTS). After changing the compiler option from TI to GNU(GNU v5.3.0.244). I met a lot of warning message. One warning message is "ignoring #pragma PERSISTENT [-Wunknown-pragmas]" The target device is MSP430FR6989. The variable will be written to FRAM.
Header file is
" #pragma PERSISTENT (fram_write_mark)
UBYTE fram _write_mark= 0;".
How can I resolve it? Your help is very appreciated.

  • 0
    TI__Guru**** 244280 points

    seogje cho said:
    How can I resolve it?

    Unfortunately, there is no solution in this case.  The MSP430 gcc compiler has no mechanism by which you can get the same functionality as the TI compiler #pragma PERSISTENT.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 110 points
    Hello George!

    Thank you for your reply. I understand that there is no replacement of "#pragma PERSISTENT" for MSP430 GCC compiler.
    But, I read some manual. At the moment, I don't know exactly which manual I read. Using the instruction of it, I have changed my header file as follow.

    typedef unsigned char UBYTE;
    #if defined(__TI_COMPILER_VERSION__)
    #pragma PERSISTENT (fram_write_mark)
    UBYTE fram_write_mark = 0;
    #elif define(__GNUC__)
    UBYTE fram_write_mark __attribute__((persistent)) = 0;
    #else
    #error Compiler not supported!
    #endif

    In this case, there is no warning message like "ignoring #pragma PERSISTENT[-Wunknown-pragmas]"
    but I met another error message.
    The message is
    section '.text will not fit in region 'ROM'
    section __interrupt_vector_40 loaded at [0000ffde,0000ffdf] overlaps section .text loaded at [00004904,000110db]
    region 'ROM' overflowed by 4444 bytes

    your comments are very helpful.

    Thanks & Regards,

    Seogje Cho,
  • 0 in reply to George Mock
    TI__Guru**** 244280 points

    I apologize.  I was wrong when I said ...

    George Mock said:
    The MSP430 gcc compiler has no mechanism by which you can get the same functionality as the TI compiler #pragma PERSISTENT.

    I searched again, and found the documentation for all the MSP430 variable attributes, including persistent.

    Thanks and regards,

    -George

  • 0 in reply to seogje cho
    TI__Guru**** 244280 points

    seogje cho said:
    but I met another error message.
    The message is
    section '.text will not fit in region 'ROM'
    section __interrupt_vector_40 loaded at [0000ffde,0000ffdf] overlaps section .text loaded at [00004904,000110db]
    region 'ROM' overflowed by 4444 bytes

    This usually means your program is too big for your device.  I cannot give more specific advice, because that requires detailed knowledge of your device and the linker script you use.  That linker script probably comes from TI, though not the compiler team that monitors this forum.  Those experts are over in the MSP device forum.  I recommend you start a new thread there.  Or, if you prefer, I can move this thread to that forum.

    Thanks and regards,

    -George