Conversation
-p is required when the real (not symbolic) directories are not nested in one another. The documentation gap was clearly demonstrated by me getting confused even though _I_ implemented this logic some time back. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Building imx is critical to test changes like thesofproject#4524 Note not signing imx means sof-imx.ldc is staged for deployment but no imx firmware is, example: $ scripts/xtensa-build-zephyr.sh imx apl build-sof-staging ├── sof │ ├── community │ │ └── sof-apl.ri │ ├── sof-apl.ldc │ └── sof-imx.ldc └── tools └── sof-logger Signed-off-by: Marc Herbert <marc.herbert@intel.com>
| PLAT_CONFIG='intel_adsp_cavs15' | ||
| ;; | ||
| imx) | ||
| PLAT_CONFIG='intel_adsp_cavs15' |
There was a problem hiding this comment.
Hasty copy/paste... @iuliana-prodan which --board parameter have you been using?
There was a problem hiding this comment.
I believe it's nxp_adsp_imx8.
There was a problem hiding this comment.
yes, is PLAT_CONFIG='nxp_adsp_imx8'
|
|
||
| SUPPORTED_PLATFORMS=(apl cnl icl tgl-h) | ||
| SUPPORTED_PLATFORMS=(apl cnl icl tgl-h imx) | ||
| # Default value, can (and sometimes must) be overridden with -p |
There was a problem hiding this comment.
Shouldn't we add imx8 instead of imx here?
There was a problem hiding this comment.
yes, should be imx8:
-SUPPORTED_PLATFORMS=(apl cnl icl tgl-h)
+SUPPORTED_PLATFORMS=(apl cnl icl tgl-h imx8)
| "$bdir"/zephyr/zephyr.elf | ||
|
|
||
| test "$RIMAGE_KEY" = 'None' || | ||
| west sign --build-dir "$bdir" \ |
There was a problem hiding this comment.
Indentation looks odd here. Same with line below.
There was a problem hiding this comment.
Tabs vs spaces, the new line seems to be indented with spaces.
|
@marc-hb I already have a patch for this, but is only local...since Zephyr pull request is not yet merged - see zephyrproject-rtos/zephyr#35467 Here's my patch: With this you compile imx8 with: The commands for west are: |
Thanks this helps. You can already submit the BTW what about the RIMAGE_KEY? You don't care for now that this script signs sof-imx with the Intel key? Just curious. So I cherry-picked zephyrproject-rtos/zephyr#35467 and #4524 but now I'm gettting this with the Zephyr SDK 0.12.2, any clue? |
Ok, I will make a draft PR for adding
TBH I thought that if I don't specify a RIMAGE_KEY here, the .ri image is not signed. I'll have to double check this.
For this you'll have to update the xtensa_hal, also. I had a PR on that repo, also. See here. |
No there is a default value at the top. I don't think the build can produce any unsigned file with I was confused by this default value too which is why I added a comment in this PR. Maybe the default value should simply be moved down next to the relevant code.
It won't because you didn't update the west manifest in the Zephyr PR. If you want your Zephyr PR to update hal_extensa there must be a west manifest update in your Zephyr PR pointing at the new hal extensa version. https://docs.zephyrproject.org/latest/guides/modules.html#submitting-changes-to-modules Or probably even better: you could simply submit and fast-track the manifest update separately, upgrading everyone to the new hal_xtensa even before your Zephyr PR is merged. It works after cherry-picking everything, thanks! |
In fact if you run |
Building in CI is required to test changes like #4524 and others