doc/manual/main.txt

   1 /** @mainpage OpenOCD Reference Manual
   2
   3 Welcome to the OpenOCD Reference Manual -- the developer's resource for
   4 learning about the internal architecture of the OpenOCD project.
   5
   6 In addition, this document contains the tactical and strategic plans
   7 and processes that have been devleoped by and for the community.
   8
   9 Developers that want to contribute to OpenOCD should read the following
  10 sections before starting work:
  11
  12 - The List of @subpage thelist enumerates opportunities for improving or
  13 extending the OpenOCD platform.  If your ideas are on The List, you might
  14 check the mailing list archives to find the status of your feature (or bug).
  15 - The @subpage styleguide provides rules that developers should
  16   follow when writing new code for OpenOCD.
  17 - The @subpage patchguide provides policies that developers should
  18   follow when submitting patches to the project.
  19 - The @subpage bugs page contains the content of the BUGS file, which
  20   provides instructions for submitting bug reports to the maintainers.
  21
  22 @ref primer provide introductory materials for new developers on various
  23 specific topics.
  24
  25 Finally, the @ref oocd pages explain how the code has been organized
  26 into layers of APIs, providing an overview of how they fit together.
  27 These pages attempt to give developers a high-level perspective of the
  28 various code modules provided by OpenOCD.
  29
  30  */
  31
  32 /** @page primer OpenOCD Technical Primers
  33
  34 This pages lists Technical Primers available for OpenOCD Developers.
  35 They seek to provide information to pull novices up the learning curves
  36 associated with the fundamental technologies used by OpenOCD.
  37
  38 - @subpage primertcl
  39 - @subpage primerjtag
  40
  41 Contributions or suggestions for new Technical Primers are welcome.
  42
  43  */
  44
  45 /** @page oocd OpenOCD Architecture
  46
  47 The OpenOCD library consists of several APIs that build together to
  48 provide the support functionality.  The following list shows how these
  49 modules are stacked in the current implementation (from bottom to top):
  50
  51 - @subpage helperdocs
  52   - @ref helperporting
  53   - @ref helperjim
  54   - @ref helpercommand
  55   - @ref helperlogging
  56 - @subpage jtagdocs
  57   - @ref jtagcable
  58   - @ref jtagtap
  59   - @ref jtagmdriver
  60   - @ref jtagdriver
  61 - @subpage targetdocs
  62   - @ref targetarm
  63   - @ref targetnotarm
  64   - @ref targetregister
  65   - @ref targetimage
  66   - @ref targettrace
  67 - @subpage flashdocs
  68   - @ref flashcfi
  69   - @ref flashnand
  70   - @ref flashtarget
  71 - @subpage serverdocs
  72   - @ref servergdb
  73   - @ref servertelnet
  74   - @ref serverhttp
  75 - @subpage appdocs
  76
  77 Obviously, there are some nuances to the stack that are not shown by
  78 this linear list of layers.
  79
  80 The List of @ref thelist enumerates opportunities for improving or
  81 extending the OpenOCD platform.
  82
  83  */