PCIe分析仪不存储来自两个方向的流量

什么？
你跑的速度是多少？
您使用的是LTSSM Viewer，还是以其他方式查看LTSSM？
你怎么知道链接上发生了什么？
你在运行训练序列之间重置了吗？
哪个方向，上游或下游缺少流量？
使用TS1或TS2作为触发器会发生什么？
你用示波器查看了这个链接吗？
眼睛好看吗？
抖动怎么样？
当系统无法可靠连接时，通常是电气问题。
免责声明：为了获得更可靠的响应，您应该考虑致电当地的安捷伦技术呼叫中心。
安捷伦论坛在“可用”的基础上进行监控，并不一定是解决技术问题的最快方式。



     以下为原文

  What?

What speed are you running?

Are you using the LTSSM Viewer, or are you looking at the LTSSM some other way? How do you know what's happening on the link?

Do you reset in between running the training sequences?

Which direction, upstream or downstream is missing traffic?

What happens when you use TS1 or TS2 as a trigger?

Have you looked at the link with an oscilloscope? Do the eyes look good? What about jitter? When a system can't link reliably it is quite often an electrical issue.

Al

Disclaimer: For more reliable response, you should consider calling your local Agilent Technical Call Center. The Agilent Forums are monitored on an "as available" basis, and aren't necessarily the fastest way to get technical questions answered.

> {quote：title = algoss写道：} {quote}>你的速度是多少？
这是一个正常的PCIe gen2训练序列，因此从2.5GHz开始，在训练的speed.recovery状态下达到5gHz。
> {quote：title = algoss写道：} {quote}>您使用的是LTSSM Viewer，还是以其他方式查看LTSSM？
你怎么知道链接上发生了什么？
我正在使用LTSSM查看器> {quote：title = algoss写道：} {quote}>你在运行训练序列之间重置了吗？
分析仪在训练序列号之间没有重置。
> {quote：title = algoss写道：} {quote}>哪个方向，上游或下游缺少流量？
我缺少来自下游的流量（root complex tx）> {quote：title = algoss写道：} {quote}>你看过示波器的链接了吗？
眼睛好看吗？
抖动怎么样？
当系统无法可靠连接时，通常是电气问题。
即使没有在分析仪上捕获，当它正确训练时，眼睛看起来很好并且链接正常。
> {quote：title = algoss写道：} {quote}>当你使用TS1或TS2作为触发器时会发生什么？
我需要锁定这个，但正如我所说，当我只运行一个训练序列时，一切似乎都没问题。



     以下为原文

  > {quote:title=algoss wrote:}{quote}
> What speed are you running?

This is a normal PCIe gen2 training sequence so starts at 2.5GHz and goes to 5gHz in the speed.recovery state of the training.

> {quote:title=algoss wrote:}{quote}
> Are you using the LTSSM Viewer, or are you looking at the LTSSM some other way? How do you know what's happening on the link?

I'm using the LTSSM viewer

> {quote:title=algoss wrote:}{quote}
> Do you reset in between running the training sequences?

The analyzer doe's not get a reset inbetween training sequenses no.

> {quote:title=algoss wrote:}{quote}
> Which direction, upstream or downstream is missing traffic?

I'm missing traffic from downstream(root complex tx)

> {quote:title=algoss wrote:}{quote}
> Have you looked at the link with an oscilloscope? Do the eyes look good? What about jitter? When a system can't link reliably it is quite often an electrical issue.

the eye looks fine and the the link is ok when it trains correctely, even if it is not captured on the analyzer.

> {quote:title=algoss wrote:}{quote}
> What happens when you use TS1 or TS2 as a trigger?

I need to lock at this, but as I said when I only run one training sequence everything seems to be ok.

我不会称之为Gen2训练序列。
我称之为训练序列，然后是速度变化。
是的，它只是语义，但我想要清楚，并确保我们谈论同样的事情。
当你说，“当我只运行一个训练序列时，一切似乎都没问题”，你的意思是Gen1训练吗？
您是否经历了培训和速度变化之间的正常启动序列，包括InitFC和Config访问？
分析仪设定的深度是多少？
您是否打开了任何存储过滤功能？
您的跟踪内存可能已用完。
2个方向独立存储，可以在不同时间开始和停止。
我没有可用的分析仪，但可以通过使用顺序触发来触发速度变化。
它通常是TLP，后跟TS。
如果可行，请仔细查看TS以确认它是速度变化。
免责声明：为了获得更可靠的响应，您应该考虑致电当地的安捷伦技术呼叫中心。
安捷伦论坛在“可用”的基础上进行监控，并不一定是解决技术问题的最快方式。



     以下为原文

  I wouldn't call this a Gen2 training sequence. I would call it a training sequence, followed by a speed change. Yes, it just semantics, but I want to be clear and make sure we're talking about the same thing.

When you say, "when I only run one training sequence everything seems to be ok", do you mean just the Gen1 training?

Do you go through the normal startup sequence between training and speed change, including InitFCs, and Config accesses?

What depth is the analyzer set to? Do you have any storage filtering turned on? It is possible that you are running out of trace memory. The 2 directions are stored independently and may start and stop at different times.

I don't have an analyzer available, but it is possible to trigger on the speed change, by using a sequential trigger. It's generally a TLP followed by a TS. If that works, look closely at the TS to verify that it's a speed change.

Al

Disclaimer: For more reliable response, you should consider calling your local Agilent Technical Call Center. The Agilent Forums are monitored on an "as available" basis, and aren't necessarily the fastest way to get technical questions answered.

> {quote：title = algoss写道：} {quote}>我不会称之为Gen2训练序列。
我称之为训练序列，然后是速度变化。
是的，它只是语义，但我想要清楚，并确保我们谈论同样的事情。
根复合体和端点都是PCIe gen2，因此目标是将链接作为PCIe gen2。
但是你很自然地说，发生的事情是一个速度变化的训练序列。
> {quote：title = algoss写道：} {quote}>当你说“当我只运行一个训练序列时，一切似乎都没问题”，你的意思是Gen1训练吗？
不，我知道如果我使用停止按钮上的触发启动分析仪，请再次向下和向上取下链接，以便运行训练。
按停止按钮以生成触发器。
在LTSSM查看器中计算LTSSM状态。
我在上下链路上得到了正确的状态转换。
来自于LTSSM查看器中的detect - > L0（gen1） - > recovery - > L0（gen2）。
但如果我通过上下连接运行几个连续的训练序列。
强制重新运行链接训练。
将停止按钮设置为触发器。
在LTSSM查看器中计算LTSSM状态。
我得到的训练状态在上游到达gen1和gen2中的L0，但我在下游获得的所有内容都是最终的轮询状态。
> {quote：title = algoss写道：} {quote}>你是否经历了培训和速度变化之间的正常启动序列，包括InitFC和Config访问？
没有。
但是正如我从PCIe rev 2.01中可以理解的那样，这不是必要的，因为速度变化是由链接训练的配置状态发出的。
> {quote：title = algoss写道：} {quote}>分析仪设置的深度是多少？
您是否打开了任何存储过滤功能？
您的跟踪内存可能已用完。
2个方向独立存储，可以在不同时间开始和停止。
深度设置为4GB。
我可能会耗尽内存，但随后分析器prioretice，因为我从上游有一个很长的跟踪，只是从下游的一小部分。
> {quote：title = algoss写道：} {quote}>我没有可用的分析仪，但可以通过使用顺序触发来触发速度变化。
它通常是TLP，后跟TS。
如果可行，请仔细查看TS以确认它是速度变化。
我还没有尝试过这个，但在gen complex的gen2中链接很好，所以它应该没问题。



     以下为原文

  > {quote:title=algoss wrote:}{quote}
> I wouldn't call this a Gen2 training sequence. I would call it a training sequence, followed by a speed change. Yes, it just semantics, but I want to be clear and make sure we're talking about the same thing.

both root complex and endpoint are PCIe gen2 so the objective is to get the link up as PCIe gen2. But you are apselutely correct that what happens is a training sequence with speed change.

> {quote:title=algoss wrote:}{quote}
> When you say, "when I only run one training sequence everything seems to be ok", do you mean just the Gen1 training?

No. 
I meen that If I start the the analyzer with trigger on stop button, take the link down and up again so that the training is run. 
Press the stop buttom to generate trigger.
calulate the LTSSM states in the LTSSM viewer.
I get the correct state transitions both on up and down strem. from detect -> L0(gen1) -> recovery -> L0 (gen2) in the LTSSM viewer.

but if I run several consecutive training sequenses by taking the link up and down. Forcing to rerun the linktraining. With stop buttom set as trigger.
calulate the LTSSM states in the LTSSM viewer.
I get training states on the up stream reaching L0 in both gen1 and gen2, but all I get in the down stream is a polling state all at the end.

> {quote:title=algoss wrote:}{quote}
> Do you go through the normal startup sequence between training and speed change, including InitFCs, and Config accesses?

no. But as I can understand from the PCIe rev 2.01 this is not nessasery, as the speed change is signaled by the configuration state of the linktraining.

> {quote:title=algoss wrote:}{quote}
> What depth is the analyzer set to? Do you have any storage filtering turned on? It is possible that you are running out of trace memory. The 2 directions are stored independently and may start and stop at different times.

the depth is set to 4GB. 
I may be running out of memory but then the analyzer prioretice addly as I have a long trace from the up stream bu only a littel bit from the down stream.

> {quote:title=algoss wrote:}{quote}
> I don't have an analyzer available, but it is possible to trigger on the speed change, by using a sequential trigger. It's generally a TLP followed by a TS. If that works, look closely at the TS to verify that it's a speed change.

I havent tryed this but the link comes up fine in gen2 at the root complex so it should be ok.

那么，如果你把目标放下来然后备份，目标是不能正常运行的问题，还是当你这样做时分析器没有正确捕获数据的问题？
人



     以下为原文

  So, is the problem that the target doesn't run properly if you bring it down then back up, or is the problem that the analyzer isn't correctly capturing data when you do that?

Al

问题是分析仪在上下链接时捕获数据。
或者它不存储来自两种方式的数据。



     以下为原文

  the problem is that the analyzer dosent capture data when bringing the link up and down. or it does not store data from both ways.

好的，从你告诉我的情况来看，如果你只需要系统一次，分析仪就能很好地捕获数据，但是如果你把它带上，下来，那就不行了。
分析仪无法知道系统中发生了什么，除非捕获流量，这取决于看到有效的电压水平和速度。
它没有看到重置线或除了车道之外的任何东西。
如果它根据您对目标的处理方式进行不同的操作，则目标必须采取不同的操作。
您是否尝试过使用有效的触发器和序列？
依靠“停止”按钮似乎不是正确的做法。
顺便说一句，由于LTSSM查看器除了捕获的流量之外无法访问任何内容，因此它从它所看到的内容中做出了很多猜测和推论。
除非您有双向有效的触发器和有效数据，否则可能是错误的。
您需要使用越来越复杂的触发器来完成整个过程，以查看正在发生的事情。
有一些我刚才想到的......我们还没有谈到车道宽度。
您的目标是否有可能改变车道宽度？
我已经看到目标不正确，有时在两个方向上有不同的车道宽度。
这肯定会对分析仪造成严重破坏。
免责声明：为了获得更可靠的响应，您应该考虑致电当地的安捷伦技术呼叫中心。
安捷伦论坛在“可用”的基础上进行监控，并不一定是解决技术问题的最快方式。



     以下为原文

  OK, from what you have told me, the analyzer captures data just fine if you bring your system up just once, but it doesn't if you bring it up, down, and up.

The analyzer has no way of knowing what's going on in the system, except by capturing traffic, which is dependent on seeing valid voltage levels and speeds. It doesn't see the reset line or anything except the lanes. If it is operating differently based on what you are doing with your target, then the target must be doing something different.

Have you tried using a valid trigger, with a sequence? Relying on the "Stop" button just doesn't seem like the right thing to do.

BTW, since the LTSSM viewer doesn't have access to anything except captured traffic, it makes a lot of guesses and inferences from what it sees. Unless you have a valid trigger, and valid data in both directions, it may be wrong.

You need to work your way through the process using more and more complex triggers to see what's happening.

There's something I just thought of... We haven't talked about lane width. Is there a possibility that your target is changing lane width? I have seen targets that, incorrectly, sometimes have different lane widths in the 2 directions. That will definitely cause havoc with the analyzer.

Al

Disclaimer: For more reliable response, you should consider calling your local Agilent Technical Call Center. The Agilent Forums are monitored on an "as available" basis, and aren't necessarily the fastest way to get technical questions answered.

只要我能看到电压水平和眼图开启就可以了。
> {quote：title = algoss写道：} {quote}>分析师无法知道系统中发生了什么，除非捕获流量，这取决于看到有效的电压水平和速度。
它没有看到重置线或除了车道之外的任何东西。
如果它根据您对目标的处理方式进行不同的操作，则目标必须采取不同的操作。
在包窗口的末尾只有一些向下包，所以它不仅仅是LTSSM解码器。
> {quote：title = algoss写道：} {quote}>您是否尝试过使用有效的触发器和序列？
依靠“停止”按钮似乎不是正确的做法。
>您需要使用越来越复杂的触发器来完成整个过程，以查看正在发生的事情。
我没有找到一个触发器，可以在polling.configuration trainign状态的超时时触发。
但是我想在这里发现什么是不相干的。
> {quote：title = algoss写道：} {quote}>我想到的是......我们还没有谈到车道宽度。
您的目标是否有可能改变车道宽度？
我已经看到目标不正确，有时在两个方向上有不同的车道宽度。
这肯定会对分析仪造成严重破坏。
没有看到任何证据，但我一直在寻找。



     以下为原文

  as long as I can see the voltage levels and the eye opening is ok.

> {quote:title=algoss wrote:}{quote}
> The analyzer has no way of knowing what's going on in the system, except by capturing traffic, which is dependent on seeing valid voltage levels and speeds. It doesn't see the reset line or anything except the lanes. If it is operating differently based on what you are doing with your target, then the target must be doing something different.

there is only some down packages at the end of the package window as well so it's not only the LTSSM decoder.

> {quote:title=algoss wrote:}{quote}
> Have you tried using a valid trigger, with a sequence? Relying on the "Stop" button just doesn't seem like the right thing to do.
> You need to work your way through the process using more and more complex triggers to see what's happening.

I have not found a trigger that can trig on timeout from polling.configuration trainign state. but I'm looking to find what is unike here. 

> {quote:title=algoss wrote:}{quote}
> There's something I just thought of... We haven't talked about lane width. Is there a possibility that your target is changing lane width? I have seen targets that, incorrectly, sometimes have different lane widths in the 2 directions. That will definitely cause havoc with the analyzer.

not seen any evidens of this but I havent been looking.

“我没有找到一个触发器，可以在polling.configuration trainign状态下触发超时。但是我想在这里发现什么是不合适的。”分析器实时对任何状态一无所知。
从捕获的数据推断出有关底层机器状态的任何信息。
可以在没有TLP或DLLP发生的超时时触发。
在从Gen1切换到Gen2之前，您可能需要考虑做一些类似于Gen1的全套配置读取和/或写入，或者至少是寄存器0的配置读取类型0，从而为分析仪提供一些流量来触发。
免责声明：为了获得更可靠的响应，您应该考虑致电当地的安捷伦技术呼叫中心。
安捷伦论坛在“可用”的基础上进行监控，并不一定是解决技术问题的最快方式。



     以下为原文

  "I have not found a trigger that can trig on timeout from polling.configuration trainign state. but I'm looking to find what is unike here. "

The analyzer knows nothing about any of the states, in real time. Any information about the state of the underlying machine is inferred from captured data. It is possible to trigger on a timeout where no TLPs, or maybe DLLP's occur. You might need to think about doing something like a full set of Config Reads and/or Writes at Gen1, or at least a Config Read Type 0 of register 0 before you switch from Gen1 to Gen2, giving the analyzer some traffic to trigger on.

Al

Disclaimer: For more reliable response, you should consider calling your local Agilent Technical Call Center. The Agilent Forums are monitored on an "as available" basis, and aren't necessarily the fastest way to get technical questions answered.