Issue occurred when "wb.ack" became active in the same cycle as "wb.stall" became inactive. The "RESPONSE_READ" state was skipped and therefore a proper handshake with the axilite bus wasn't guaranteed.

Add scoped XDC constraints for CDC modules

See merge request !16

These XDC files can be used by Vivado projects to automatically infer
proper timing constraints for CDC paths.

Fix reset CDC issue in gc_sync_word_rd

See merge request !15

Fix wb_ack_o violation in wb_simple_timer

See merge request !14

The clk_out domain mistakenly used reset from clk_in domain.
Additionally, the data_out_o port had this reset signal connected mistakenly as clock enable.

Fixes issue #29

Logically it's exactly the same, but for some reason Synplify doesn't
like "/=" for file opening status.

sim/if_wb_master: fix wb classic broken in commit cbc1c428: [sim] rewrite of the WB master interface

So that in one read access, the software can read both the status and
the value and can decide if the value is correct.  This avoids race
issues.

Simplify the code and avoid possible glitches.

The goal is to make sure that files in the common directory don't
depend on things defined elsewhere. With these changes, the only
remaining issue is gc_delay_line that uses generic_dpram from
genrams
Signed-off-by: Olof Kindgren <olof.kindgren@gmail.com>

Fixes to the latest proposed_master merge

See merge request !11

1.1.1 - 2020-09-14
==================

Fixed
-----
- sw: fix SPI driver to update the spi_message->actual_length

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

The spi-ocore driver was not updating the actual_length field in the
spi_message structure. This field could be used by SPI users to see if
all bytes have been transferred.

In particular we found the problem because the m25p80 driver uses the
actual_length to determine if there are transmission errors (-EIO).
Signed-off-by: Mamta Shukla <mamta.ramendra.shukla@cern.ch>
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

The response should not be EXOKAY unless an atomic access is requested
by the master using the LOCK signals.  This bridge does not even
support atomic accesses (it's an AXI4-Lite slave and does not have the
LOCK signals) so it's required to respond OKAY even if the master
does attempt an atomic access (this is how the master knows that the
slave does not support atomic accesses).  The AXI4-Lite specification
clearly states that the EXOKAY response is not supported in AXI4-Lite.

The BVALID signal must be asserted once the write operation is
completed.  The master is not required to assert BREADY before this
happens.  The old code happened to work if the master tied BREADY
high, which is allowed but not required.

Conflicts:
	modules/wishbone/wb_fine_pulse_gen/xwb_fine_pulse_gen.vhd

wb_fine_pulse_gen: implement separate serdes/PLL reset and lock indicator (required to maintain correct phase of the output pulses)