CCS5.1 Hang In Launching Sample Code

I browsed through Backhawk website and downloaded BHDetect.exe to see if my lpatop recognize XDS100 and CCS5.  The result is negative.  I include the Blackhawk log.

Thanks,

Dennis

I include CCS5 "Test Connection" log.

Thanks,

Dennis

Dennis,

It sounds like your emulator connection is good but CCS hangs when connecting to the target. To confirm this could you please do the following:

Instead of clicking on "Debug Active Project" for your Hello world program, could you right-click on the target configuration file (.ccxml) in the Target Configurations view and choose "Launch Selected Configuration". This will launch the debug session and take you to the Debug perspective. Then go to menu Run->Connect Target. Verify that this is where CCS hangs.

We've seen in past a few cases where the connect takes a long time. Could you confirm if that's the same for you - maybe give it 5-10 mins and see if it completes just as a test. We may have a patch for this that you could try out, but I'd like to confirm the symptoms before looking into whether the patch will help you or not.

Hi Dennis,

what would actually be most useful for us are any error logs or dump files (.dmp) generated.  See here for more information

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

Is this reproducable with all projects and workspaces?

What exact behaviour do you see?   A hang?  A crash?  

Could you try renaming ctools.dll to see if this has an effect?

Best Regards,

Lisa

AartiG said:

choose "Launch Selected Configuration". This will launch the debug session and take you to the Debug perspective. Then go to menu Run->Connect Target. Verify that this is where CCS hangs.

Hi AartiG,

With my setup, "Connect Target" is gray out and not selectable.  What does this mean?

Thanks,

Dennis

Dennis,

When you are in the debug perspective make sure you highlight the processor you want to connect to in the Debug view (in this case CortexA8) before going to the menu Run. Let us know if this helps.

AartiG,

I did a View->debug and I was able to select theEmulator_0/Cortex_A8_0.  The default is C64XP_0 fo rsome reason.  I did a "Connect Target" and the "GEL Expression: OnTargetConnect()" has been running for 10 minutes now and still running.  I think the behavior is just like you mentioned in ealier post.

Thanks,

Dennis

Dennis,

Could you close down CCS, then rename the file ctools.dll to something else as suggested by Lisa, and let us know if the connection works? This file can be found in \ccsv5\ccs_base\emulation\analysis\bin folder within the CCS installation.

I renamed the ctools.dll to something esle.  The OnTargetConnect() still going forever

 

Also, I have no dmp file generated.

Thanks,

Dennis

Hi Dennis,

could you please send any error logs generated then.  Also please do a search for ctools.dll.   There have been some cases where it is in two places and you have to rename the correct one. 

Is this consistant against all projects/workspaces?

Best Regards,
Lisa

Lisa TI said:

could you please send any error logs generated then.

I on my way to response to you that didn't have any error or core dump and then CCS5 crashed and it did a dump.  I have all the file in the attached zip file.

Lisa TI said:

Also please do a search for ctools.dll.   There have been some cases where it is in two places and you have to rename the correct one. 

I did a complete search on my laptop hard drive. There is no ctools.dll anymore.

Lisa TI said:

Is this consistant against all projects/workspaces?

I only have one project/workspace. The only thing I change from the sample "Hell Word" code was copy the common\common.cfg to the local workspace to override the BIOS.cpuFreq.lo = 600000000;

Please let me know the info form the dump files.

Thanks,

Dennis

Hi,

I found this log and I attach the whole log file from my workspace:

!ENTRY com.ti.ccstudio.debug 1 0 2012-01-27 08:29:54.814
!MESSAGE DS_ERROR: Cortex_A8_0: GEL: Error while executing OnTargetConnect(): Evaluation canceled.

Thanks,

Dennis

I added more GEL_TextOut() and I saw the OnTargetConnect() was hung in mDDR_Samsung_K4X51323PC();

My first guess is the OMAP3530 evm use a different DDR than the AM3517 EVM.  I will check the schematic.

Thanks,

Dennis

Dennis Nguyen47496 said:

I added more GEL_TextOut() and I saw the OnTargetConnect() was hung in mDDR_Samsung_K4X51323PC();

My first guess is the OMAP3530 evm use a different DDR than the AM3517 EVM.  I will check the schematic.

Which GEL file do you have specified in your target configuration? If you are using the default omap3530_cortexA.gel included with CCS that will likely not work, and that could very well be the reason for it hanging when processing GEL functions. GEL files are highly dependent on the board and are tailored to match the hardware, so are typically provided by the board manufacturer. If you are using the LogicPD evm you need to download the GEL file from their web site. Please download and use their GEL file for the AM3517 and let us know if that helps.

A related thread on this topic: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/106399.aspx

Thank you for your inputs.  I downloaded the gel file from LogicPD and I reviewed the pointed related thread. I moved one step closer. I was able to connect to the processor (I think, since the processor state changed from disconnected to suspended). My question is LogicPD provided a linker.cmd file. If I remember right, CCS3.3 allow me to put this linker.cmd file into my workspace.  However, CCS5 auto generate this file from C:\TI\xdctools_3_23_00_32\packages\ti\targets\elf\linkcmd.xdt. Please assist on how to generate the attached linker info to my workspace linker.cmd.

Without the correct memory map, I have "data verification error occurrred" during Run->Load->HelloWorld.out.

Thanks,

Dennis

Hi Denis,

you should be able to drag and drop it into CCSv5 into your project.   If you want to be absolutely sure and the incorrect .cfg file is still there, you can right click on the file and go

properties->build and exclude it from build.

Note right-clicking also had an option to replace the file.

Best REgards,
Lisa

I think I did as Lisa said (see Untitled.gif).  However, '-l"./configPkg/linker.cmd"' is still in the linker string that caused my DDR3_RAM problem at 0x80000000.

Thanks,

Dennis

Hi Dennis,

I just wanted to check for an update with your enquiry. 

Best Regards,
Lisa

Hi Lisa,

Thanks for checking up. My goal is to look for common core tool sets with OS/kernel in TI CCS5 and SYSBIOS on ARM Cortex-A8 with LogicPD AM3517 EVM for our future reference designs for medical devices.  With the combination of AM3517, CCS5, SYSBIOS6, I ( and other users) spent a lot times to jump through (for eaxmple using OMAP3530 device with AM3517 device issue in most released SYSBIOS 6.33.1.25, get GEL file from LogicPD, etc).  I still think there are SDRAM configuration issues need to be resolved.  I was not be able get to the SYSBIOS evaluation yet.  I was very familiar with C674x and C55 with older DSP/BIOS.  Newer users might have a harder times.

My laptop got hit by virus and I reinstalled Windows 7 and TI CCS5.  TI licensing team have get back to me yet to enable my eval CCS5.  I am stuck right now and I don't think it is worth the efforts to call up TI account manager for Flextronics to give me a CCS5 permanent license for my research.  May be that the route I have to take because I don't even know if ARM Cortex-A8 event work with CCS5 and SYSBIOS6.

Thanks,

Dennis