Expected Behavior

FAQ should reflect latest release.

Current Behavior

PTP (IEEE-1588) is identified as future work.

Possible Solution

Steps to Reproduce (for bugs)

Context

Possibly some more PTP docs could be added, and referred to in the FAQ.

Your Environment

• SatCat5 version used: 2.2.0

Short bug description

The axi_bvalid is tied to one.

OneSpin 360DV Protocol Complience

The OneSpin Protocol Compliance App automatically tests all possible communication transactions for specific protocols exhaustively, without the need to create stimulus. In addition, the app automates and simplifies the configuration and instantiation of these assertion sets for particular verification setups. The engineer simply instantiates the appropriate Verification Intellectual Property (VIP) checker and the app does the rest with no further interaction. The checker can test for the existence of specific protocol violations, or formally prove that the interface is performing correctly.

Steps to reproduce and details

There are two valid signals in the design, the axi_bvalid and the axi_rvalid. For each, OneSpin AXI4Lite VIP checker includes the check to make sure the VALID is inactive during or right after reset, based on section 11.1.2 in 'AMBA AXI Protocol Version 2.0 Specification'. Both assertions are failing. The assertion for the axi_bvalid is very simple to debug and analyze because the signal is tied to one. Here is a snippet from the OneSpin debugger

Expected Behavior

Documentation reflects current status.

Current Behavior

The documentation reflects earlier versions of satcat5, especially the directory path. It looks like is possibly only works on Linux (or at least I'm not sure how to do the command line version on Windows).

Possible Solution

It probably needs an update by someone who actually understands what it should now do, but I'll try to make at least some fixes.

Steps to Reproduce (for bugs)

Context

Your Environment

Short bug description

The RDATA signal should not change during VALID && !READY

Steps to reproduce and details

Based on the section 3.1 in AMBA AXI Protocol Version 2.0 Specification, the data or control information from the source remains stable until the destination drives the READY signal HIGH, indicating that it accepts the data or control information.
In the latest version of the RTL, following the fixes based on this issue, the RDATA signal changes during the window the VALID is high and READY is low.

Here is a screenshot from the debugger in OneSpin 360DV, based on the OneSpin Protocol Compliance App.