CLA Target Connect Issue

Hi,

Jaspreet Kaur Bhambra said:

The device is a F2806x piccolo control stick and I'm using the XDS100v2 USB Emulator for the debug session.

Note that the integrated emulator on the F2803x control stick is an XDS100v1. I'm not sure if that is the root cause of your issue, but it is something to note.

Also please provide the exact CCS version you are using. please provide the fill build number. It should look

something like

example: CCSv5.5.0.00077 (the latest CCSv5 version).

Thanks

ki

Hello Ki, 

The Code Composer version I'm using is  Version: 5.5.0.00077.

I checked the integrated emulator for the F2806x piccolo control stick. It's USBv1. I tried to use this emulator version. But still I'm getting the same error.

Hope its not something to do with Memory allocation.

Sincerely,

Jaspreet

I'm able to reproduce this issue on v5.5. I don't see it in older v5 versions so it must be something fairly new. The issue does not exist on CCSv6 beta builds.

Jaspreet Kaur Bhambra said:

Hope its not something to do with Memory allocation.

No, the issue was that the debugger failed to read the PC at that time. But I can read it afterwards. It could be that the error will have no impact to your debug session.

CCSv6 will be released sometime next week or so. You can move to that if it is a concern.

ki

hello ki,

I had used the CLA_0 in the same configuration before. I didnt get this error. I know its not something to do with the debugger.

yesterday, i found new things which look troublemsome to me.

During the debug session i found these errors:

on the CPU core: c_int00 (entry point reached).

on the CLa core: CLAtask1 does not contain frame information.

Does these errors are known issues.

Sincerely,

Jaspreet

Those messages aren't really errors.

Jaspreet Kaur Bhambra said:

on the CPU core: c_int00 (entry point reached).

c_int00 is the default entry point of ya program built by TI build tools. When you load a program, the debugger is supposed to set the program counter to the location of c_int00. The debugger then can auto-run to a label after that (usually 'main') but that is optional. Often times when you reset or restart, it will go to c_int00

Jaspreet Kaur Bhambra said:

on the CLa core: CLAtask1 does not contain frame information.

This can happen if there is not enough debug symbol information in the code you are halted in. Many times when you link in libraries, they don't have the symbolic information to unwind the call stack.

Thanks

ki