• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 30 subscribers
  • Views 641 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.

RM46L852: SafeTi Library not compiling

Hassan Haroon
Intellectual 830 points
Part Number: RM46L852

I am following the safet ti example. but getting this error

Description Resource Path Location Type
#10010 errors encountered during linking; "i2cirq.out" not built i2cirq C/C++ Problem
<a href="file:/c:/ti/ccsv6/tools/compiler/dmed/HTML/10234.html">#10234-D</a> unresolved symbols remain i2cirq C/C++ Problem
gmake: *** [i2cirq.out] Error 1 i2cirq C/C++ Problem
gmake: Target 'all' not remade because of errors. i2cirq C/C++ Problem
unresolved symbol _SL_Barrier_Data_Access, first referenced in ./source/sl_selftest.obj i2cirq C/C++ Problem
unresolved symbol _SL_Disable_IRQ, first referenced in ./source/sl_selftest.obj i2cirq C/C++ Problem
unresolved symbol _SL_Get_ARM_Mode, first referenced in ./source/sl_selftest.obj i2cirq C/C++ Problem
unresolved symbol _SL_Get_DataFault_Address, first referenced in ./source/sl_selftest.obj i2cirq C/C++ Problem
unresolved symbol _SL_Get_DataFault_Status, first referenced in ./source/sl_selftest.obj i2cirq C/C++ Problem
unresolved symbol _SL_Init_ECCFlash, first referenced in ./source/sl_init.obj i2cirq C/C++ Problem
unresolved symbol _SL_Init_ECCTCMRAM, first referenced in ./source/sl_init.obj i2cirq C/C++ Problem
unresolved symbol _SL_Init_EnableEventExport, first referenced in ./source/sl_init.obj i2cirq C/C++ Problem
unresolved symbol _SL_Kickoff_STC_execution, first referenced in ./source/sl_selftest.obj i2cirq C/C++ Problem
unresolved symbol _SL_Restore_IRQ, first referenced in ./source/sl_selftest.obj i2cirq C/C++ Problem

  • 0
    TI__Guru 59540 points
    Hello Hassan,
    I have forwarded your question to one of our SW leads who should be able to help you work through the errors you are seeing during linking.
  • 0 in reply to Chuck Davenport
    Intellectual 830 points

    Thank you.These errors are removed. The code get compiled.But know i have error something like this .

  • 0 in reply to Hassan Haroon
    TI__Guru 59540 points
    Good to hear, Hassan.

    The "error" that you are seeing now is really just a warning and is, most likely, a result of the execution of the STC LBIST test which resets the CPU when it is done running. This often makes debug difficult because of the loss of breakpoint and other debug configuration information when the CPU resets. To avoid this, it is usually recommended to comment the call to the LBIST execution routine for debug purposes but to re-enable for actual product/application run time.
  • 0 in reply to Chuck Davenport
    Intellectual 830 points
    Thanks alot.You made my life easy..So do i need to comment out this part of code?

    /* Start CPU Self-Test */
    /*********************************************************************************************************/
    /*cpuSelfTest(STC_INTERVAL, STC_MAX_TIMEOUT, TRUE);*/
    stcSelfTestConfig.stcClockDiv = 0; /* STC Clock divider = 1 */
    stcSelfTestConfig.intervalCount = 1; /* One interval only */
    stcSelfTestConfig.restartInterval0 = TRUE; /* Start from interval 0 */
    stcSelfTestConfig.timeoutCounter = 0xFFFFFFFF; /* Timeout counter*/
    _SL_HoldNClear_nError();
    SL_SelfTest_STC(STC_RUN, TRUE, &stcSelfTestConfig);
    /*********************************************************************************************************/
  • 0 in reply to Hassan Haroon
    TI__Guru 59540 points

    Hello Hassan,

    Hassan Haroon said:
    Thanks alot.You made my life easy..So do i need to comment out this part of code?

    /* Start CPU Self-Test */
    /*********************************************************************************************************/
    /*cpuSelfTest(STC_INTERVAL, STC_MAX_TIMEOUT, TRUE);*/
    stcSelfTestConfig.stcClockDiv = 0; /* STC Clock divider = 1 */
    stcSelfTestConfig.intervalCount = 1; /* One interval only */
    stcSelfTestConfig.restartInterval0 = TRUE; /* Start from interval 0 */
    stcSelfTestConfig.timeoutCounter = 0xFFFFFFFF; /* Timeout counter*/
    _SL_HoldNClear_nError();
    SL_SelfTest_STC(STC_RUN, TRUE, &stcSelfTestConfig);
    /*********************************************************************************************************/

    Only the green highlighted function call would need to be commented for debug purposes and then uncommented for production/realtime execution.

    Also, I believe you interval count should be more than 1 (highlighted in blue). Usually there are at least 24 intervals that would need to be ran to get full capability of coverage of the CPUs.

  • 0 in reply to Chuck Davenport
    Intellectual 830 points

    I am not able to run it in debug mode.Its behaving the same by commenting out the green highlighted part.

  • 0 in reply to Hassan Haroon
    TI__Guru 59540 points
    Hassan,

    So you are still seeing the device reset message? Have you enabled ECC and programmed ECC? Do you see the nERROR LED on or are there any codes set in the ESM shadow registers?