1. 20 Mar, 2018 1 commit
  2. 06 Mar, 2018 1 commit
  3. 14 Dec, 2017 1 commit
  4. 06 Dec, 2017 1 commit
  5. 30 Nov, 2017 5 commits
  6. 27 Nov, 2017 8 commits
  7. 24 Nov, 2017 2 commits
  8. 14 Nov, 2017 1 commit
  9. 13 Nov, 2017 1 commit
  10. 25 Oct, 2017 1 commit
  11. 24 Oct, 2017 1 commit
  12. 11 Oct, 2017 1 commit
  13. 09 Oct, 2017 1 commit
  14. 05 Oct, 2017 1 commit
  15. 02 Oct, 2017 1 commit
  16. 29 Sep, 2017 1 commit
  17. 22 Sep, 2017 1 commit
  18. 21 Sep, 2017 1 commit
  19. 18 Sep, 2017 1 commit
  20. 15 Sep, 2017 1 commit
  21. 06 Sep, 2017 1 commit
  22. 26 Aug, 2017 1 commit
  23. 17 Jan, 2017 1 commit
  24. 14 Jan, 2017 1 commit
    • Tom Levens's avatar
      Cleanup · de63753d
      Tom Levens authored
      Move user CR/CSR space to VME64xCore_Top with generic to enable/disable
      it. Standardise generic default values between VME64xCore_Top and
      xvme64x_core.
      Signed-off-by: Tom Levens's avatarTom Levens <tom.levens@cern.ch>
      de63753d
  25. 13 Jan, 2017 3 commits
  26. 12 Jan, 2017 1 commit
    • Tom Levens's avatar
      Clean up CR/CSR space · 62b13b5e
      Tom Levens authored
      The CR/CSR space has been cleaned up and reworked. All decoding of the
      addresses has been moved from VME_bus to VME_CR_CSR_Space to make the
      code a bit more structured..
      
      The option to have a user CR and CSR areas has been added. These are
      external such that they can be implemented by the user.
      
      The custom CSR registers (IRQ vector/level ...) have been moved to
      VME_User_CSR.vhd. By default (in the xvme64x_core wrapper) this area is
      mapped to 0x7FF33..7FF5F (in the reserved area) in order to maintain
      compatibility with the previous version of the core. However, it can be
      moved using generics to a non-reserved area for new applications. This
      fixes Bug #1353.
      Signed-off-by: Tom Levens's avatarTom Levens <tom.levens@cern.ch>
      62b13b5e