Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
xtensa-build-xephyr: fix xt-objcopy failure when default-params missing
Fixes recent commit 8aab183 ("xtensa-build-zephyr: fix DEFAULT_TOOLCHAIN_VARIANT spill on next platf") Some XtensaTools installation are missing this `default-params` symbolic link: ``` XtensaTools/config/ |-- X4H3I16w2D48w3a_2017_8-params |-- X6H3CNL_2017_8-params |-- cavs2x_LX6HiFi3_2017_8-params `-- default-params -> cavs2x_LX6HiFi3_2017_8-params ``` Maybe it's missing when installing with the graphical interface? This symbolic link is surprisingly enough to make `xt-objcopy` work _without_ the XTENSA_ variables. But when the variables _and_ the link are both missing, then `xt-objcopy` fails with the usual error: ``` in current dir: work/current/sof; running command: XtDevTools/install/tools/RG-2017.8-linux/XtensaTools/bin/xt-objcopy --remove-section .comment sof/build-tgl/zephyr/zephyr.strip build-sof-staging/sof-info/tgl/stripped-zephyr.elf Error: there is no Xtensa core registered as the default. You need to either specify the name of a registered Xtensa core (with the --xtensa-core option or the XTENSA_CORE environment variable) or specify a different registry of Xtensa cores (with the --xtensa-system option or the XTENSA_SYSTEM environment variable). The following Xtensa cores are available: hifiep_bd5 cavs2x_LX6HiFi3_2017_8 sample_config sample_flix ... ``` Fix this failure by simply passing the XTENSA_ variables to xt-objcopy. Kudos to Seppo Ingalsuo for the interactive debugging session that allowed root-causing this problem extremely quickly. Signed-off-by: Marc Herbert <[email protected]> (cherry picked from commit 3aeb2bf)
- Loading branch information