• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 642 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.

CCS/TDC1000-TDC7200EVM: Firmware project for actual Code Composer Studio

Stefan Beetschen
Prodigy 115 points

Part Number: TDC1000-TDC7200EVM
Other Parts Discussed in Thread: TDC7200EVM, TDC7200, TDC1000

Tool/software: Code Composer Studio

Hi

Is there an actual project environment for the TDC1000-TDC7200EVM Evaluation board Firmware?.

I have installed the CCS Version: 9.1.0.00010 and the compiler is TI v4.4.3 [TI v18.12.2LTS]

I imported the Projects "TDC1000_TDC7200EVM", "TDC1000_basic_spi_readwrite" and "TDC7200_basic_spi_readwrite"

When I try to build the "release" of the project "TDC1000_TDC7200EVM" I got a lot of include path related errors.

Is there somewhere a step by step guidance?

Best Stefan

  • 0
    Prodigy 115 points

    Hi

    In the meantime i was able to build the project "TDC1000_TDC7200EVM". I have changed the compiler to TI v18.12.2LTS, changed the compiler switch printf_support=minimal to full, comment out all the include <cstring> and added some include paths. At the moment I can only build the "debug" configuration.

    I am surprised because the size of the new generated outputfile is quite bigger then original size (TDC1000_7200_FW-v2.01-1MHz = 64KB  versus TDC1000_TDC7200EVM = 99KB). After loading the new software (with  BSL_USB_GUI) the Labview - Program seems to work.

    For the "release" configuration I get the message, that the linker can't find some symbols (unsolved symbol ....). I think the library is not a "release"- built. Could that be?

    Is there a better way to solve my problems?

    Best Stefan

  • 0 in reply to Stefan Beetschen
    TI__Genius 11015 points

    Best,

    I have received your question & will get back with you by Monday.

  • 0 in reply to Bharat Aravamudhan
    TI__Genius 11015 points

    Best,

    I am checking with our MSP team to understand the issue that could be caused while using the 2 separate modes and will respond soon as we get it.

    Sorry for the inconvenience.

  • 0 in reply to Bharat Aravamudhan
    TI__Mastermind 30570 points

    Hey Stefan,

    I think this thread linked below explains the difference between the "Debug" and "Release" build configurations.  These two are provided by default, but you can create and customize additional build options if you would like. 

    Switching build configurations may also switch things such as include paths, optimization, and remove symbolic debugging.  If there are libraries that have been included under the debug configuration, it's possible that these include paths also need to be added to the release configuration.     

    https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/21882

    Thanks,

    JD