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.

C2000 Digital Power Supply Workshop



I cannot complete Lab1 in the C2000 Digital PS Workshop.  I have the EVM with the F28035.  After building the project and fixing the one error that was present and building again, I launch the F28035.ccxml configuration file and nothing happens.  When I open the memory browser, nothing is there.

  • My CCS version is:  5.5.0.00077

    Using Windows XP Professional 5.1.2600 Service Pack 3 Build 2600

  • Hi Bradley,

    Any warnings? Also, what was the error? Please attach a screenshot of the debug window.

    Regards,

    Gautam

  • Bradley,

    I assume that you are getting stuck around Step 28.  At Step 28 your CCS installation should look like the attached screenshot.

    Does it look like this?


    Thank you,
    Brett

  • Bradley,

    My guess is that your target configuration is not getting picked up or your target configuration is just a bit off.

    I might recommend choosing the F28035.ccxml target configuration to be "Set as Default".  If set as default you should then be able to click on the green bug button, see something similar to the screenshot in my previous post, and then proceed from there.

    Hopefully, this helps.


    Thank you,
    Brett

  • The F28035.ccxml is set to default.  When I click on the Debug button, The LAB1.c file does not open, I do not get any variables, and the Debug view does not open.  The build is successful with no errors.

    I am at APEC now and won't be able to try LAB1 again until Friday.

  • Bradley,

    Does CCS do anything when you press the Debug button?

    Let me know when you're back and we'll get it working.


    Thank you,
    Brett

  • CCS does not seem to do anything after I press the Debug button.  See the screen capture attached.

    6136.Screen Shot.pdf

    Screen Shot.pdf
  • Brad,

    I think the issue lies with following Step27 with Step28.  When you run Step28, does a window pop up asking you to terminate the existing session?  If not, I believe that Step28 is effectively not happening.  From what I see, Step28 essentially undoes Step27 and then does more.

    I usually connect, load, and debug using one of two ways. 

    1)  This way has more steps, but you have control of each step.
    a) From the CCS Edit view, right-click on the target configuration and click "Launch Selected Configuration".
    b) within the CCS Debug view's Debug window, right-click on the C28xx core and click Connect Target
    c) load your .out file by clicking on the load icon.  (just above the 'u' in "Code Composer Studio - Device" in your screenshot).  HotKey: Ctrl+Alt+L
    d) You should now be at Step29 in the workshop manual.  You can now run the code, single step, view memory, etc. 

    2) This way is more automated and easier.  I usually use this method when I'm debugging something other than Concerto MCUs or F2837xD (dual-core) C2000 devices.
    a) Assuming no debug session is active and assuming that the target configuration you want is set as "Set as Default", just click on the green bug button within the CCS Edit view.  (ie omit Step27 from the manual's procedure)
    b) CCS will do some things and after about 15 seconds, you should now be at Step29 in the workshop manual.  You can now run the code, single step, view memory, etc. 

    Based on your screenshot I believe that you are at step 1b.

    Hopefully the above makes sense.  Let me know if not...


    Thank you,
    Brett

  • The first way you mentioned worked (1).  However, if I try the second way (2), it does not work.  I get the screen shot I sent earlier.  I will continue with the labs and let you know if I have anymore issues.  Thanks!

  • Brad,

    It's good to hear that you are moving forward again.

    If interested in method 2, you may have to select the "Lab1" option from the bug button drop-down, not "F28035.ccxml", etc.


    Thank you,
    Brett