Storage Verification Framework
Early Prototype Test and Debug Start debugging early on in the prototype stage
The OakGate SVF provides two tools for Early Prototype Test and Debug. Register Editor allows PCIe register testing while IO Editor allows the user to send individual commands to the device under test (DUT).
Register EditorNVMe and AHCI register test tool
Allows NVMe and AHCI developers to ensure the register set of their HBA or Drive is working correctly. Users can read and write all registers defined by the PCIe standards.
IO Editor and Analyzer DebugPerfect for early command test and debug
The user can send individual commands to the Device Under Test (DUT) by using the IO Editor. The SVF Analyzer can be used to capture the command to ensure the device is responding properly to each command.
Real Time IO Monitoring
The SVF Analyzer provides real time monitoring capabilities allowing the user to track low level statistics, commands, and warnings in real time. This allows the user to capture the right traffic in the capture buffer.
IO MonitoringTrack traffic workload in real time
The user can monitor real time traffic to ensure the workload is running error free. If not, the analyzer can be used to identify what errors are occurring and why. Monitoring commands in real time allow the user to ensure the desired traffic is available in the capture buffer before stopping the capture.
Debugging and Analysis of IO Traffic
The SVF Analyzer allows the user to capture the packet flow of an IO Workload to debug communication problems between host and Device Under Test (DUT). The user has the capability to stop the capture manually or set a trigger through the IO Status Policy.
Frame AnalysisAnalyze all Frames (CMD, DATA, Response)
The user can select a specific Frame in a command transfer to analyze the data in the frame. The analyzer provides Decoded and Raw views of all frames allowing detailed analysis of the workload between host and DUT.
Easily Find a Command in the BufferRight click and jump to a command
The user can easily find a command in the capture buffer identified by the Real Time Traffic monitoring capabilities. After stopping the capture, the user can jump to the command in the capture buffer by utilizing the Command statistics collected during the IO traffic.
Search for FramesFind frames by Destination ID, Source ID, etc.
The user can easily find a frame in the capture buffer by using the Search Tab in the analyzer. With this tab you can search for specific Dest ID, Source ID, LBA, Ini Tag, IO Xfer (Blk), thus giving the user many options to quickly find specific frames in the buffer.
Use Fatal IO Errors to Capture DataCapture data upon error
By setting an event to be a “Fatal Error” in the IO Status Policy settings, the user can halt the IO by “Stopping” on a Fatal Error. Stopping on Fatal Errors will ensure the traffic causing this event is kept in the Capture Buffer, making it easier to analyze traffic flow.
Debug with Event LogsEasily correlate errors with analyzer captures
Easily navigate from IO Exerciser LUN errors/warnings to their corresponding locations in the Analyzer with two right-clicks. The first will open the Event Log showing each error or warning in detail, and a right-click from there will take you to that exact error or warning condition in the Analyzer buffer.