CCS/F28M35H52C: problem running xds 510 Spectrum Digital debugger on concerto cortex m3 core.

Hi,

How are you starting the debugger? Are you selecting the project and clicking on the green bug button? If so, it is possible the cortex M3 core is not connected but the JTAG debugger is trying to load the code anyways.

In this case, can you try to follow the procedure shown below, connect to the M3 core and load the code.

software-dl.ti.com/.../sdto_ccs_debug-handbook.html

I tested my environment here but did not find anything problematic with the connection itself - however, I am still installing controlSUITE to get some suitable projects to load to my F28M35 board. I will report back if I find anything out of the ordinary.

Hope this helps,
Rafael

Preetham kashyap said:

Target must be connected before calling the function.  

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:

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 Cester,

This option is already checked. I did this as a troubleshooting method.

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

Hi Rafael,

Sorry for the delayed response. 

So i have till here: 

So when i now try to connect to the m3 core, it throws this error message. Can you tell me if i should edit some gel file to correct this error. 

Thanks

Hi,

Sorry, I missed your late reply. Are you still having this issue?

Regards,
Rafael

Rafael,

Yes i still have issues connecting XDS510 debuggers !! 

Still seeking support in this regards.

Thanks

Hi,

I am still trying to reproduce this issue here. I am suspecting there is perhaps a HW or initialization issue that prevents the M3 from properly being released from reset.

Regards,
Rafael

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