Generate IAR code coverage when running C-Spy outside of the IDE -
i have large number of projects, each @ least 1 automated test suite. tests run in iar's c-spy simulator. (i using iar embedded workbench arm v6.60.)
if run 1 of these test executable ide, can generate , view code coverage information. okay single project, gathering information of projects running each 1 manually far cumbersome. i'd able run build , have generate code coverage information test suites.
based on found in ewarm_debuggingguide.pdf, should able generate code coverage executable passing c-spy code coverage plugin:
--plugin c:\<iar path>/common/plugins/codecoverage/codecoverage.dll
as file code coverage info should dumped to:
--code_coverage_file c:\<test suite path>/codecoveragereport.log
so actual command i'm invoking:
c:\<iar path>/common/bin/cspybat.exe c:\<iar path>/arm/bin/armproc.dll c:\<iar path>/arm/bin/armsim2.dll c:\<test suite path>/test.out --plugin c:\<iar path>/arm/bin/armbat.dll --plugin c:\<iar path>/common/plugins/codecoverage/codecoverage.dll --backend -b --endian=little --cpu=cortex-m4 --fpu=vfpv4 --semihosting --code_coverage_file c:\<test suite path>/codecoveragereport.log
c-spy launches test suite successfully, test results printed, no code coverage file created. there no error messages.
what missing?
also, found some information states iar allows run code coverage report when using simulator configurations, not while running tests on hardware debugger configurations.
i'm using iar v7.80 , able generate code coverage file command line using c-spy using following command:
"c:\<iar path>\common\bin\cspybat.exe" --code_coverage_file coveragereport.txt -f .\settings\myproject.debug.general.xcl --backend -f .\settings\myproject.debug.driver.xcl
this command generates file called "coveragereport.txt" iar project named "myproject".
i did not have specify codecoverage.dll file work. try switching project on simulator configuration , try trimming number of options you're passing in; also, put parameter --code_coverage_file right after cspybat.exe.
hope helps!
Comments
Post a Comment