• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 676 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.

CCS/LAUNCHXL-F28379D: Code debugging error

Lahiru Sandaruwan
Intellectual 270 points

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hi all,

I am using LAUNCHXL-F28379D for my application. When I use the debug mode on CCS, code is uploading to the micro controller but when I try to run the program in debug window program is halt with dummy values on the watch window. Please help me to resolve this issue. I would like to know which parameters should be modified in the JTAG/Debugger settings in order to run my code in debug mode properly.

Thank You

Lahiru

  • 0
    TI__Guru* 85850 points
    Lahiru,
    If you are able to connect and load code into the MCU then it is likely that something in your code is causing an issue when you run. Can you load and run an example in C2000Ware for the F28379 device? If this works correctly we can look to see what differences exist in your code and the reference code.

    Best,
    Matthew
  • 0 in reply to MatthewPate
    Intellectual 270 points

    HI Matthew,

    Other code are working fine. The code i'm specifying is not give any compilation errors and load to the micro controller properly. When I try to run the code from the debug window it is not working in the intended manner. My settings for the debugger as follows. Please let me know if I require any modifications to the following settings.

    Thank You

    Lahiru

  • 0 in reply to Lahiru Sandaruwan
    TI__Guru* 85850 points
    Lahiru,
    I should have been more specific; there are no settings for the emulator/emulator actions that would effect the connection to the device in the manner you have described.

    My thought is that something in your code, when executed, is terminating the connection or resetting the device. For instance, all of our devices have a watchdog module to prevent run away code in the final application. However, during debug(and our examples) we typically disable this so that the user doesn't have to comprehend writing to it to prevent it from triggering(which is a reset action).

    That is just one example, there are other possibilities like over clocking the device with too high a PLL setting, or not initializing the ECC, etc. Most of these are taken care of/given an example of in our C2000Ware examples, which is why I suggested looking there.

    If you have based your code on these examples, for instance taking the setup portion of the examples(clock, device config, etc) then we can rule some things out. If not, we need to see if there are initializations that are not the same between your code and our examples and start there.

    Best,
    Matthew
  • 0 in reply to MatthewPate
    TI__Guru* 85850 points
    Lahiru,
    Wanted to follow up to see if you have been able to resolve your issue or had some feedback on my suggestions in the previous post. I'm going to mark this as TI thinks resolved, but feel free to reply back and the thread will open back up on my end.

    Best,
    Matthew