Skip to content
Snippets Groups Projects
  1. Sep 09, 2019
  2. Aug 07, 2019
  3. Jul 10, 2019
  4. May 23, 2019
  5. May 10, 2019
  6. Apr 26, 2019
    • Dimitris Lampridis's avatar
      genrams: rework g_show_ahead feature. · 4e5f7bad
      Dimitris Lampridis authored
      The previous implementation was introducing latches to the GN4124 core under Xilinx ISE.
      
      Tested and verified to work with the following SPEC-based reference designs:
       - WR
       - MT
       - WRTD
      4e5f7bad
  7. Apr 12, 2019
  8. Feb 13, 2019
  9. Jan 28, 2019
  10. Nov 29, 2018
  11. Nov 20, 2018
  12. Aug 07, 2018
  13. Aug 06, 2018
  14. Aug 03, 2018
  15. Jun 19, 2018
  16. Jun 08, 2018
  17. May 29, 2018
  18. Oct 11, 2017
  19. Aug 25, 2017
  20. Jun 23, 2017
  21. May 02, 2017
  22. Feb 14, 2017
  23. Feb 03, 2017
  24. Oct 13, 2016
  25. Oct 05, 2016
  26. Sep 27, 2016
  27. Jan 06, 2016
    • Cesar Prados's avatar
      generic_fifos: reorganization of the inferred, generic and altera fifos · bd7bca1c
      Cesar Prados authored
      The so-called "inferred_X_fifo" are basically generics fifos using
      inferred rams blocks from altera or xilinx, depending the target
      platform. That's why it makes more sense to move them to the "generic"
      folder of genrams. This change forces to rename the "generic_X_fifo"
      under "altera". Since these fifos are using the altera fifo  Megafunction,
      are going to be called "altera_X_fifo". The Manifest has been changed accordingly.
      btrain-v2.5
      bd7bca1c
  28. Feb 17, 2015
  29. Dec 09, 2014
    • Peter Jansweijer's avatar
      genrams/xilinx: address bus modulo ram size but only for simulation · 12c045eb
      Peter Jansweijer authored and Grzegorz Daniluk's avatar Grzegorz Daniluk committed
      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.
      12c045eb
  30. Aug 14, 2014