• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 270 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.

Original question:

CCS/CC1310: smartrf_settings_predefined confusion

CCS/CC1310: EasyLink_Phy_Custom and sdk_2_40: no data transfer

Orl Nick
Prodigy 150 points
Part Number: CC1310

Tool/software: Code Composer Studio

Hello!

I decided to go from simplelink_cc13x0_sdk_2_30_00_20 to simplelink_cc13x0_sdk_2_40_00_20.

In my working project I copy from sdk_2_40 example rfEasyLinkRx_CC1310_LAUNCHXL_nortos files easylink*, smartrf_settings* and replace files smartrf_settings.* from SmartRF Studio 7 2.12.1.

I get project with (EasyLink_init(&easyLink_params) != EasyLink_Status_Success).

I replace file ".cproject" from sdk_2_40 example (now there are unclear parameters "<listOptionValue builtIn="false" value="SUPPORT_PHY_CUSTOM"/>" )

I get project with (EasyLink_init(&easyLink_params) == EasyLink_Status_Success), but without Packet sending.

What am I doing wrong?

  • 0
    TI__Guru**** 317180 points
    It looks like the configuration of EasyLink has changed from v2.3 and v2.4. In v2.4 of the SDK a EasyLink_config.c/ h file have been added and a predefined symbol has to be added for the PHYs you want to support. Which explains that you had to add SUPPORT_PHY_CUSTOM.

    Not sure why you don't transmit anything though since you should have gotten a compilation/ run time error if you had done something wrong with the update.

    How do you know that a packet is not sending? Is that because you don't receive a packet with a board running easylink code? If that is the case, have you used SmartRF Studio as receiver?

    If you step through the code, does it looks like it send the packet?
  • 0 in reply to TER
    TI__Guru**** 317180 points
    Closing this thread since we haven't received more input.
  • 0 in reply to TER
    TI__Guru**** 317180 points
    I see that you rejected my suggested answer but you haven't come with feedback. Please comment.
  • 0 in reply to TER
    Prodigy 150 points

    I'm sorry.
    I did not receive any compilation errors and warnings when I used the path of SimpleLink ™ Academy 2.40 and there I did not see undocumented compiler options:
    SUPPORT_PHY_CUSTOM,
    SUPPORT_PHY_50KBPS2GFSK,
    SUPPORT_PHY_625BPSLRM
    SUPPORT_PHY_5KBPSSLLR
    Now I see a new CCS 9.0.0.00018 and simplelink_cc13x0_sdk_3_10_00_11.
    I think that dokumuntation does not have time for changes to the CDK and would like to have a clear and precise migration path to the new SDK.