On the host to which your target or targets are connected, type the following:
$ chserver |
This starts the debug server as a background process. An empty configuration file called dbg_config.xml is copied into your home directory the first time you run the debug server.
If you have defined a slot number n and have not set the environment variable, you can start the debug server by typing:
$ chserver -slot n |
If the CHSERVER_HOST environment variable is set, it must contain the correct host name, otherwise the debug server will not operate correctly.
A complete description of the debug server is provided in the chserver(1CC) man page.
If chserver is run on a different host from the one on which the system image was built (particularly on a shared file system with a different view of the build directory) it will not be able to access the necessary source files during system debugging. The symbolic link created on one host may not be valid for another because of the relative file references in the layout.xml file. There are two solutions to this problem:
Break the build_dir/build-NUCLEUS/conf/mkimage/layout_typedef.xml symbolic link accessed by chserver and replace it with a copy of the file to which it points.
Copy the conf and image directories to the host where chserver will run, then use chadmin to set the path of the layout.xml file. You will need to do this each time the system image is regenerated.