• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 379 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.

Partial build of ez430-chronos for limited CCS edition

Filip Wahlberg
Prodigy 10 points

Hi! I am successfully using CCS Core edition for editing and compiling source code in the ez430-chronos suite.

Using the limited build configuration, all source files in the "driver" folder are marked as "Excluded from Build", and the pre-compiled library "ez430_chronos_drivers.lib" is included, in order to keep source code size within limits.

My problem is that I need to tweak one of the "driver" files, namely "timer.c". Simply removing the "Excluded from Build" tag for "timer.c" lets me compile without warnings so obviously the code is still within size limits, but my changes are ignored when I run the code probably because the object code from the pre-compiled library is used. Can I tell the linker to use my new object file (timer.obj) and let its functions override "ez430_chronos_drivers.lib"?

/Filip

  • TI__Guru**** 171839 points

    Filip,

    By default in CCSv4 the object files are linked before the libraries, therefore any functions defined in source files will take precedence over the libraries.

    In you case the default behaviour would be <timer.obj> be linked before <ez430_chronos_drivers.lib>.

    Therefore, to have a better idea on what may be happening in your case could you please send additional information?

    - copy and paste the contents of the console window when the linker is called. This will help seeing how the parameters are being passed to the linker;

    - send the .map file generated. This way we will have an idea if <timer.obj> is being correctly included in the .out file.

    Thanks,

    Rafael