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.

Problem Running C28 Blinky

Other Parts Discussed in Thread: CONTROLSUITE, ADS1274

Good morning,

Yesterday I was able to get the M3 blinky running on CCS5.3 on my DOCKH52C1 Controlcard.  I had some problems with correctly launching. Once I got past that I added the C28 Blinky to my workspace from ControlSUITE.  I have the project compiling and creating new out files.  I can launch the debug of the C28 processor.  I can get it to load the program. I can get it to run and even to step through disassembly.  However the LED never go on or off.  One thing that bothers me is that if I run the program the disassembly eventually gets to and IDLE, and never gets off of it.

I can't use the symbolic debug because the symbols don't seem to be available.  In the settings there is a warning saying that if the symbols are loaded that performance is degraded and that a kernel patch is necessary.  I find it hard to believe that the processor can't be debugged without these issues because the Concerto training showed us the ability to do symbolic debug.

Can somebody give me a step by step to correctly debug a C28 program. like the blinky?

For completeness I am attaching a zip of my project out for anyone to try.0317.blinky_c28.zip

  • Mike,

    I am not sure if you did this already but on the Concerto, since the M3 is the Master and has control of the GPIOs and Control subsystem, a setup_m3 program needs to be run first to enable all GPIOs and map them to the Control subsystem. This program is in the \F28M35x_examples_Control directory in ControlSuite.

    So here is the procedure I would recommend:

    - Import setup_m3 and blinky_c28 into your workspace. Build both projects
    - Link the target configuration file (.ccxml) created for the Concerto controlcard to both projects ( or atleast setup_m3)
    - Click on the green bug button to debug setup_m3 - this should launch the debugger and load setup_m3 (Alternately you could manually launch the target configuration and connect and load manually too if you wish)
    - Run the code and halt after a few seconds
    - Connect to the C28 device
    - Load blinky_c28 and run - you should see the LED blinking

    Let me know if this does not work.

    Just FYI, the setup_m3 program and what it does is documented in the F28M35x-FRM-EX-UG.pdf found in the C:\ti\controlSUITE\device_support\f28m35x\v160\doc folder, although I agree it isn't terribly clear that it needs to be run first to set up the Control subsystem.

  • Aarti,

    I figured out that there was some M3 coding required when I went to the next step and loaded the blinky for both cores.  You can see the added setup in the M3 blinky.c in that project.  Based on what I saw I would suggest either a readme be added to the C28 Blinky project explaining that you need to run the M3 project before the C28 can run, or at least a large clear comment in the C28 blinky.c that indicates that the M3 project must be run first.

    Thanks again for your help.  My next step is to figure out how to interface the C28 McBSP to an ADS1274.  Let me know if you have seen any diagrams and code setups for this.

    Sincerely,

    Mike Fontes

  • Mike Fontes said:
    My next step is to figure out how to interface the C28 McBSP to an ADS1274.  Let me know if you have seen any diagrams and code setups for this.

    Sorry but I don't have the expertise to help with this. You may have better luck posting this question to the C2000 device forum.