• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 239 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.

RTOS: How to eliminate this warning

jinjinjin
Intellectual 480 points
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

Since DSP1_RST_VECT of CTRL_CORE_CONTROL_DSP1_RST_VECT can only fill 22 bits, I specified this specific address.

I want to know how to eliminate this warning and whether this warning has an impact on the software.

  • 0
    TI__Guru 55685 points
    Hi,

    _c_int00 is a symbol and not a section.
    Symbols should be assigned using "=".

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 480 points
    Hi,

    using "=" is error.
    replace ">" with ">>" will be eliminate this warning.

    There is still a problem here.

    In the sysbios project, when I rebuild project or clean project, I had to re-add this sentence to the link script to specify _c_int00 to a specific address. Is there any other way that will not be deleted when rebuild project or clean project?

    Regards.
  • 0 in reply to jinjinjin
    TI__Guru*** 125430 points

    valvalvalval said:
    replace ">" with ">>" will be eliminate this warning.

    Correct.  FYI, that's mentioned here:

    http://processors.wiki.ti.com/index.php/Accessing_c_int00#Using_SYS.2FBIOS

    valvalvalval said:
    In the sysbios project, when I rebuild project or clean project, I had to re-add this sentence to the link script to specify _c_int00 to a specific address. Is there any other way that will not be deleted when rebuild project or clean project?

    You can have more than one *.cmd file associated with your project.  Instead of making the change in the *.cmd generated by sysbios, just create your own *.cmd and put the definition there.