1. Nov 07, 2019
  2. Nov 06, 2019
  3. Oct 29, 2019
    • Tim Newsome's avatar
      Add CSR content section. · a0e0043c
      Tim Newsome authored
      This includes XLEN and basic extension info the the structure without
      having to worry about the details because that's already done in the CSR
      contents.
      a0e0043c
  4. Oct 24, 2019
  5. Oct 17, 2019
  6. Oct 16, 2019
  7. Oct 11, 2019
    • Tim Newsome's avatar
      Add support for triggers to feature discovery. · ae690771
      Tim Newsome authored
      Also change the format so it is more generally useful, no longer using
      32-bit words everywhere, adding a magic section, adding an
      end-of-structure section, and no longer relying on which harts are
      currently selected by the debugger.
      ae690771
  8. Oct 10, 2019
  9. Oct 09, 2019
  10. Oct 05, 2019
  11. Oct 03, 2019
    • Tim Newsome's avatar
      Rewrite/clarify DM Reset Control (#494) · d933becb
      Tim Newsome authored
      * Rewrite/clarify DM Reset Control
      
      Hopefully fixes #480.
      
      * Clarifications from review.
      
      * Another clarification.
      
      * There's no way to tell when reset has started.
      
      I don't think that's very important. If it is, we'll probably have to
      add a status bit that indicates a hart is held in reset.
      d933becb
  12. Sep 24, 2019
    • Philipp Wagner's avatar
      Fix wrong table reference (#484) · 039bd5a6
      Philipp Wagner authored
      * Fix wrong table reference
      
      The label is named dtmTable:jtagregisters, not table:jtag_registers.
      
      * Remove reference to non-existent table
      
      The referenced table was removed in
      b0420b3a.
      039bd5a6
  13. Sep 17, 2019
  14. Sep 14, 2019
  15. Sep 13, 2019
    • Philipp Wagner's avatar
      dmcontrol.hartreset is WARL, not R/W (#490) · 448de850
      Philipp Wagner authored
      The spec says about the dmcontrol.hartreset field:
       "If this feature is not implemented, the bit always
      stays 0, so after writing 1 the debugger can read
      the register back to see if the feature is supported."
      
      That makes it a WARL field not a R/W field. Changing the annotation to
      make it more obvious to the reader.
      448de850
  16. Sep 11, 2019
  17. Sep 10, 2019
    • Megan Wachs's avatar
      Update implementations.tex (#482) · 99ae160f
      Megan Wachs authored
      * Update implementations.tex
      
      In the suggested implementation which uses memory map, clarify that the region should only be accessible in Debug Mode.
      
      If this region is accessible in non-debug Mode, it is unclear how the Debug MOdule is supposed to interpret the interactions with the memory regions specified here.
      
      * Update implementations.tex
      
      core -> hart for consistency
      
      * Update implementations.tex
      
      Pluralize "harts" as several harts may be in debug mode at once.
      99ae160f
  18. Sep 05, 2019
  19. Sep 04, 2019
  20. Aug 14, 2019
    • Tim Newsome's avatar
      Tighten up trigger specification. (#478) · 1e99ce75
      Tim Newsome authored
      
      
      * Tighten up trigger specification.
      
      This contains a bunch of improvements that came out of an e-mail
      discussion. The biggest one is that it specifies the priority of various
      triggers compared to the exceptions already in the Privileged Spec.
      
      * dmcontrol->mcontrol, fix cut and paste mistakes.
      
      * All trigger fields are WARL.
      
      It already said this in Trigger Registers: "All {\tt tdata} registers
      follow write-any-read-legal semantics."
      
      * supported->legal
      
      Co-Authored-By: default avatarPaul Donahue <48959409+pdonahue-ventana@users.noreply.github.com>
      
      * Incorporate minor feedbacks.
      
      * Trigger PC is set to next instruction to execute.
      
      Previously on precise timing=after exceptions we said it should be set
      to the PC of the matching instruction. But that doesn't work well
      because the debugger can't know if triggers are precise or not.
      
      * Tweak trigger priorities.
      
      Add itrigger/etrigger.
      Move mcontrol after (on previous instruction) to top priority.
      
      * Fix typo.
      
      Co-Authored-By: default avatarPaul Donahue <48959409+pdonahue-ventana@users.noreply.github.com>
      
      * Clarify mcontrol load before side effect.
      
      * Clarify trigger priority table.
      1e99ce75
    • Tim Newsome's avatar
      Rebuild PDF. · a121ee15
      Tim Newsome authored
      a121ee15
  21. Aug 02, 2019
  22. Jul 17, 2019
  23. Jul 13, 2019
  24. Jul 12, 2019
  25. Jul 09, 2019
  26. Jul 04, 2019
  27. Jun 27, 2019
  28. Jun 12, 2019
  29. Jun 07, 2019
  30. May 30, 2019
    • Tim Newsome's avatar
      Fully qualify register/field macro names. (#457) · 165f120a
      Tim Newsome authored
      * Fully qualify register/field macro names.
      
      This solves the problem we have with the same field existing in multiple
      registers, as reported in #451.
      
      * Turns out we do need serial.tex.
      
      It's used in riscv-debug-workgroup-notes.pdf which is built by default.
      
      * Fix \F and \R in serial
      165f120a
    • Paul Donahue's avatar
      Fix #452 (#459) · c47f0a03
      Paul Donahue authored
      c47f0a03
  31. May 29, 2019
    • Paul Donahue's avatar
      Fixed #453 (#458) · 633ee13c
      Paul Donahue authored
      Defined ebreaks and ebreaku as WARL fields that are 0 if the associated mode
      is not supported by the hart.
      633ee13c
  32. May 21, 2019