How to use edge trigger and pre-trigger data viewing on Gowin online logic analyzer

littleshrimp

How to use edge trigger and pre-trigger data viewing on Gowin online logic analyzer [Copy link]

 

I encountered edge triggering and trigger position when I first used it, but I didn't use it because it was not necessary. This time, I had to use edge triggering to analyze the signal, and I "carefully" read the "Gowin Online Logic Analyzer User Guide" but couldn't find a solution.

My question is this: there is a vsync signal, and I want to detect the data before and after its rising edge, that is, I want it to be like Xilinx's ILA, so that the trigger position is in the middle of the entire memory segment, so that I can see both the data before and after the trigger. However, my settings seem to have no effect on the trigger.

In the "Gowin Online Logic Analyzer User Guide", I saw that edge triggering is supported with w/edges.

I first selected Basic w/edges and then Extended w/edges. When I selected Basic w/edges, the Function only had == and !=. I selected == according to my understanding, and then entered R in the value below. Although this method of entering R in BIN or OCT always makes me feel that it may be wrong, I have not found any other way to enter R except this way.

It can be triggered when input R, but it has the same effect as input 1, as shown in the figure below. Maybe the edge trigger is successful, and the data corresponding to the rising edge of the 0th data is displayed, but I can't view the data before the trigger like common tools such as oscilloscopes.

Later I found that changing the Trigger Position can solve this problem. Very convenient.

Jacktang

It is a good idea to select Basic w/edges first and then Extended w/edges.

littleshrimp

Jacktang posted on 2022-1-10 07:47 It is a good idea to select Basic w/edges first and then Extended w/edges

I would like to clarify that this post was originally a question post, but I found a solution right after submitting the post, so it was "urgently" turned into an experience post.
"Select Basic w/edges first and then Extended w/edges" was my attempt before I found a solution, and it is not a solution to this problem.