- Mar 26, 2020
-
-
Tristan Gingold authored
-
Tristan Gingold authored
-
- Sep 09, 2019
-
-
Dimitris Lampridis authored
-
- Jul 10, 2019
-
-
Grzegorz Daniluk authored
-
- Nov 20, 2018
-
-
Grzegorz Daniluk authored
-
- Jun 19, 2018
-
-
Dimitris Lampridis authored
-
- Jun 08, 2018
-
-
Dimitris Lampridis authored
-
- May 29, 2018
-
-
Grzegorz Daniluk authored
-
- Aug 25, 2017
-
-
Grzegorz Daniluk authored
They finally don't help much and they break simulation as Modelsim complains about types conversion.
-
Grzegorz Daniluk authored
-
Grzegorz Daniluk authored
-
Grzegorz Daniluk authored
-
- Feb 14, 2017
-
-
Grzegorz Daniluk authored
-
Grzegorz Daniluk authored
-
Grzegorz Daniluk authored
-
- Oct 05, 2016
-
-
Dimitris Lampridis authored
-
- Sep 27, 2016
-
-
Tomasz Wlostowski authored
-
- Dec 09, 2014
-
-
The simulator is crashing at the end of the LM32 startup code when it tries to access the highest RAM location (at the stack pointer). After this access, the LM32 verilog code already increments the address to be prepared for the next cycle, which will never actually happen because you are at the end of the RAM. It is this address increment in verilog that is one address outside the defined RAM array for which the simulator complains and terminates. The actual synthesized code is perfectly fine; no accesses outside RAM.
-
- Mar 28, 2014
-
-
- Feb 26, 2014
-
-
Xilinx defines almost full threshold not as the used words in the FIFO but as number of available empty words (UG363 - Virtex 6 FPGA Memory Resources
-
-
- Oct 30, 2013
-
-
Matthieu Cattin authored
Replaced by a function taking the number of bits in parameter and returning a vector.
-
- May 10, 2013
-
-
Grzegorz Daniluk authored
-
- Mar 08, 2013
-
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
Conflicts: modules/genrams/xilinx/Manifest.py
-
Tomasz Wlostowski authored
Conflicts: modules/genrams/xilinx/Manifest.py modules/genrams/xilinx/generic_dpram_sameclock.vhd modules/genrams/xilinx/spartan6/generic_sync_fifo.vhd
-
- Mar 05, 2013
-
-
Wesley W. Terpstra authored
On Altera, "" generates a null-range warning. When the dpram is used heavily, these warnings add up to many.
-
Wesley W. Terpstra authored
The RW ordering on address conflict varies by platform. Some platforms only support some options. Most of the dprams in WR are portable and don't depend on the order. This new option allows a core to specify that it does not care what the result of a RW conflict is, and thus work on more platforms. For Xilinx, "dont_care" = "read_first", the old default.
-
Wesley W. Terpstra authored
On both Altera and Xilinx, a dual port memory can achieve twice the bit-width per memory block when there is a single reader and writer. This adds a place-holder generic_simple_dpram for Xilinx so that code using the purpose-built variant for Altera continues to work on ISE.
-
Wesley W. Terpstra authored
In the past we used a generic to set the initial memory contents on altera. Unfortunately, quartus compiles big generics slowly (read: hours). Now we can load from a .mif file instead, which is much faster (seconds). Thus, this old option is no longer needed.
-
- Jul 10, 2012
-
-
Wesley W. Terpstra authored
-
- Mar 28, 2012
-
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
genrams/xilinx/generic_dpram: made two separate versions for memories with both ports clocked with the same signal and with independent clocks This is to prevent ISE from interpreting the single-clock template as a dual-clock one, which may result in read-after-write memory content corruption on Spartan-6/Virtex-6 FPGAs.
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
-
-
-