Skip to content
Snippets Groups Projects
  1. Apr 21, 2016
  2. Apr 06, 2016
  3. Mar 30, 2016
    • Wesley W. Terpstra's avatar
      wishbone_pkg: fix ghdl compile errors; type not locally static · 6346131a
      Wesley W. Terpstra authored
      The subrange type might not be known in this context.
      Fixes:
        wishbone_pkg.vhd:1379:26: object subtype is not locally static
      6346131a
    • Wesley W. Terpstra's avatar
      wishbone_pkg: fix ghdl compile errors due to loop over length of a variable · 30a36213
      Wesley W. Terpstra authored
      Variable lengths might change; standard forbids length in a loop.
      Fixes:
        wishbone_pkg.vhd:1576:18: universal integer bound must be numeric literal or attribute
        wishbone_pkg.vhd:1613:18: universal integer bound must be numeric literal or attribute
        wishbone_pkg.vhd:1734:30: universal integer bound must be numeric literal or attribute
        wishbone_pkg.vhd:1771:16: universal integer bound must be numeric literal or attribute
        wishbone_pkg.vhd:1806:16: universal integer bound must be numeric literal or attribute
        wishbone_pkg.vhd:1817:16: universal integer bound must be numeric literal or attribute
      30a36213
  4. Nov 18, 2015
  5. Nov 16, 2015
  6. Nov 12, 2015
  7. Jul 07, 2015
    • Wesley W. Terpstra's avatar
      xwb_clock_crossing: be more forgiving to pushy masters · 849883ad
      Wesley W. Terpstra authored
      If a Wishbone master lowers the cycle line before receiving its acks, it is
      non-conforming.  However, it is probably a good idea to not let an honest
      slave (whose ack then comes in outside of the cycle) be penalized for that
      master's misbehaviour.
      
      This small change ensures the FIFO does not leak space in this case.
      849883ad
  8. Apr 15, 2015
  9. Feb 25, 2015
    • Theodor-Adrian Stana's avatar
      wb_i2c_bridge: Fixed write to unknown address bug · 29db1b2a
      Theodor-Adrian Stana authored
      There was a bug in the wb_i2c_bridge that manifested itself a WB slave of the
      wb_i2c_master module replies by an error to the write command. The bridge FSM
      was buggy and was not clearing the WB signals, which led to the next WB transfer
      in the sequence (any access to the I2C slave) failing.
      
      This error was fixed by clearing the WB signals on error as well and the slave
      now replies properly.
      
      The WB signals are properly cleared on WB error in the case of a read, so this
      issue does not exist.
      29db1b2a
  10. Feb 24, 2015
  11. Feb 17, 2015
  12. Dec 09, 2014
  13. Aug 04, 2014
  14. Jul 31, 2014
  15. Jun 30, 2014
  16. Jun 10, 2014
  17. Jun 05, 2014
  18. May 22, 2014
  19. May 21, 2014
  20. May 20, 2014
  21. Apr 30, 2014
  22. Apr 25, 2014
  23. Apr 17, 2014
    • Wesley W. Terpstra's avatar
      spi flash: remove initialization and move erase to software · adc49ee7
      Wesley W. Terpstra authored
      Using the volatile configuration register to configure a flash chip
      is a bad idea. The problem is that if the FPGA is reset, the flash
      may be in a state inconsistent with what the FPGA requires to boot.
      
      The correct solution is to configure the non-volatile configuration
      register on the chip to what the FPGA expects on power-on. Then use
      these same settings inside the flash core.
      
      Going this route makes it necessary for software to be able to set
      the non-volatile configuration register. Rather than making the core
      even more complicated than it is, I have elected to add a FIFO which
      software can fill to issue custom SPI commands. Since erase can only
      be done from software anyway, I removed this code and let erase use
      the custom command FIFO.
      adc49ee7