| |
In order for the LeCroy Summit Protocol analyzer to properly decode and display traces for NVMe, the analyzer software must have record of which PCIe devices are Mass Storage, what is the MBAR address, what address each queue has, as well as several other pieces of information that is typically established shortly after a PCIe link is established and devices under test come online. Typically the easiest way for the analyzer to get this information, and properly decode an NVMe trace, is to capture a trace at boot up. Every trace captured after this boot up trace will used the same decoding mapping, eliminating the need for future boot up captures. While this is a simple process, there are a few settings that may help get the complete trace with all relevant details needed for the SSD decode mapping.
|
While the SAS/SATA Trainer supports both SAS and SATA protocols, there are significant differences in implementation between SAS and SATA. The SATA protocol uses primitives to set the state of flow control in a manner that is very different than what is used in SAS and uses none of SAS’s credit based methods of flow control. In addition, while the SAS/SATA protocol suite includes definitions for all standard SAS frames in include files, there are no included definitions for SATA frames to be drawn upon in scripting a SATA trainer script. For these reasons scripting a SATA trainer script requires a different methodology than what is typically used in a SAS script.
|
Teledyne LeCroy PCIe suite supports a versatile data pattern search. This technical brief will show how us the search tool to locate a file directory to determine the starting LBA of the directory structure.
|
Teledyne LeCroy PCIe suite supports a versatile data pattern trigger. This technical brief will show how us the trigger in typical use cases as a tool to locate a file or directory access or simply to trigger on a starting LBA. This technical brief will focus on an NVMe application however the methodology is applicable to many other scenarios.
|
The Teledyne LeCroy SATA and SAS Host and Initiator Emulator tools include a feature that makes it easy to perform write-then-read data compare tests on SATA or SAS storage devices such as HDDs and SSDs. This tech brief details the functionality and use of the “write_read_compare.stc” example Host Emulation script included with the SAS/SATA Protocol Suite software installation.
|
The Sierra Trainer can be used to place a SATA Host or Device into Built In Self Test (BIST) loopback mode, usually for the purpose of transmitter testing. This technical brief details an easy step-by-step method for placing a SATA device into “Far end transmit-only,” aka “T” mode, with the Sierra Trainer.
|
For the first time in USB, the new Type-C specification defines a connector that can operate in either of the two logical orientations. This application note explains the technical considerations in effect when operating the Voyager M310C with USB Type-C cables. With an understanding of how a Type-C cable operates, users will find that the M310C design allows the ability to test all logical cable orientations in their system.The Mercury T2C also follows these plug orientation conventions.
|
M.2 SATA Adapters allow easy connection between SATA Analyzers and M.2 SSDs.
|
Target Emulation for the SAS protocol allows the DUT to be scanned and have the mode pages of the device saved and modified, allowing the Sierra system to initiate traffic and emulate a target for development and testing. The SAS Protocol Suite software provides an easy ability to identify the Device Under Test (DUT) and monitor performance during testing.
|
Guide to troubleshooting calibration and link-up issues with the Teledyne LeCroy’s Sierra SAS 12Gbps Protocol Analyzer platform.
|
|