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/LAUNCHXL-CC2640R2: AoA error

Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: UNIFLASH, CC2640R2F, CC2642R, LAUNCHXL-CC26X2R1

Tool/software: Code Composer Studio

Hello,

we have a customer with a concern as below:

Conducting AoA by rtls_master, rtls_slave and rtls_passive.
First Case:- Using simplelink_cc13x2_26x2_sdk_4_30_00_54 with CCSv10.1.1. When try to load the sample code of rtls_master and rtls_slave it gave me this error:
" Cortex_M4_0: File Loader: Memory write failed: Timed out waiting for target flashloader to execute command.
Cortex_M4_0: GEL: File: C:\Users\ANAMUL HAQUE SOHEL\workspace_v10\rtls_master_CC26X2R1_LAUNCHXL_tirtos_ccs\Debug\rtls_master_CC26X2R1_LAUNCHXL_tirtos_ccs.out: Load failed."
Gave the details in attached file.

Second Case::- Using simplelink_cc2640r2_sdk_3_10_00_15 with CCSv10.1.1 and CCSv9. The rtls_master and rtls_slave sample code gave error at building. Error:
"gmake: Target 'all' not remade because of errors.
Description Resource Path Location Type
#20 identifier "__int8_t" is undefined .ccsproject /rtls_master_cc2640r2lp_app line 37, external location: C:\ti\ti-cgt-arm_18.12.5.LTS\include\sys\_stdint.h C/C++ Problem
#20 identifier "__int8_t" is undefined .ccsproject /rtls_master_cc2640r2lp_app line 88, external location: C:\ti\ti-cgt-arm_18.12.5.LTS\include\machine\_types.h C/C++ Problem
#66 expected a ";" AOA.c /rtls_master_cc2640r2lp_app/Drivers/AOA line 4 C/C++ Problem
gmake: *** [Drivers/AOA/AOA.obj] Error 1 rtls_master_cc2640r2lp_app C/C++ Problem
gmake: Target 'all' not remade because of errors. rtls_master_cc2640r2lp_app C/C++ Problem"

Third Case:- Using hex file of rtls_master.hex in UniFlash but RTLS UI could not Detect the device. I used xdsdfu.exe for changing the firmware version but unable to do it.


Regards,

Roland

  • Hi Roland,

    Roland Melad said:
    Conducting AoA by rtls_master, rtls_slave and rtls_passive.
    First Case:- Using simplelink_cc13x2_26x2_sdk_4_30_00_54 with CCSv10.1.1. When try to load the sample code of rtls_master and rtls_slave it gave me this error:
    " Cortex_M4_0: File Loader: Memory write failed: Timed out waiting for target flashloader to execute command.
    Cortex_M4_0: GEL: File: C:\Users\ANAMUL HAQUE SOHEL\workspace_v10\rtls_master_CC26X2R1_LAUNCHXL_tirtos_ccs\Debug\rtls_master_CC26X2R1_LAUNCHXL_tirtos_ccs.out: Load failed."
    Gave the details in attached file.

    Please see YiKai and Clement's replies in the below thread:

    https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/931476

    Roland Melad said:
    Second Case::- Using simplelink_cc2640r2_sdk_3_10_00_15 with CCSv10.1.1 and CCSv9. The rtls_master and rtls_slave sample code gave error at building. Error:
    "gmake: Target 'all' not remade because of errors.
    Description Resource Path Location Type
    #20 identifier "__int8_t" is undefined .ccsproject /rtls_master_cc2640r2lp_app line 37, external location: C:\ti\ti-cgt-arm_18.12.5.LTS\include\sys\_stdint.h C/C++ Problem
    #20 identifier "__int8_t" is undefined .ccsproject /rtls_master_cc2640r2lp_app line 88, external location: C:\ti\ti-cgt-arm_18.12.5.LTS\include\machine\_types.h C/C++ Problem
    #66 expected a ";" AOA.c /rtls_master_cc2640r2lp_app/Drivers/AOA line 4 C/C++ Problem
    gmake: *** [Drivers/AOA/AOA.obj] Error 1 rtls_master_cc2640r2lp_app C/C++ Problem
    gmake: Target 'all' not remade because of errors. rtls_master_cc2640r2lp_app C/C++ Problem"

    The SDK versions can be tied to CCS versions. v3.10 of the SDK is quite and likely validated with an older CCS version. I suggest updating to the current version of the SDK.

    Roland Melad said:
    Third Case:- Using hex file of rtls_master.hex in UniFlash but RTLS UI could not Detect the device. I used xdsdfu.exe for changing the firmware version but unable to do it.

    Are you able to connect to the launchpad via CCS?

    Thanks

    ki

  • Roland Melad said:
    C:\Users\ANAMUL HAQUE SOHEL\workspace_v10\rtls_master_CC26X2R1_LAUNCHXL_tirtos_ccs\Debug\rtls_master_CC26X2R1_LAUNCHXL_tirtos_ccs.out: Load failed."

    Also please note that whitespaces in the path can often cause build issues

  • Hi,

    I know that I need to use simplelink_cc2640r2_sdk instead of simplelink_cc13x2_26x2_sdk.

    Since in simplelink_cc2640r2_sdk_4_30_00_08 (latest version) the rtls_master and retls_slave project doesn't exist so I have use simplelink_cc2640r2_sdk_3_10_00_15.

    I also know that this simplelink_cc2640r2_sdk_3_10_00_15 version works with older versions of CCS.

    I checked rtls_master and rtls_slave project in CCSv10, CCSv9, and CCSv8 and each of these versions gave me errors at building.

  • I tried building the same examples from SDK 3.10.00.15 with CCS 10.1.1. It built without error. I'm not sure what the issue is with your environment. I will bring this thread to the attention of the device experts. They will be more familiar with the SDK example

    Thanks

    ki

  • Hi Ali,

    I will help you through the resolution to your issue. Before that, I wanted to be sure you are aware that we recommend using CC2642R device instead of CC2640R2F device for AoA.

    TI has made the decision to discontinue further development and support of the TI-proprietary Angle of Arrival (AoA) on the CC2640R2. We recommend and welcome our customers using AoA on CC2640R2 to transition from the CC2640R2 to the new RTLS examples based on the Bluetooth 5.1 specification which can be used with the CC13x2R and CC26x2R devices. These software examples can be found in the SimpleLink™ CC13x2 and CC26x2 software development kit 3.40 or later which features a Bluetooth 5.1 qualified stack with support of Bluetooth 5.1 Angle of Arrival. To make this transition, here is a list of available resources you can reference: Simple Link Academy, AoA stack users guide, LaunchPad Tool Order Page

    For the rest, could you please specify which issues are currently remaining?

    Thanks and regards,

  • Hi Clement,

    Thanks for your quick reply.

    So, with this condition, we can't implement AOA on CC2640R2 devices?

    Because we have bought two months ago 5 CC2640R2s for implementing Angle of arrival with them, and now we couldn't use the sample link SDK.

    If I well understand, the Angle of arrival feature on Bluetooth 5.1, is not supported by CC2640R2, am I right? Or this transition is only du to discontinue further support from TI technical part on AoA on the CC2640R2?

    Best Regards,

    //Ali

  • Hi Ali,

    Bluetooth 5.1 compliant AoA has never been supported on CC2640R2F. Only proprietary AoA was supported on CC2640R2F.
    For evaluation, you can still use the code provided for CC2640R2F in older SDKs. That being said, I strongly discourage you to use this code to go to production.

    I recommend you to migrate to CC2642R1 (use LAUNCHXL-CC26X2R1). This will allow you to leverage all the new features and tools we have developed.

    Best regards,

  • Hi Clément

    Since we brought CC2640R2F two months ago, we have no option buy CC2642R. We need work with CC2640R2F. I am finaly able to solve the building error of the SDK, now rtls_master and rtls_slave sample code are working fine.

    Then I tried rtlsui.exe from rtls_agent folder in simplelink_cc13x2_26x2_sdk_4_30_00_54. The rtlsui.exe is detecting the rtls_master and rtls_slave devices but when performing the AoA calculation its given me error. I looked at some quarries and I found I need to close the CCS then run RTLSUI.exe. I did this, still get this error.

    RTLS Ul Error
    Dont panic, some exception occur in server while performing last action.
    How to solve it? start with dismissing this message, try each solution one at a
    time.
    Try last action again
    Press on Restart and start over
    No one of the solutions above didnt help restart the application serve

    Best Regards,

    //Ali

  • Hi Ali,

    The issue you are experiencing with the GUI is due to the fact you are using a GUI version that is not compatible with your code / HW. There is nothing that you and I can do to get the GUI working with CC2640R2F. Exactly like there is nothing you and I can do to have a BLE5.1 compliant AOA implementation on CC2640R2F. From a technical point of view, I cannot do more.

    If the the price of the HW is a problem, I remind you that you only need two LAUNCHXL-CC26X2R1 for the evaluation. The same BOOSTXL-AOA can still be used.

    Best regards,