Debug Server Configuration File

Configuration information about targets is kept in a configuration file that the debug server reads every time it is run. For each target, the configuration file contains:

• The name of the target.

• The serial device used to communicate with the target.

• Configuration parameters for the serial device (baud rate and parity) .

• The architecture type of the target (for example, x86, PPC, SPARC) .

• The absolute path of the layout.xml image layout file generated by mkimage.

When a new target is registered, the configuration file is modified. (See "Registering a Target" for details of how to do this). A sample configuration file is shown below.

Example 3-1 Sample Debug Server Configuration File

<!-- ChorusOS debug server configuration file -->
<!-- Generated by ChorusOS debug server v1.0 -->
<package>
  <object name="target_name" type="target_type">
    <set param="pathmap" value=""/>
    <set param="layout_file" 
        value="build_dir/image/bmon/chorus/layout.xml"/>
    <set param="get_image_desc_cmd" 
        value="chgetlayout -stamp $(image_stamp)  $(abs_layout_file)"/>
    <set param="archive_file" value=""/>
    <set param="activate" value="1"/>
    <object name="backends" type="BackendList">
      <object name="log:bkpts:cache:log:serial" type="SerialBackend">
        <set param="device" value="/dev/term/a"/>
        <set param="baud" value="9600"/>
        <set param="parity" value="none"/>
        <set param="debug_mode" value="1"/>
        <set param="reboot_cmd" value=""/>
        <set param="reboot_wait" value="5"/>
        <set param="connect_timeout" value="120000"/>
        <set param="sync_retry_delay" value="5000"/>
      </object>
    </object>
  </object>
</package>