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/TMS320F28335: TMS320F28335

Part Number: TMS320F28335
Other Parts Discussed in Thread: TMDSDOCK28335, C2000WARE

Tool/software: Code Composer Studio

ahello, i need to ask about hardware setting

i am using tms320f2835 customized board and to startup i just build and debug the one of the exmple given in C2000 about gpio_toggle

but when i build and debug the code everything works fine with ccs but i didn't saw anything across any Gpio pins on the oscilliscope.

what might be the problem i ave with some other examples as well. 

  • Muhammad,

    this is a custom board that you have developed, correct? Have you ever ran this code on a controlCARD? http://www.ti.com/tool/TMDSDOCK28335

    When you attempt to load the GPIO toggle code to the F28335 device, do you receive any errors?

    1. Have you begun executing the code?
    2. Is the device powered?
    3. What is the state of the XRSn line?
    4. Have you provided a clock to the device?

    Regards,
    Cody 

  • I didn't run the code on a control card(TMDSDOCK28335) I just loaded the example given in c2000ware in the custom board and I didn't get any logical error and debugging section was smooth and the board is also powered as I check.3.3v on the oscilloscope that is given to the soc-30MHz clock  but for every example across each pin I can just see 3.3v signal I don't know what might be wrong or I miss something?

    at the output of soc-30MHz, I am getting 3.3v signal on the oscilloscope

    did I miss something because for each example it's the same?

  • Muhammad,

    are you experienced in using code composer studio(CCS) or similar IDEs? It is possible that you are not loading the code correctly, or are doing something as simple as failing to begin code execution. Please follow the workshop if you are unfamiliar with CCS. Found here: https://training.ti.com/c2000-f2833x-microcontroller-workshop?context=1137791-1137783 .

    Being that you also have new untested hardware your problem could be caused by almost anything.

    muhammad usama said:
    at the output of soc-30MHz, I am getting 3.3v signal on the oscilloscope

    'soc-30MHz' seems to be a custom name, I am not familiar with this signal. Can you explain what you are looking at? If this is you clock input, then yes, you have an issue. What type of clock input are you providing?

    The examples are setup to run with a specific clocking configuration, outside of that they should run on almost any hardware.

    Regards,
    Cody 

  • actually i have run one of the code given by my employer to run the motor drive and generates the epwm with 16khz switching freq.So the code is working quite well .so to try some more example to learn more i tried to run some code thats are given in c2000ware f28335 example. The code is burn and debug in the mcu but there is no signal across the desire pin that are mention in the f28335 examples.

    I have tried some other example as well but i found the same problem..

    i just want to know now if one wants to run the code that are given in example. so what steps one have to consider it.

    i have imported the the project file (example file) and after that i have added target configuration. ccxml and and then build the code and then debug the code once debugging complete then i play the code but i cant get result on the oscilliscope for the specified examples....so what might be wrong.

  • Muhammad,

    its good to know that you don't have an issues with your hardware.

    Honestly being that this is custom hardware any number of things could be required for code to execute. You will need to understand the system around the device, for example sometimes users will implement complex external watchdogs which could keep the device from running.

    The code provided in c2000Ware is well tested, and you shouldn't have an issue there. Although, as stated before, you may need to modify the code to work with your hardware depending on the clock you provide to the device.


    Regards,
    Cody 

  • Has this issue been resolved? 

    Thanks,
    Cody

  • Still, I have the problem but I understand what you said in your last message, there might be something that I missed in the code so I am looking for that now

    Thank you for the guidance