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

captivate code size limit

Nandish H S
Expert 1020 points

HI team,

i am facing an while developing prodcuts based on 8KB controllers , if i use captivate GUI design then it generates code based on UART but i am dveloping standalone product where i need to toggel GPIOs based on key pressed so please let me know whether i can develop with less software overhead.

Regards

Nandish

  • 0
    TI__Mastermind 21855 points

    Nandish,

    A lot of the CapTIvate software is built into ROM on the device, to save memory for your custom application.  You can modify the source code that is generated by the CapTIvate design center by loading it into CCS.  Take a look at the Software Library section of the CapTIvate Technology Guide for more information on how to add custom code using the CapTIvate data.

    Mike

  • 0 in reply to Mike Pridgen
    TI__Mastermind 21855 points
    Nandish,

    Did you need any additional information or have any follow up questions? If not, I will close the thread.

    Thanks,
    Mike
  • 0 in reply to Mike Pridgen
    Expert 1020 points

    Hi Mike,

    i need any example code for  one or two key with self mutual code without gui, 

    regards

    Nandish

  • 0 in reply to Nandish H S
    TI__Expert 7530 points

    Hi Nandish,

    It is possible to configure your project with the CapTIvate COMM module disabled, reducing the memory requirements for your design.

    The communications interface is controlled in the CapTIvate Design Center controller customizer (the MCU icon).  If you open up the controller customizer, you can select NONE for the communication interface.  See the informational link below for more detail.  If you re-generate and/or update your source code project based on this change, the CapTIvate COMM module will be complied out and the required code will decrease accordingly.  Alternatively, you could change this directly in the source code by modifying the CAPT_INTERFACE definition in /captivate_config/CAPT_UserConfig.h to be __CAPT_NO_INTERFACE__.  I advise making the change in the Design Center to keep your source code project in sync with the GUI configuration.

    If you are mainly interested in memory size optimization, we also have a code size optimized one-button example for the CapTIvate Development Kit that gets the required size down to about 3kB of FRAM.  This example is available in the CapTIvate Design Center, as well as in the TI Resource Explorer in Code Composer Studio.  It disables the communications features (as discussed above), and also uses more bare-metal configuration functions for things like setting up the clock system in order to save memory.  Wake-on-proximity features are also removed and the CapTIvate top level API is called directly for efficiency.

    Please let Mike and I know if you have further questions, otherwise I hope this addresses your issue!


    Regards,
    Walter

**Attention** This is a public forum