Hi! No idea how to do it on hardware side. Of course you can do a break on instruction fetch and check it for a call instruction, or a RET/RETI instruction (and the return address is found on stack). But that's rather slow (if not even slower). Alternatively you can put a write access to a global 'trace' variable on every point you want to trace, and trigger a breakpoint when this address is written to. Would be better than a breakpoint on a timer interrupt, and allows tracing ISRs too. But it is possible that not all MSPs support write-access triggers. The EEM isn't really good documented in the users guides.
JMGross ----- Ursprüngliche Nachricht ----- Von: Sergei Sharonov Gesendet am: 14.Juni.2012 05:04:55 Sorry if this is a bit of topic, but did anybody manage to get trace working with FET430UIF? I got src code for MSP430.dll V3 and some appnotes from TI but so far no go. The goal is to use it for statistical profiling. Currently I simply grab PC from a randomized timer interrupt but that requires code instrumentation and does not account for any ISRs. Regards, Sergei ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
