Contents

% render "layouts/basic.html" do

%# HTML tags can be embedded in mark down files if you want to do specific custom
%# formatting like this, but in most cases that is not required.
<h1><%= Origen.config.name %> <span style="font-size: 14px">(<%= Origen.app.version %>)</span></h1>

### Purpose

This plugin provides tester models to drive bench debuggers such as the Segger J-Link or PE Micro.

### How To Import

##### To use in an application:

Add the following to your application's <code>Gemfile</code>:

~~~ruby
gem 'origen_debuggers', '<%= Origen.app.version %>'
~~~

##### To use in a plugin:

Add the following to your plugin's gemspec:

~~~ruby
spec.add_runtime_dependency 'origen_debuggers', '~> <%= Origen.app.version.major %>', '>= <%= Origen.app.version %>'
~~~

and require the gem in your code:

~~~ruby
require 'origen_debuggers'
~~~

### How To Use

For JTAG based protocols all that should be required is to change the application target
to instantiate one of the debuggers that support JTAG, such as J-Link or P&E:

~~~ruby
$tester = OrigenDebuggers::JLink.new
#  or
#$tester = OrigenDebuggers::PEmircro.new
~~~

Patterns should now generate a debugger command file without any additional application
modifications.

### How To Setup a Development Environment

[Clone the repository from Github](https://github.com/Origen-SDK/origen_debuggers).

Some patterns can be found in the pattern directory to exercise the debuggers.

Follow the instructions here if you want to make a 3rd party app
workspace use your development copy of the <%= Origen.app.config.initials %> plugin:
[Setting up a Plugin Development Environment](http://origen-sdk.org/origen/latest/guides/plugins)

This plugin also contains a test suite, make sure this passes before committing
any changes!

~~~
origen examples
~~~

% end

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
origen_debuggers-0.5.0	templates/web/index.md.erb