• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 209 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.

Original question:

CC2650: BLE-STACK 2.2.3: compilation failure with TI ARM CGT 19.6.0.STS due to change in ltoa() (with patch to fix)

CC2640R2F: ltoa function redefinition causes link time optimization failure

Munan Xu
Expert 4930 points
Part Number: CC2640R2F

Hello,

I have a customer trying to get started on the CC2640R2F Launchpad and we've been having some issues with this change in the ltoa function prototype. Changing the compiler back to 16.9.x does indeed solve the compile time issue as referenced in the related thread, but the customer is also seeing a related link stage error from the function being redefined or provided somewhere else and the function prototypes are incompatible.

We have left the runtime library support to be automatic, but could this potentially be from an incompatible library being included? Shouldn't osal.c override any library implementation of the ltoa function anyways?

Would be good to get a listing either on the project zero tirex page or the CC2640R2F landing page describing the recommended compile chain on these examples at this point if they're not going to be updated to support the latest CGT versions with CCS v10.

Munan

  • 0
    TI__Guru** 101450 points

    HI Munan,

    Generally speaking, you can review the release notes of the specific SDK version you are using. For example, for CC2640R2F SDK 4.30, you will find this in the file simplelink_cc2640r2_sdk_4_30_00_08\release_notes_simplelink_cc2640r2_sdk_4_30_00_08.html.

    As a side note, CCS 10 is not reomended for CC2640R2F devices.

    Best regards,