Lines Matching +full:flash +full:- +full:specific
8 the Audio and Context Engine (ACE). These Xtensa-based ADSPs can be integrated
12 +----------+-----------------------------+
16 +----------+-----------------------------+
18 +----------+-----------------------------+
20 +----------+-----------------------------+
22 +----------+-----------------------------+
24 Intel open-sources firmware for its ADSP hardware under the Sound Open Firmware
26 Xtensa OS (XTOS) and run on a variety of Intel and non-Intel platforms.
30 `UP Xtreme i11-0001 series`_ (:ref:`intel_adsp_cavs25`) board as an example.
32 otherwise stated. You will be referred to the documentation for your specific
39 -----------------------
41 You can only flash Zephyr to the ADSP by using Zephyr's Python tool in a Linux
43 to build the binary locally on their development machine and flash remotely,
58 ------------
63 .. code-block:: shell
66 west config manifest.project-filter -- +sof
72 use ``west config rimage.path /path/to/rimage-build/rimage``; see more details
73 in the output of ``west sign -h``. Running directly from the build directory
76 Platform-specific configuration files are located in the ``rimage/config/``
78 ``west config build.cmake-args -- -DRIMAGE_CONFIG_PATH=/path/to/my/rimage/config``.
82 ---------------------------
84 The Zephyr SDK provides GCC-based toolchains necessary to build Zephyr for
95 .. code-block:: shell
100 export TOOLCHAIN_VER=RG-2017.8-linux
103 The bottom three variables are specific to each version of cAVS / ACE; refer to
110 --------
114 .. zephyr-app-commands::
115 :zephyr-app: samples/hello_world
120 -------
125 the command logged for your own purposes. Run ``west sign -h`` for more
129 needed, there are several ways to override them depending on your specific
133 - For local, interactive use prefer ``rimage.extra-args`` in west config, see
134 ``west sign -h``. The WEST_CONFIG_LOCAL environment variable can point at a
137 - You can add or overwrite a ``$platform.toml`` file(s) in your
140 - For board-specific needs you can define WEST_SIGN_OPTS in
144 Starting with Zephyr 3.6.0, ``west flash`` does not invoke ``west sign``
145 anymore and you cannot pass rimage parameters to ``west flash`` anymore. To
146 see an up-to-date list of all arguments to the Intel ADSP runner, run the
149 .. code-block:: console
151 west flash --context
153 Remote Flashing to cAVS-based ADSP
154 ----------------------------------
158 and need to be restarted if a flash or runtime error occurs on the ADSP. From
163 :zephyr_file:`soc/intel/intel_adsp/tools/remote-fw-service.py` will receive
166 "cAVS tool"), which performs the flash and captures the log. Start
167 :file:`remote-fw-service.py`.
169 .. code-block:: console
171 scp -r $ZEPHYR_BASE/soc/intel/intel_adsp/tools/cavstool.py username@remotehostname
172 scp -r $ZEPHYR_BASE/soc/intel/intel_adsp/tools/remote-fw-service.py username@remotehostname
174 sudo ./remote-fw-service.py
176 :file:`remote-fw-service.py` uses ports 9999 and 10000 on the remote host to
186 .. code-block:: console
188 west flash --remote-host remotehostname --pty remotehostname
192 .. code-block:: console
194 …-p intel_adsp/cavs25 --device-testing --device-serial-pty="$ZEPHYR_BASE/soc/intel/intel_adsp/tools…
197 :file:`cavstool_client.py` to :file:`remote-fw-service.py` is forwarded through
202 .. code-block:: console
204 west flash --remote-host intermediatehost:reqport --pty remotehostname:logport
205 …-p intel_adsp/cavs25 --device-testing --device-serial-pty="$ZEPHYR_BASE/soc/intel/intel_adsp/tools…
210 .. code-block:: console
212 twister -p intel_adsp/cavs25 --hardware-map cavs.map --device-testing -T samples/hello_world
216 .. code-block:: console
218 - connected: true
223 …us/zephyrproject/zephyr/soc/intel/intel_adsp/tools/cavstool_client.py,-s,remotehostname:logport,-l"
225 - --remote-host=remotehostname:reqport
229 arguments by passing the ``--context`` flag while flashing with West.
233 Local Flashing to cAVS-based ADSP
234 ---------------------------------
236 You can also directly flash the signed binary with the cAVS tool on the board.
239 .. code-block:: console
245 .. code-block:: console
247 ***** Booting Zephyr OS vx.x.x-xxx-gxxxxxxxxxxxx *****
250 Flashing to ACE-based ADSP
251 --------------------------
253 Flashing is not yet supported for platforms with ACE-based ADSP, as these
257 ---------
260 recommended to take advantage of Zephyr's built-in :ref:`coredump` and
268 .. code-block:: console
270 sudo ./remote-fw-service.py -v
271 sudo ./cavstool.py zephyr.ri -v
275 .. code-block:: console
277 sudo ./remote-fw-service.py --help
278 sudo ./cavstool.py --help
283 .. code-block:: shell
289 :file:`remote-fw-service.py` on the board, you may have another instance of the
292 .. code-block:: console
294 $ sudo netstat -peanut | grep 9999
299 with :file:`remote-fw-service.py` but hang with no output afterwards,
300 there are two possibilities: either :file:`remote-fw-service.py` failed
301 to communicate, or :file:`cavstool.py` failed to flash. Log into
302 the remote host and check the output of :file:`remote-fw-service.py`.
308 .. code-block:: shell
310 ERROR:remote-fw:incorrect monitor communication!
312 If a "load failed" message appears, that means the flash failed. Examine the
313 log of ``west flash`` and carefully check that the arguments to ``west sign``
316 .. code-block:: console
318 WARNING:cavs-fw:Load failed? FW_STATUS = 0x81000012
319 INFO:cavs-fw:cAVS firmware load complete
320 --
322 Sometimes a flash failure or network miscommunication corrupts the state of
323 the ADSP or :file:`remote-fw-service.py`. If you are unable to identify a
327 Users - particularly, users of the Xtensa toolchain - should also consider
332 .. code-block:: console
334 rm -rf build twister-out*
335 rm -rf ~/.ccache ~/.cache/zephyr
342 .. _Chromebooks: https://www.hp.com/us-en/shop/pdp/hp-chromebook-x360-14c-cc0047nr
344 .. _UP Xtreme: https://up-board.org/up-xtreme/
346 .. _UP Xtreme i11-0001 series: https://up-shop.org/up-xtreme-i11-boards-0001-series.html
348 …ructions: https://thesofproject.github.io/latest/getting_started/build-guide/build-with-zephyr.html
350 .. _UP Community wiki: https://github.com/up-board/up-community/wiki/Ubuntu
352 .. _Cadence: https://www.cadence.com/en_US/home/tools/ip/tensilica-ip.html