• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1071 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

With TI-RTOS 2.13.1.09, CCS compiler error, CC2640, 5x5, when recompiling the Stack I get an error : undefined symbol TimerElapsed, first referenced in file ./OSAL/OSAL_Timers.obj. Previous version of RTOS compiled OK. Any clues?

Luiz Barros
Prodigy 40 points
Other Parts Discussed in Thread: CC2640, CC2650STK

With TI-RTOS 2.13.1.09, CCS compiler error,  CC2640, 5x5, when recompiling the Stack I get an error :  undefined symbol TimerElapsed, first referenced in file ./OSAL/OSAL_Timers.obj. Previous version of RTOS compiled OK. Any clues?

  • 0
    Prodigy 40 points
    I found that TimerElapsed is only referenced within osal_adjust_timers( void ). There is no references to this function in the whole project. I commented out osal_adjust_timers() and it compiled OK.
  • 0 in reply to Luiz Barros
    TI__Guru** 105180 points
    Thanks for letting us know.

    Best wishes
  • 0 in reply to JXS
    Expert 1790 points
    BLE SDK 2.02.00.31 this issue still exists. With optimization O5 (whole program), the issue is not manifest, but with O0 (no optimization) it does. If you consider this a problem in the linker (If there are no calls to the function, why would the linker try to resolve it?) I am using TI ARM complier v5.2.7. Easy enough to work around.
  • 0 in reply to lloyd konneker
    Expert 1180 points
    This problem was giving my the error DWARF information is corrupted for stack.out when I tried to debug using optimization O5. It build with no errors. I only saw a problem when trying to upload it to my target when I would get the corrupted stack.out error.

    It wasn't until I dropped down the optimization level that I realized there was still that same error that I had when setting this up a year ago. Only this time it gave me a much different much more misleading error.
  • 0 in reply to Peyton Davari
    Prodigy 135 points

    Confirmed I'm encountering this same error .. exhibited as a DWARF corruption when trying to flash the stock `sensortag_cc2650stk_stack` build with O5 optimization. Once I followed instructions here and dropped to O0 optimization I got the `TimerElapsed` undefined symbol linking error. I then commented out the entire `osal_adjust_timers()` function body and was able to rebuild and load without issue.