Connecting to XDS100 emulator on EVMC6748 in CCSV4.1

What version of CCS 4.1 are you using? 4.1.0, 4.1.1 or 4.1.2? Are you using the on-board emulation?

Ryan Bishop said:

However, all of the options under the Target menu are grayed out,

Did you see this FAQ?

http://processors.wiki.ti.com/index.php/FAQ_-_CCSv4#Q:_I.27ve_successfully_started_a_debug_session_but_most_of_the_target_operations_under_the_.27Target.27_menu_are_grayed_out._How_do_I_get_access_to_them.3F

Ki-Soo,

Thanks, I know I saw that before, and I remeber now that the Debug window was closed. However now when I attempt to "Connect to Target" the entire CCS studio hangs up and has to be killed through the Task Manager. It appears to be the javaw process that is hanging. CCS will not restart properly unless I go into the Task Manager and kill the javaw.exe process.

Also to answer your question I am using CCS version 4.1.2.00027

Thanks again!

Just to summerize your environment:

-LogicPD OMAPL138 EVM

-CCS 4.1.2.00027

-Using on-board XDS100 emulation

Please correct me if any of this is incorrect.

Are you connecting to the ARM or DSP when the connect hang occurs? Could you also provide your *.ccxml file being used (see #7 of: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3131.aspx)?

Thanks

ki

Ki,

-LogicPD OMAPL138 EVM

Yes, but I am using the C6748 SOM rather than the L138 SOM.

-CCS 4.1.2.00027

Yes.

-Using on-board XDS100 emulation

Yes.

I am running the DSP only. I am using the TMS320C6748.ccxml file which I am attaching as a text file.

Thanks

Ryan

Also, here is the board .dat file.

Can you attach your GEL file? Is it the same from Logic's site?

I believe it is the same GEL file provided by Logic, but I have attached it here.

Ki,

I posed this question to the support department at Logic as well. Here was their response:

"The on-board emulator is the XDS100v1. The XDS100v2 was not developed when we designed the baseboard, else, that would have been what was used.

The CCS4.1 does not work with the XDS100v1. The best thing to do is to order the XDS100v2 from TI ($79US -- at last check) which includes the

CCS4.1 download. It is good that you already have the CCS4.1. The

XDS100v2 also permits access to the ARM L138 processor in addition to the DSP C6748."

I am confused now as to what the real status of support is for this tool in CCSv4.1. The wiki http://processors.wiki.ti.com/index.php/XDS100#What_is_the_XDS100.3F and other documents from TI seem to indicate that the XDS100v1 is supported. Please advise.

Ryan

XDS100v1 is supported with CCSv4.1.

I am actually using the on-board emulation but have my ccxml file for XDS100v2. I can actually access the ARM and DSP.

Since you are using the C6748 SOM, you can use the XDS100v1 setup and access the DSP.

Another thing to check is your switch settings for S2 and S7. Your user manual for the board has the descriptions for them

ki

Ki,

I've tried the emulator in the different modes (particularly EMU Debug boot mode) set by S7,  and it makes no difference. S2 is apparently for user application.

Ryan

Ryan,

Could you generate and provide a Debug Server Log? It will require some setup on your end but can contain a lot of information to give us insight on your issue:

http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#Debug_Server_Logging

ki

Ki,

I have followed the instructions as specified on the wiki page, however I am not seeing any output at all on the Debug View screen. Do I need to turn on some kind of debug output from CCS?

Ryan

The only thing you need to do to enable it is set the environment variable:

> set TI_DS_ENABLE_LOGGING=1

this turns on logging

Ki,

Yes. I did that. From the command prompt: "C:\Program Files\Texas Instruments\ccsv4\eclipse>set TI_DS_ENABLE_LOGGING = 1". When I enter "set" at the command prompt after that to read back the variables, it shows that TI_DS_ENABLE_LOGGING =1 just as it should. Still no output.

Ryan

You would only get output when you start a debug session (not when you start CCS). Have you tried starting a debug session? If you are still not seeing any logging, then I'm not sure what could be wrong.

Ki,

Yes, I have started a debug session. There is still no output to the dbgview. When I start debugging is when the CCSv4 hangs and becomes unresponsive. Could this be part of the problem and the reason why I see nothing on the debug view? Is there another tool we can try?

Ryan