Occasional Contributor
Occasional ContributorHello,
Thanks for the feedback. The same issue arises whether I use the programmer or directly program the .sof from the signal tap analyzer window.
On top of that, I would like to enable signal tap to debug some faulty behavior at power up that happens once in a while, therefore I do not want to re-program the device once the faulty behavior happens.
Thanks again,
BeB
Super ContributorFor that, you need to set up a power-up trigger that does exactly what you need: look for a trigger event to occur after device programming but before you can manually start the logic analyzer. See the debug tools user guide for details on setting up a power-on trigger.
Occasional ContributorYes I am aware, but that doesn't work when the message "program the device to continue" is displayed. I am sure the trigger worked, but I can't get the data from signal tap.
Super ContributorAre you programming in the .stp window or in the Programmer?
If you are successfully programming the device from within the .stp window and you are still seeing that status, which is preventing you from starting the logic analyzer to obtain the power-up trigger captured data, the only thing I can think of is recompile and generate a new programming file.
Occasional ContributorHi,
I have done both (.stp window and programmer), with the same result. I have tried recompiling, without success.
One of the major change introduced between the working signal tap and broken signal tap is the clocking scheme. I selected a new reference clock in signal tap to reflect that, it's a valid reference clock as far as I know, but maybe signal tap disagrees with that assessment? Mind you, the project is completely functional otherwise.
I can't really think of anything else.
Thanks,
BeB
