anchor.diff:  
   #### Low-Level Timing Setup
   
  -~~~
  +~~~ruby
       # pinformat=
       #   This method is used to setup the pin clock format on the debugger device.
       #   The supported formats are rl and rh
  
positive.code: 
  ~~~ruby
    # example of capturing and programatically using information read from the DUT
  ~~~
  
  * Capture using mem api
  
  ~~~ruby
    # example of mem api use
  ~~~
  
  * reg.sync!
  
  ~~~
    (debugger prompt): dut.reg(:MyReg).sync! 
  
negative.code:   debugger	# generation of the pattern will pause here
  ~~~
  
  #### Debugging Pin Map
  
  There are pin methods available to aid debug of an OrigenLink setup.
  
  ~~~
    # Cause a pin to continuously toggle every 2 seconds
    (debugger prompt): dut.pin(:tdi).hello
    
    # Stop the pin from toggling
    (debugger prompt): dut.pin(:tdi).goodbye
  ~~~
  
  #### Staying Synchronized
  
  For efficiency vectors that are generated by your app are compressed and stored until the pattern generation is completed.  This means that when execution reaches a 'debugger' statement the previously generated vectors may not have been sent to the server yet.  There are a handful of ways to make this happen.
  