- 14 Sep, 2020 4 commits
-
-
Federico Vaga authored
1.1.1 - 2020-09-14 ================== Fixed ----- - sw: fix SPI driver to update the spi_message->actual_length
-
Federico Vaga authored
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Mamta Shukla authored
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>
-
- 09 Sep, 2020 17 commits
-
-
Marcus Comstedt authored
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.
-
Marcus Comstedt authored
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.
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
Conflicts: modules/wishbone/wb_fine_pulse_gen/xwb_fine_pulse_gen.vhd
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
wb_fine_pulse_gen: implement separate serdes/PLL reset and lock indicator (required to maintain correct phase of the output pulses)
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
gc_simple_spi_master: keep MOSI at 0 when inactive so that multi-master SPI signals can be just ORed together
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tristan Gingold authored
-
- 03 Sep, 2020 1 commit
-
-
Tristan Gingold authored
-
- 24 Jul, 2020 5 commits
-
-
Dimitris Lampridis authored
1.1.0 - 2020-07-24 ================== https://www.ohwr.org/project/general-cores/tags/v1.1.0 Added ----- - hdl: New indirect wishbone master (driven by an address and data register). - hdl: New memory wrapper for Cheby. - hdl: Provide a simple vhdl package to generate WB transactions. - hdl: New wb_xc7_fw_update module. - bld: Introduce gen_sourceid.py script to generate a package with the source id. Changed ------- - bld: gen_buildinfo.py now adds tag and dirty flag. Fixed ----- - hdl: regression to gc_sync_ffs introduced by v1.0.4. - hdl: add dummy generic to generic_dpram in altera. - hdl: add missing generics to generic_sync_fifo in genram_pkg. - hdl: avoid f_log2() circular dependencies in gc_extend_pulse.
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
Signed-off-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>
-
Dimitris Lampridis authored
Previously, the full flag was asserted at g_size-1 when using g_show_ahead. The new implementation solves this. However, for backward compatibility, the default is to still use the previous behaviour. Set g_show_ahead_legacy_mode to false to switch to the new one.
-
Dimitris Lampridis authored
-
- 07 Jul, 2020 1 commit
-
-
Dimitris Lampridis authored
-
- 25 May, 2020 1 commit
-
-
Tomasz Wlostowski authored
-
- 19 May, 2020 1 commit
-
-
Tristan Gingold authored
As a generic module to update xc7 firmware.
-
- 11 May, 2020 1 commit
-
-
Tomasz Wlostowski authored
-
- 06 May, 2020 3 commits
-
-
Tristan Gingold authored
Used for fpga-dev-id (aka the convention).
-
Tristan Gingold authored
-
Tristan Gingold authored
-
- 04 May, 2020 1 commit
-
-
Tristan Gingold authored
-
- 24 Apr, 2020 3 commits
-
-
Dimitris Lampridis authored
Signed-off-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>
-
Dimitris Lampridis authored
This bugfix has been tested by myself on the latest development version of SPEC-based FMC-ADC, as well as by M. Lipinski on BTrain test setup. Closes #23.
-
Dimitris Lampridis authored
The only reason for this is to improve readability and reduce the usage of gc_posedge/gc_negedge, in case we want to deprecate them in the near future. Signed-off-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>
-
- 23 Apr, 2020 1 commit
-
-
Dimitris Lampridis authored
Signed-off-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>
-
- 21 Apr, 2020 1 commit
-
-
Dimitris Lampridis authored
The main reason for doing this is so that all our sync modules are based directly on gc_sync (instead of using it indirectly through gc_sync_ffs). Another benefit of this is that the feedback loop of the pulse synchroniser will now be two clock cycles shorter (one input clock cycle + one output clock cycle), since gc_sync_ffs is using one more flip-flop compared to gc_sync. This will also reduce the number of warnings in various synthesis and simulation tools, since gc_pulse_syncrhonizer is also used by the gc_sync_word modules, as well as the async dual clock FIFOs. Signed-off-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>
-