Thanks for the feedback! Getting "something" out indeed is a bit of a progress
Out of curiosity: what do these "beeps" sound like? speaker-test -t sine should output a 440Hz sine alternating on left and right channels.
Baytrail audio seems to be a really deep rabbit hole and I'm a bit running out of ideas. Testing different firnwares and trying a few other settings look worthwihile though - although these are just (educated) guesses.
The driver loads the firmware from `intel/fw_sst_0f28.bin`, so you can create a .config/firmware/intel directory and try with other firmware files - they have to be named `fw_sst_0f28.bin"` and stored in that directory. Just reboot after changing the file and it should be picked up (you can check with `ls -la /lib/firmware/intel/fw_sst_0f28.bin`, that should be a symlink pointing to /storage/.config/firmware/intel/fw_sst_0f28.bin).
One firmware to test would be /lib/firmware/intel/fw_sst_0f28_ssp0.bin, you can also try the realtek_fw_sst.bin from the windows driver (not idea though if that will work).
With the ssp0 firmware and maybe also with the realtek firmware you could try alternate config settings related to ssp0 firmwares - I noticed this in /usr/share/alsa/ucm/codecs/rt5640/EnableSeq.conf:
# uncomment to enable swap between AIF1 and AIF2
# warning: can only work with SSP0 firmware enabled
cset "name='SDI select' 0"
cset "name='DAI select' 0"
#cset "name='SDI select' 1"
#cset "name='DAI select' 1"
So after configuring the device with alsaucm try the following 2 commands, after that try speaker-test
You'll probably have to test all combinations of firmware and with/without these amixer commands, maybe some combination of these will succeed.
When searching the web for baytcr, rt5640 and fw_sst_0f28.bin I came across some (github) repos which had different fw_sst_0f28.bin firmware files for some devices (eg this one firmware/intel at master · Asus-T100/firmware · GitHub) - maybe one of these contain firmware matching your baytrail box.
so long,
Hias