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.
Tool/software: Code Composer Studio
Need some help running xds 510 SD debugger on concerto cortex m3 core.
i am using a C2000 based F28M35H52C Control Card along with Docking station.
For software development till date, i used inbuild XDSv100v2 version debugger for software debugging. But now when i tried to use XDS 510 spectrum digital debugger using 10 pin JTAG connector on the docking board i am having problems.
To be more specific,
The problem i see is only when i try to debug the cortex m3 core of the controller. Meaning i can debug c28 core using xds 510, but not cortex m3 core. The error pop up message i get when i try to debug cortex m3 core is as below:
Load program Error.
Target must be connected before calling the function.
I am not sure if it has to do something with gel file. Because as i already mentioned the USB JTAG works perfectly fine for both the core.
Can you check if the "Connect to the target on debugger startup" option is ticked under the debug project properties for the Cortex_M3 core:Preetham kashyap said:Target must be connected before calling the function.
If that option isn't ticked, it can cause the "Target must be connected before calling the function" error.
Hi Rafael,
I created a new .ccxml target configuration for XDS 510 debugger and ran Test Connection too to check if the debugger is detected and the test passed.
Now i clicked on the green debug button by selecting the project of interest (cortex m3 core application). I was taken to CCS Debug perspective and some GEL files were ran. The last one it runs is f28m35h52c1_m3.gel file and this where is throws the error pop up !!
I did try the method explained in the link you shared but the manual debug launch does not work at all for me. So i can not even open Target configuration view from view tab in the menu section.
But again like i said before i can successfully launch and debug the C28 core.
Thanks
Hi,
Preetham kashyap said:Now i clicked on the green debug button by selecting the project of interest (cortex m3 core application). I was taken to CCS Debug perspective and some GEL files were ran. The last one it runs is f28m35h52c1_m3.gel file and this where is throws the error pop up !!
In this case, I suspect that a routine on the GEL file or an external factor (external watchdog or even a power glitch) may be inadvertently resetting the device when CCS attempts to load code to this core.
Preetham kashyap said:I did try the method explained in the link you shared but the manual debug launch does not work at all for me. So i can not even open Target configuration view from view tab in the menu section.
That is very strange. Don't you see the option in the View drop down menu as shown below? Selecting it will open the Target Configurations view on the right of the screen (pointed by the arrow).
If you are not seeing this option, make sure you have the CCS Edit perspective opened
The reason I insist on launching the target manually is because it is the safest to properly acknowledge what may be happening in your case - especially because the project may be trying to load code to a different target.
Hope this helps,
Rafael
Rafael,
Yes i still have issues connecting XDS510 debuggers !!
Still seeking support in this regards.
Thanks
Hi,
Please apologize for the delay, I have been trying to reproduce this issue and find additional information. Unfortunately I couldn't find anything that enabled me to recreate this scenario and the experts on the F28x device group couldn't think of any reasons why the M3 core is unable to be connected.
One suggestion was to enable the "Extended IcePick Router Support" on the Target Configuration file, but I recall this setting was only valid for the XDS510Plus models - it didn't make any difference for me. At any rate, you could give this a try and see if it works for you.
Apart from this I don't have any additional ideas, but I will keep looking and report back if I find anything.
Regards,
Rafael