• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 154 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TDC1000-C2000EVM: Source Code and Binary Files

Gerald
Genius 9575 points
Part Number: TDC1000-C2000EVM
Other Parts Discussed in Thread: TDC1000, TMS320F28035, MSP430F5528

Hi Team,

May I ask for help? I am looking for the binary files and source code of the TDC1000-C2000EVM reference design for our customer. 

I have check this link below:
https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/925670/tdc1000-c2000evm-gui-for-tdc1000-c2000evm

That source code on the link provided is for the GUI which communicates with the TDC1000. I'm after the source code for the TMS320F28035 microcontroller which is on the TDC1000, (U2). Is that available? If yes, can it be shared to our customer? Thank you so much.

Kind regards,
Gerald

  • +1
    TI__Expert 8036 points

    HI Gerald,

    Thank you for your question. 

    Unfortunately, we are no longer able to provide the source code for the TDC1000-C2000EVM.

    We recommend customers utilize the software included with the EVM to develop their custom solution. 

    Regards,

    Jacob

  • 0 in reply to Jacob Nogaj
    TI__Genius 9575 points

    Hi Jacob,

    I got a response from our customer: In that case would it be possible to have the source code for the TDC1000-TDC7200EVM instead please? This is the source code for the MSP430F5528 (U2).

    I hope you can you can further help us.

    Kind regards,
    Gerald

  • +1 in reply to Gerald
    TI__Expert 8036 points

    Hey Gerald,

    Thank you for relaying the response from the customer. I checked with another Engineer to understand if this is something we can share. 

    Unfortunately, we are not able to share this source code to the customer.

    Do you know why the customer is seeking the source code for the microcontroller? Most of the operations for configuring the TDC1000 and managing the output should be detailed in the device datasheet. Additionally, the microcontroller is also performing EVM specific tasks, which would otherwise not be necessary in a custom solution.

    This may be a helpful thread for the customer: Reading and writing to TDC7200. 

    Please let me know if I can support the design process any further. 

    Thank you,

    Jacob

  • 0 in reply to Jacob Nogaj
    TI__Genius 9575 points

    Hi Jacob,

    Thank you so much again for your continuous support. We still got a response from our customer as shown below:

    "I hope this message finds you well. Thank you for your response. The reason for requesting the source code is that we would like to make a custom solution based on your reference design. My client wishes to be able to change the number of pulses from 5 to say 10 for a more accurate measurement, (using averaging). I may be wrong, but I'm not sure if this is something that can be configured externally. Can the number of pulses be changed externally? Also, is it possible to have the binary file instead so that we can program the MSP430 in our own design? We don't want to breach any copyrights you have by the way. Many thanks."

    We hope to received further advise. Thank you.

    Kind regards,
    Gerald

  • +1 in reply to Gerald
    TI__Expert 8036 points

    Hi Gerald,

     

    Thank you for the comments from the customer. The TDC1000 can be programmed vis the CONFIG_0 register to change the number of transmit pulses in a burst, see below for register:

    As for the averaging, this can also be configured in a measurement cycle via the CONFIG_1 register.

    Unfortunately, we are unable to share the binary file.

    In most applications, the TDC1000 will be internally managing the timing and settings for the burst and receive. Therefore, the microcontroller will primarily be for programming and measuring the time between the start and stop pulses. This means it should be relatively easy to implement this into a design from a software standpoint. 

    Please let me know if the customer has any questions,

    Thank you,

    Jacob

  • 0 in reply to Jacob Nogaj
    TI__Genius 9575 points

    Hi Jacob,

    Thank you so much for your detailed response. We will let you know if we need further help. 

    Kind regards,
    Gerald