Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

CCS/CCSTUDIO: How to enable clock when using loadti

$
0
0

Part Number:CCSTUDIO

Tool/software: Code Composer Studio

Hi there,

I have a C674x application that I am loading with the c674x cycle accurate simulator to profile it. I am using the clock function to read cycles. If I use the CCS IDE, I have to use the menu to enable the clock before running it to get a measurement. However, I am trying to figure out how to enable the clock when running my application from command line using loadti.  When using it like this:

loadti -a -c g_ccsConfigFile ITFOut.out;

I am getting 0 cycles (clock still disable).  Any ideas?

g_ccsConfigFile contains the following:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">

<instance XML_version="1.2" desc="C674x CPU Cycle Accurate Simulator, Little Endian" href="configurations/tisim_c674le.xml" id="C674x CPU Cycle Accurate Simulator, Little Endian" xml="tisim_c674le.xml" xmlpath="configurations"/>
<configuration XML_version="1.2" description="simulates the c674x core in a cycle accurate manner. supports a flat memory system and 2 timers. does not model the cache system and any other peripherals. this cpu only configuration is suitable for core level algorithms development (including bios based development), without considering the system effects, for all c674x based devices. also, it is much faster than the device simulators. &#10; choose the device configurations for developing applications that involves modules other than the core." id="C674x CPU Cycle Accurate Simulator, Little Endian">
<connection XML_version="1.2" desc="C674x CPU Cycle Accurate Simulator, Little Endian_0" id="C674x CPU Cycle Accurate Simulator, Little Endian"/>
</configuration>
</configurations>


Viewing all articles
Browse latest Browse all 17527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>