TDC7200EVM: Obtaining clean* and stable TDC7200EVM_USB example project

B Lench,

Please explain further, do you need any help with the firmware?

Hi Bharat,

As a matter of fact, could use help with this: (Merged threads below) related issue. You can use the steps above to setup the project, however, the problem (in other thread) arises when I move the source-code into the Project folder.

Thanks.

Part Number: TDC7200EVM

Tool/software: Code Composer Studio

Hi,

I'm trying to incrementally convert a TI example project into the application I need but am encountering obstacles..

I installed example code for the TDC7200EVM, to default destination "C:\Program Files (x86)\Texas Instruments\TDC720xEVM".

I naively unzipped the accompanying example projects into the installation folder, but (after many tweaks) was able to obtain clean compiles and program my device.

However, I need to manage this code outside the example's installation directory and spent many hours trying to move project dependencies, piece-wise, into my workspace. I gave-up when I ran into the SAME error below. However, before that.   

Trying something new, I've copied the (unzipped) example's workspace (TDC720xEVM_Firmware_Source-v2.07\CCS) into a new workspace "workspace_v8" under C:\Users and

moved the source code (from TDC720xEVM_Firmware_Source-v2.07\code\demo_apps\demo2_tdc_usb) into "workspace_v8\TDC7200EVM_USB\Source"

copied all other directories from TDC720xEVM_Firmware_Source-v2.07\code into "workspace_v8\TDC7200EVM_USB\Source\Source"

modified Project\Linked Resources to match new locations

After cleaning-up compiler errors (see notes below) I'm left with:

>> Compilation failure
Source/library/subdir_rules.mk:9: recipe for target 'Source/library/TI_MSP430_spi_USCIA0_5xx.obj' failed
"../Source/library/TI_MSP430_spi_USCIA0_5xx.c", line 51: fatal error #1965: cannot open source file "TI_LMP91400.h"
1 catastrophic error detected in the compilation of "../Source/library/TI_MSP430_spi_USCIA0_5xx.c".
Compilation terminated.
gmake: *** [Source/library/TI_MSP430_spi_USCIA0_5xx.obj] Error 1

The thing is, I've had clean compiles (when project was under installation directory). I can't find "TI_LMP91400.h" anywhere. I don't understand why the compiler thinks it needs to handle the LMP91400,

ANY HELP IS APPRECIATED!

Win 7, Professional, CCS  Version: 8.3.0.00009, MSP430F5529EVM w/TDC7200EVM 

Note to any brave sole(s) who attempts to help:

After creating the new project,

Edit host_interface.c

#include "usb.u"

//extern uint8_t USB_disable(void);

Edit the Project:

Props\Build\MSP430Compiler\ to "include_path="C:/TI/ccsv8/tools/compiler/ti-cgt-msp430_18.1.4.LTS/include/libcxx" --" POINT this to your COMPILER! Fixes missing CSTRING error

Props\Build\MSP430Compiler\Advanced Options\Library Func Assumptions\Level of printf support to FULL; fixes printf compiler errors

Props\Build\MSP430Compiler\Advanced Options\Language Options\Treat C files as C++

After following these steps I was getting clean compiles until I started shifting the location of the source code. After moving the "code" hierarchy into the project's folder and changing the folder name from "code" to Source, I started getting the error described above:

>> Compilation failure
Source/library/subdir_rules.mk:9: recipe for target 'Source/library/TI_MSP430_spi_USCIA0_5xx.obj' failed
"../Source/library/TI_MSP430_spi_USCIA0_5xx.c", line 51: fatal error #1965: cannot open source file "TI_LMP91400.h"
1 catastrophic error detected in the compilation of "../Source/library/TI_MSP430_spi_USCIA0_5xx.c".
Compilation terminated.

There are 10 or so "--include_path" directives in the compiler flags. The order of those flags has changed - could that make a difference?

Hello,

I'm not familiar with this example project.  As you already have a thread with the Sensing team, I'll see if I can help with you linking issues here.  

I don't think the order of linking should matter.  

In your project, are there any paths under your include file that are greyed out?  This usually indicates that are pointing to non-existing paths, like the compiler one you mentioned.  

Thanks,

JD

Hello,

I've merged your two threads together here.  

Thanks,

JD

B Lench,

Please send me your final firmware file that you are trying to compile, please note that these files are only for pointers to the customer to help with their own programming. We typically do not help with program decoding.

Hi Bharat,

I understand and appreciate the offer. However, we changed the project requirement to simply acquire a finite set of measurements to a buffer (2D array), and to send the entire buffer by USB, after acquisition. The acquisition is working!

So now I'm trying to speed-up the post-acquisition USB-transfer by increasing the UART baud rate - however, I have questions about that, I'll start another thread.

Thank you!