Is there a document that describes the timestamp logic behind the TarmacTrace plugin?
When we get concurrent events from different cores, are the timestamps valid?
Any additional information about the timestamps would be appreciated, thank you.
I'm using FVP_Base_RevC-2xAEMv8A (the free Base FVP binary from ARM). I want to use a running model that is usually designed before anything else in the chain of modeling the target system. Precise cycle timing is not my concern (if something takes 10 or 15 cycles is not of importance) but logical order of execution (like a cause and effect, or which core's signal was chosen first for example) is important. Thank you both for taking the time to address my question.
Thanks for confirming, that's a great use case, let us check the details and come back to you.