sof icon indicating copy to clipboard operation
sof copied to clipboard

scripts: create symlink for community base FW binary

Open lgirdwood opened this issue 2 months ago • 6 comments

Currently the symlink for sof-ipc4/platform/sof-basefw.ri is not created. Fix this so that deployable builds can be copied directly to target from staging directory.

lgirdwood avatar Nov 04 '25 12:11 lgirdwood

I'm confused, we don't use sof-basefw.ri as firmware name for SOF firmware, it is only used by AVS closed firmware, which we don't support.

ujfalusi avatar Nov 21 '25 14:11 ujfalusi

I don't think it is correct to symlink the production key firmware to the community key one.

These must be different, their md5sum must be different, the key used to sign them must be different.

This is a developer script. When we want to build -> deploy -> test this is what we use. We dont want to use custom install steps or add kernel command line options.

Production signing uses a different process so not impacted.

lgirdwood avatar Nov 21 '25 15:11 lgirdwood

v2: opt-in only with new command line switch to create the developer deployable build.

lgirdwood avatar Nov 27 '25 16:11 lgirdwood

@lrudyX I dont think Internal CI tests these developer scripts ?

lgirdwood avatar Nov 28 '25 17:11 lgirdwood

@lgirdwood, am I looking at this new version right and you are no longer creating the link: sof-adl.ri -> community/sof-adl.ri ?

ujfalusi avatar Dec 03 '25 06:12 ujfalusi

@lgirdwood, am I looking at this new version right and you are no longer creating the link: sof-adl.ri -> community/sof-adl.ri ?

correct - I've just updated the help to point out that existing option can be used for developer deploy.

lgirdwood avatar Dec 04 '25 14:12 lgirdwood