TDC7201-ZAX-EVM: TDC7201-ZAX-EVM : the Demo example doesn't. No good response with many posts

Antoine,

I followed the steps in the Use's Guide and got the EVM to work in my lab. I had sent you the same verified register map for your reference, but looks like it does not work in your end.

Incase you connect the signals from the signal generator at START1 & STOP1 and run the GUI, does the INTB pin toggle post the STOP Signal, if yes then the device is able to process the ToF data but we are unable to read it through the GUI. This could be a communication issue and I will check what causing that.

Also when you update the firmware yes you need not connect the TDC7201 EVM since you will have to press the BSL button. Post the firmware update you can hook up the EVM to the LP.

Please add me as a friend in this e2e forum, we can try to setup a call/webex to get you going.

Meanwhile I will merge your previous thread with this thread.

Thank you Bharat for your quick response,

I can't find the INTB pin. Would you mean this pin is on the TDC4201 EVM board?

I try to compile the example with CSS but I have some issues with include folders...

Bests,

Antoine

Hi Bharat,

It seems that INTB1 (or 2) doesn't activated since it stays always HIGH.

About the compilation with CCS the blink demo example works fine.

For the TDC7200EVM_USB project my installation folder is d:/ti and the project was configured at c:\ti\... It was compiled with 36 warnings msg but no error in debug, flashed to the eval board OK too. But in release build there are 42 error msg like : #1965 cannot open source file "cstring". Also for descriptors.h, driverlib.h, etc.. So I add include directories to the project and now still get 15 errors : only "cstring" was not found.

Bests,

Antoine

Antoine,

So you are running this EVM example with the CCS rather than the GUI and you have issues in compiling the code?

Did you try to check if this EVM works fine with the GUI as described in the User's Guide ?

Also I have closed the other thread, please continue this thread for all the issues with the TDC7201-ZAK EVM. 

Hi Bharat,

I finally compile the TDC7200EVM_USB example with success in debug mode by installing the compiler  MSP430 v4.4.8 just get 34 warnings msg . But still have no value read in the GUI application.

Bests,

Antoine

Finally compile in release mode is also OK but still no reading data in GUI app!

Hi Antoine,

I am working with the TDC7201EVM. At one point I too wasn't seeing any measurement in GUI and it was because I forget to supply the Start and Stop signals. ;-)

If you write your own app to communicate with the TDC7200EVM_USB example firmware, just set the Config0 register to 0x02 and then send the "05" command; that will cause the firmware to do a measurement and return the Time, ClockCount and calibration registers (39 bytes). If you send "09", the firmware will reply with its firmware version (32 bytes).

Hope it helps!

Thank you Lench for your response,

I try to send "05" and "09" commands with my Terminal app and it seems to works. My COM port config is : 9600 (or 38400) bauds / 8 bits data / no parity / 1 stop bit / no flow control

How do you set the Config0 register? I can't find it with the GUI. But without this config I receive 32 bytes with the command "09" : the version is 0207 as expected.

nota: I append "05" with "\r\n" before sending to COM port.

Where do you find these commands : "05", "09", etc. ?

When you said that you forget to supply the Start and Stop signals you mean that they were not connected? In my case I have 3.3V from the signal generator and I can see it with my scope

I'll try with the command "05" and the Start-Stop signals...

regards,

Antoine

Hi Antoine,

If you install this example, it comes with a TDC7200EVM_USB example project. Open the project with CCS.  The available firmware commands ("05", "09", and many others) are described in "host_interface.h" and "host_interface.c".  One of the available commands is  "Command_TDC720x_SPI_Byte_Write" "12xxYY" where xx is the register address, and YY is the value being written.  Replace "xx" with "00" to write to CONFIG1, and set "YY" to "02" to enable Measurement mode 2. Note, TDC1 is probably the default, but the "current_tdc" can be selected with command "35".

I'm using the MicroUSB connector on the MSP430F5529 Launch Pad. and connecting to the "TDC7200EVM (COMx)" device in Device Manager.

I'm NOT sending any termination characters (no "\cr\lf")..

I'm using the same (8/1/none) connection settings, but my app sets the baud-rate to 921600.

EDIT: Apparently the USB port runs at 38400, by default, when compiling this example.

Re: "they were not connected?"

Yes, no Start or Stop signals were connected. I now use two separate signals for stop and start, but I _think_ you could use a single pulse for Start and Stop, by using the rising and falling edges of the same pulse. That's settable in the GUI (or set BIT3 and BIT4 of CONFIG1 register). Beware that these signals are 50 ohm terminated so if you connect the same signal to both Start and Stop, it's effectively 25 ohms between signal and ground. My signal-source was not sufficiently capable of driving that load.

Hope it helps,

Bill