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
↧