Lines Matching full:you
32 otherwise stated. You will be referred to the documentation for your specific
41 You can only flash Zephyr to the ADSP by using Zephyr's Python tool in a Linux
45 the binary sent over the network by West and flashes it. You should install a
50 Note that if you plan to use SOF on your board, you will need to build and
52 recommended you follow the `SOF instructions`_ to build and run SOF on Zephyr.
61 you will also need to set up the SOF rimage signing tool and key.
71 your system. You can either copy the executable to a directory in your PATH or
74 makes you less likely to use an obsolete rimage version by mistake.
77 subdirectory. For a different configuration directory you can use:
87 `Cadence`_ instead. The following instructions assume you have purchased and
122 ``west build`` tries to sign the binary at the end of the build. If you need
123 to sign the binary yourself, you can invoke ``west sign`` directly. Read the
124 ``west`` logs to find the ``west sign`` invocation; you can copy and modify
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
145 anymore and you cannot pass rimage parameters to ``west flash`` anymore. To
147 following after you have built the binary:
179 (its "requests port"). When you run West or Twister on your local host,
198 an intermediate host, you may need to tell :file:`cavstool_client.py` to connect
199 to different ports as well as a different hostname. You can do this by appending
207 You can also save this information to a hardware map file and pass that to
227 Any of the arguments you would pass to Twister or West, you can pass with the
228 hardware map. As mentioned previously, you can see the Intel ADSP runner
236 You can also directly flash the signed binary with the cAVS tool on the board.
243 You should see the following at the end of the log if you are successful:
266 You can pass verbose flags directly to the Intel ADSP scripts:
288 If you get an "Address already in use" error when starting
289 :file:`remote-fw-service.py` on the board, you may have another instance of the
304 If a message about "incorrect communication" appears, you mixed up the port
323 the ADSP or :file:`remote-fw-service.py`. If you are unable to identify a
330 scratch. You can try using the "pristine" option of West first, if you like.