Hello,
I use a LPC2148(arm7) in uVision Keil Mdk. I get the dis-assembly listing when I compile any code.Suppose if I want to calculate the execution time for the code, one way is to find the number of cycles for execution each instruction,multiply it with the clock frequency,have a recursive addition for all the instructions and finally I can get it.. But I don want to do it manually. I want to develop an app where if I enter the dis-assembly listing and the clock frequency used, it must give me my execution time. we have the readily available dis-assembly listing for the respective code generated from the ide. But how do I proceed with that? I hope I am clear with my question..
Regards Ram Prasadh
oh!! I will have a look on what is that...
"Do you really want to do it?"
This is my scenario. Suppose 10 people are writing a code for the working of LCD module for an arm7 uP. I want to find out the execution times of each code out there and obviously we will be having a code with the least and the high execution time. Depending on those time obtained,I am going to make an algorithm for execution of the a task(in this case,the LCD code is the task) for which I will be taking the computation time of the task as the least execution time which was obtained earlier and the deadline for the task as the highest execution time obtained.. I hope I am clear with what am going to do.. So , for making these stuffs possible , I need a program to find the execution times from the dis-assembly listing...
The thing which you said just now, full-blown cycle-accurate simulator, will it suit my need??
Regards RamPrasadh
By the way, there is a simulator in Keil uVision, so you can just use that. I don't know how accurate it is timing-wise, but I'm sure you'll have to work hard to match it if you decide to write your own simulator. But normally it is so much easier to measure execution time in actual target hardware, and you get real numbers as opposed to simulations which can be not so accurate. I suggest you do just that.
By the way, there is a simulator in Keil uVision, so you can just use that. I don't know how accurate it is timing-wise, no simulator (I know of) consider cache misses and thus, per definition, no simulator can assess execution time accurately.
anyhow
why bother with a simulator? set a pin at start and reset it at end, put a scope on and you have, by simple means, a precise run time measurement.
Erik
Surely, the ARM7 instruction execution time is going to be (almost) negligible relative to the timings required of the LCD...?!
View all questions in Keil forum