boards: xtensa: update the documentation for changes of cavstool

Update the usage for cavstool.py to remote-fw-service.py to adapt
the renaming. And also correct the params --log-port and --req-port
in the doc.

Signed-off-by: Enjia Mai <[email protected]>

Author: enjiamai

boards/xtensa/intel_adsp_cavs15/doc/index.rst

@@ -77,6 +77,7 @@ ip address), and the user account is ``user``. Then copy the python tool to the
 ``up_squared`` board from your build environment::
 
    $ scp boards/xtensa/intel_adsp/tools/cavstool.py user@cavs15:
+   $ scp boards/xtensa/intel_adsp/tools/remote-fw-service.py user@cavs15:
 
 
 Note that the ``/dev/hda`` device file created by the diagnostic driver must
@@ -85,7 +86,7 @@ loader script as root:
 
 .. code-block:: console
 
-   cavs15$ sudo ./cavstool.py
+   cavs15$ sudo ./remote-fw-service.py
 
 Cavstool_server.py is a daemon which accepts a firmware image from a remote host
 and loads it into the ADSP. After successful firmware download, the daemon also

boards/xtensa/intel_adsp_cavs18/doc/generic_intel_adsp.rst

@@ -17,8 +17,20 @@ This documentation describes how to run the intel_adsp_cavs boards. Including:
 Set up the environment
 **********************
 
-1. Copy soc/xtensa/intel_adsp/tools/cavstool.py to the target
-   host machine (DUT).
+1. Copy following two tools to the $HOME directory of the target machine (DUT):
+
+- soc/xtensa/intel_adsp/tools/cavstool.py
+   (The firmware loader)
+
+- soc/xtensa/intel_adsp/tools/remote-fw-service.py
+   (The remote service provider)
+
+   You can use scp command to copy them to DUT, Ex.
+
+.. code-block:: console
+
+   $scp boards/xtensa/intel_adsp/tools/cavstool.py user@myboard:~
+   $scp boards/xtensa/intel_adsp/tools/remote-fw-service.py user@myboard:~
 
 2. In your build machine, install the rimage tool, the signed key and
    the toml config file. Please refer to please refer:
@@ -55,7 +67,7 @@ Build and run the tests
 
 .. code-block:: console
 
-   sudo ./cavstool.py
+   sudo ./remote-fw-service.py
 
 2. Build the application. Take hello world as an example:
 
@@ -104,22 +116,22 @@ using, you can do it with following parameters:
 .. code-block:: console
 
    # with specifying the port
-   sudo ./cavstool.py --log-port 54321 --req-port 12345
+   sudo ./remote-fw-service.py --log-port 54321 --req-port 12345
 
    # can be simplified with
-   sudo ./cavstool.py -p 54321 -r 12345
+   sudo ./remote-fw-service -p 54321 -r 12345
 
    # with specifying a IP address
-   sudo ./cavstool.py -s 192.168.0.2
+   sudo ./remote-fw-service -s 192.168.0.2
 
    # with specifying the IP address with a log port
-   sudo ./cavstool.py -s 192.168.0.2:54321
+   sudo ./remote-fw-service -s 192.168.0.2:54321
 
    # with specifying the IP, log and request port
-   sudo ./cavstool.py -s 192.168.0.2:54321 -r 12345
+   sudo ./remote-fw-service -s 192.168.0.2:54321 -r 12345
 
    # Also works in this way
-   sudo ./cavstool.py -s 192.168.0.2 -p 54321 -r 12345
+   sudo ./remote-fw-service -s 192.168.0.2 -p 54321 -r 12345
 
 
 Run by twister
@@ -189,10 +201,10 @@ like following example. Assume you have a log port of 54321 and a req port
      platform: intel_adsp_cavs25
      product: None
      runner: intel_adsp
-     serial_pty: "/home/user/zephyrproject/zephyr/soc/xtensa/intel_adsp/tools/cavstool_client.py,-s,192.168.1.4,--port-log,54321,-l"
+     serial_pty: "/home/user/zephyrproject/zephyr/soc/xtensa/intel_adsp/tools/cavstool_client.py,-s,192.168.1.4,--log-port,54321,-l"
      runner_params:
        - --remote-host=192.168.1.4
-       - --tool-opt=--port-req
+       - --tool-opt=--req-port
        - --tool-opt=12345