• State TI Thinks Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 2 answers
  • Subscribers 83 subscribers
  • Views 843 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.

TMDSCNCD280039C: TMDSCNCD280039C

Shashank Mathur
Prodigy 60 points
Part Number: TMDSCNCD280039C
Other Parts Discussed in Thread: TMDSHSECDOCK, CONTROLSUITE, C2000WARE

I am getting started on using board TMDSCNCD280039C which has F280039CSPZ, mounted on the controlCARD docking station TMDSHSECDOCK, and I wanted to see if there are example project and instructions to start using the board

If your response in email may include steps to setup the project (say a blinking LED project) into CCS, that would be very helpful. 

Which version of CCS and controlSUITE to use with board TMDSCNCD280039C?

  • 0
    TI__Guru 50611 points

    Hi,

    Please download latest version of C2000Ware from https://www.ti.com/tool/C2000WARE

    Once you install the SDK on your system, the examples can be found at

    C:/ti/c2000/C2000Ware_4_00_00_00/driverlib/f28003x/examples

    There is also online C2000 Academy, which you can use to get started with the device:

    https://dev.ti.com/tirex/explore/node?node=AOpze8ebskysmgASY3VKSA__jEBbtmC__LATEST

  • 0 in reply to Santosh Jha
    Prodigy 60 points

    Thanks for your response. However, I am still not ready to get started with using the board. In the C2000Ware example file, I can only see .c file and a project spec file under 'CCS' folder which I am not sure how to begin using with. Also, when I try to open a new CCS Project using CCS v11.1, I get the below error message trying to verify connection with board TMDSCNCD280039C. (I selected XDS100v2 USB Debug Probe)

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-151' (0xffffff69).
    The title is 'SC_ERR_FTDI_OPEN'.

    The explanation is:
    One of the FTDI driver functions used during the connect
    returned bad status or an error. The cause may be one or
    more of: no XDS100 is plugged in, invalid XDS100 serial number,
    blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
    Use the xds100serial command-line utility in the 'common/uscif'
    folder to verify the XDS100 can be located.

    [End]

     Ideally, a step by step procedure to execute an example project with proper connection to board would be helpful. 

  • 0 in reply to Shashank Mathur
    TI__Guru 50611 points

    Shashank,

    Did you try the link I gave you earlier for C2000 Academy. Module2 of the Academy walks through the steps. 

    Here is the link which walk through the step by step how to get started.

    https://dev.ti.com/tirex/explore/node?node=ASrjG01hPgRfzY1a74A0Yg__jEBbtmC__LATEST

    Also, iIf you are using controlCARD then n your project target configuration, you will need to use xds110, not xds100v2

  • 0 in reply to Santosh Jha
    Prodigy 60 points

    Hi Santosh,

    xds110 worked. Thanks. I have done upto module 6, now on module 7, and on running the code, I saw some propagating noise in the PWM. Can you help me understand the reason behind this? How to solve this? 

  • 0 in reply to Shashank Mathur
    TI__Guru 50611 points

    Shashank,

    I will take a look later today and get back to you.

  • 0 in reply to Santosh Jha
    TI__Guru 50611 points

    Hi Shashank,

    There is a solution to the lab exercise in C2000Ware SDK. Can you import the project and check if you are getting the clean the plot?

    I just tried on my setup and I am getting the clean plot as shown below.

    The solution is provided at:

    C:/ti/c2000/C2000Ware_4_01_00_00/training/device/f28003x/module7_control_peripherals

  • 0 in reply to Santosh Jha
    Prodigy 60 points

    Hi Santosh, 
    Upon importing the project from solution link, I now see clean plot as expected. Thanks, what may be reason for the noise earlier? Also, a follow up question is on the Graph window in CCS the time period is 500us as expected, but when I connected the  EPWM1A Pin to actual oscilloscope, the time period is only 417us and I am not sure why. The amplitude is 3.3V, which I think is correct. 

  • 0 in reply to Shashank Mathur
    TI__Guru 50611 points

    Shashank,

    Can you compare the solution and the project you created manually and see what is the difference in the two?  If you find any gap in instruction, please let us know and we will fix that in next release.

  • 0 in reply to Santosh Jha
    Prodigy 60 points

    Santosh,

    Ok, I will check difference in both. Any suggestions on the second question above? Thanks.  

  • 0 in reply to Shashank Mathur
    TI__Guru 50611 points

    Shashank,

    The calculation in the instruction is assuming cpu is running at 100 MHz. But F280039C is running at 120 MHz. You can use the calculation in the instruction for 120 MHz.

    #define PWM_HALF_PERIOD 30000   // For 2kHz PWM waveform.
#define PWM_MIN_DUTY 28500      // 5% duty cycle.
#define PWM_MAX_DUTY 1500       // 95% duty cycle.
#define ADC_SAMPLE_PERIOD 2399  // For 50kHz sampling rate.

uint16_t AdcBuf[50];            // Buffer to store ADC samples.
uint16_t *AdcBufPtr = AdcBuf;   // Pointer to ADC buffer samples.
uint16_t LedCtr = 0;            // Counter to slow down LED toggle to 1Hz.
uint32_t PwmDuty = 22500;       // Default is 25% duty cycle.
uint16_t DutyModOn = 0;         // Flag to turn on/off duty cycle modulation.
uint16_t DutyModDir = 0;        // State of the duty modulation up/down.
uint16_t DutyModCtr = 0;        // Counter to slow down duty modulation.
int32_t eCapPwmDuty;            // Percent = eCapPwmDuty/eCapPwmPeriod*100.
int32_t eCapPwmPeriod;          // Frequency = DEVICE_SYSCLK_FREQ/eCapPwmPeriod.

  • 0 in reply to Santosh Jha
    Prodigy 60 points

    Hi Santosh, 
    Thanks that modification worked. If I need to generate another PWM simultaneously, is there an example I can refer to? Also, in ccs, what settings are required to keep the code after power if turned off so it runs as soon as its powered again?  

  • 0 in reply to Shashank Mathur
    TI__Guru 50611 points

    Shashank,

    Please take a look at DriverLib example for ePWM and also check build configuration CPU1_FLASH for standalone booting. Create. a new thread if you are having issue so that it can go to right subject matter expert.