I am setting up an automated testing program and I have data sets of the expected memory values for specific times given in terms of clock cycles. In other words, I would like to set a breakpoint for various times (Tclk), at which the testing script will read the relevant data memory location to be compared with the expected value. Is there a way to easily acquire the current clock cycle number from the debugger?
Is there a way to easily acquire the current clock cycle number from the debugger?
if you have a free timer, yes
I do, but the fastest it can count is once every 12 clock cycles, which isn't resolute enough.
.... use a chip with a T2.
anyhow, which chip do you use, some derivatives will give you more options, e.g. SILabs chips can run timers @ sysclk.
Erik
We are testing the T8051 (tiny) chip, which has features cut back in order to save on gate count. It only has one timer which has a maximum time resolution of 12 clock cycles.
when you choose a chip with reduced capabilities, you get reduced capabilities.
We are developing one of the world's lowest power MCUs. Sacrifices had to be made. But I was more interested in discussing the capabilities of uVision, not of my chip. Having already determined that acquiring clock cycle count data from uVision would be too time consuming to implement, I have already devised an alternative scheme. Thank you for your help.