• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 355 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.

CC1310: Reduce code size

David Calabres
Prodigy 125 points

Part Number: CC1310

Hi, im using CC1310F32RMST board and my code use 50KB in flash and 11kB SRAM. I want to reduce the size code for use CC1310F32RSMT. I try to do this:

And too  i remove the predefined simbols. I remove all less PHY_Custom. 

Although it appears in the photo without removing, it is just to show, what I have removed.

 


this actions dont reduce de code. I have to delete .map and debug again for check or what do i do now?
  • 0
    TI__Guru* 87311 points

    You do not say anything regarding which example you are using, which SDK etc., but  asume you are using one of the EasyLink example.

    I took the rfEasyLinkTx example from the 4.20 SDK and built the default example:

    I then removed the following defines:

    SUPPORT_PHY_50KBPS2GFSK
    SUPPORT_PHY_625BPSLRM
    SUPPORT_PHY_5KBPSSLLR

    and built it again:

    As you can see, both FLASH and SRAM usage is decreased. I did not do any changes to the optimization levels from the default example.

    Siri 

  • 0 in reply to Siri
    Prodigy 125 points

    yes, im looking in other file, I reduce TO 36KB but i need reduce to 32KB not? there are something more that i can do? Im using my code, but i edit the simplelink_tx example.

  • +1 in reply to David Calabres
    TI__Guru* 87311 points

    Not easy for me to tell you what you can remove and cannot remove when I do not know what you are doing in your application. 

    Why are you using using the EAsyLink API, for example. Comparing rfEasyLinkTx (just using one PHY) and rfPacketTX, you will see that you save 4-5 k FLASH by not using EasyLink

    Siri

  • +1 in reply to David Calabres
    TI__Guru**** 317180 points

    Also from RF.h:

    "Build configuration
    -------------------

    The RF driver comes in two versions: single-client and multi-client. The
    single-client version allows only one driver instance to access the RF core at
    a time. The multi-client driver version allows concurrent access to the RF
    core with different RF settings. The multi-client driver has a slightly larger
    footprint and is not needed for many proprietary applications. The driver
    version can be selected in the build configuration by linking either against a
    RFCC26XX_singleMode or RFCC26XX_multiMode pre-built library. When using the
    single-client driver, `RF_SINGLEMODE` has to be defined globally in the build
    configuration. The multi-client driver is the default configuration in the
    SimpleLink SDKs."

  • +1 in reply to TER
    Prodigy 125 points

    SIRI:

    I find it much easier to use EasyLink and since I was using a CC1310F128 launchpad I had no problem, now they have changed me to CC13F32 and I have to read the code, but if I can't it is good to know that with rfpackettx it is reduced.
    TER:
    Where can I find what you say, in rf packet or Easylink?
Is it about changing the definition that you say in the .h file?