I am using CCS v5 and sys/bios 6.33.05.46. Am using logic pd's evmomapl138 and spectrum digital xds560v2.
I am trying to run some of the generic examples. I am able to build it but when I go to the debug mode I cannot step through or run the example. Anyone has any input about this?
I have posted this in the BIOS forum and no one has answered. So I've tried posting it here.
What exact example did you try? is it one from the SYS/BIOS template examples? And how are you going to debug mode? Does the program load successfully?
Don't forget to verify answers to your forum questions by using the green "Verify Answer" button.
Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.
Having CCSv5 problems? Check out the CCSv5 Troubleshooting Guide
Click here to track an issue. Enter your bug id in the "Find Record ID" box
I have tried various examples found in the generic examples from Sys/Bios, for intance the hello world example (from the sys bios examples template). I build the project; it builds successfully. I then go to the project and choose Debug as CCS Debug Session. It configures the debugger; connects to the target; the project seems to load, but I cannot debug, just hault or terminate the session.
I get this in the console as if everything was successful:
C674X_0: Output: Target Connected.
C674X_0: Output: ---------------------------------------------
C674X_0: Output: Memory Map Cleared.
C674X_0: Output: Memory Map Setup Complete.
C674X_0: Output: KICK Unlocked.
Yet I cannot step through the program or run it.
Hope this helps. Please let me know if you need more info.
Can you post a screenshot of the target running and also when you halt it?
Sorry I took so long, I tried to unsintall and install code composer studio again to see if the problem got fixed since my coworker was able to debug from his computer. Yet the problem persisted.
When connected but cannot debug:
According to your screenshots, you are actually in a successful debug session. I assume you are hitting the green debug button. That would build your project, start the debugger, connect to the target, load the program and run to main. You first screenshot tells me all the steps were successful except the run to main. hence the target is still running. When you halt the target, the program is in some area where there is no source code for it (it may have gone into the weeds or it may be optimized code with no symbols generated for it).
So basically you have successfully started a debug session for the DSP of the L138, successfully connected to it and loaded code and is running.
What you need to determine is why the program never made it to the main of your program. I would disable the 'autorun to main' feature and then reload the program. That would simply have your application at the entry point. Then you can try debugging to see why your application never gets to main.
To disable the 'autorun to main', go to 'Tools -> Debugger Options -> Generic Debugger Options' and then in view that opens for it, scroll down until you see the autorun options. Disable the option to autorun on program reload.
Just a few minutes ago, I was able to get to the main program while trying to debug. The steps I followed were: First I chose from the Target Configurations tab the target I wanted to launch from the specific project. Then, once I was in the debug session, I connected the target, and followed to load the program. I was finally able to step through my application. Thank you so much for your input.
Sounds like you did a project-less debug session and manually loaded your program. That works too. Anyway, glad to hear you are up and running! Thanks for the update
Hi, A little late on the thread, but can someone tell me how to disable the 'autorun' feature when I am debugging? I don't know how I enabled it, but now I don't have to press F8 (Resume) once I have built and debugged a project. I have search through all the help files and tried clicking on everything but can't seem to find that option.
brendon sauercan someone tell me how to disable the 'autorun' feature when I am debugging?
When in a debug session and in the CCS Debug perspective, you can get to it via 'Tools -> Debugger Options -> Generic Debugger Options'. Look under the section for 'Auto Run Options'. To make this change persistent, remember to press the 'Remember My Settings' button at the bottom of the 'Generic Debugger Options' dialog.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.