I'm trying to perform Dynamic Code Coverage analysis in LDRA Testbed and I've set it up to run the code using uVision. However, Testbed requires an 'Execution History' to be output by uVision before it can complete the analysis - does uVision create this? If so, where does it store it and what form does it take?
The "Execution History" is LDRA specific and has nothing to do with Keil/C166.
According to a colleague, who evaluated LDRA, LDRA modifies your source code to generate analysis info. This is normally output to serial (ASC0). You can log this to a file (using a terminal program) and feed the analysis results back to LDRA. We haven't run/evaluated it in uVision, only on a target device.
Good luck! Joost
I got the same problem with Keil C51 VM. Is it possible to make LDRA work on this compiler. Is there anyone who did that?
My suggestion would be to contact the LDRA support people, they should be able to help you with this.
-- Joost
I've already sent an e-mail to the support department about this problem. Then I saw this post, and thought that maybe someone would come out with a solution before I receive one from the support department.
Thanks anyway..