scripts: create symlink for community base FW binary
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.
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.
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.
v2: opt-in only with new command line switch to create the developer deployable build.
@lrudyX I dont think Internal CI tests these developer scripts ?
@lgirdwood, am I looking at this new version right and you are no longer creating the link: sof-adl.ri -> community/sof-adl.ri ?
@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.