AnsweredAssumed Answered

ETB status stuck at stopped after trigger

Question asked by Ian Ferrel on Oct 23, 2015
Latest reply on Nov 23, 2015 by Karina Valencia Aguilar

When collecting trace in the ETB, after a trigger has occurred, I can’t seem to reset the ETB so it will collect more trace. After stopping and reenabling the formatter, the ETB status register continues to show that it’s stopped and triggered, with no new trace collected. I’ve seen similar behavior in other hardware when the trigger was not acknowledged, so I looked in the reference manual to see if there was an acknowledge bit that I had to set manually.


In the Vybrid Reference Manual, Rev 3, and I found "Table 21-8. MDM AP Control Register Assignments, which lists bit 25 as the CTI trigger ack, but also says that its reserved, and has the comment "TKT085997 : fix postponed.


Setting that bit does not resolve the issue.


Has anyone seen this behavior? Am I correct that the problem is with trigger ack? Is there another solution? Can someone explain what "TKT085997 : fix postponed." means. It sounds like this might be a known issue