Repository navigation
logger complains about abi mismatch #662
Description
While trying to run the logger with the latest SOF master, I see the error:
Error: abi version in sof-apl.ldc file does not coincide with abi version used by logger
{{ message }}
Activity
ranj063 commentedon Dec 3, 2018
kernel branch: cros-sof-v4.14-rebase
topology: SOF master (sof-glk-da7219.m4)
lgirdwood commentedon Dec 3, 2018
@ranj063 is your logger from latest SOF master too (not SOFT repo). Can you also send a PR that prints the ABI versions for logger and ldc files in the error message (that way we can tell what is out of date). Thanks
ranj063 commentedon Dec 3, 2018
@lgirdwood yes I used SOF master for logger, topology and firmware. I will send the PR
lgirdwood commentedon Dec 3, 2018
Thanks, btw ABI going through some changes to make all this go away with future ABI updates, hence the failures atm. Some more ABI PRs pending shortly.
ranj063 commentedon Dec 3, 2018
Updated the error message with version numbers in #664 and the error seen is:
Error: abi version in sof-apl.ldc file does not coincide with abi version used by logger
logger ABI Version is 33554432
ldc_file ABI Version is 1
mengdonglin commentedon Dec 4, 2018
Need to monitor
#663
#664
and further kernel update to fix this issue.
stevyan commentedon Dec 4, 2018
Summary:
Issue isn't seen both on the APL (pcm512x ) & BYT (rt5651):
Test Env:
sof master: b3692cd
sof tool: b3692cd
kernel sof-dev: d72b338
tplg: sof-apl-pcm512x.tplg-b3692cd7, sof-byt-rt5651-b3692cd7.tplg
xiulipan commentedon Dec 4, 2018
@stevyan
Are you sure about the test case?
I used the latest logger and still see the error. But some older logger have no such issues
xiulipan commentedon Dec 4, 2018
@ranj063
From you log, it seems we got some wrong ldc abi version.
33554432is0x2000000, thus the SOF_ABI_VERSION_MAJOR is 2.xiulipan commentedon Dec 4, 2018
@bkokoszx @akloniex
Please check ldc generate functions, it seems the abi_version there is not right.
mengdonglin commentedon Dec 4, 2018
I cannot see any ABI update for this on kernel sof-dev branch, so this should be a generic issue, not only for GLK.
xiulipan commentedon Dec 4, 2018
@stevyan @bkokoszx @akloniex
Retest with build server binary, no error.
Confused about why the original bug happen.
bkokoszx commentedon Dec 4, 2018
@ranj063
Could you try to rebuild rimage, then SOF and afterwards try to reproduce issue?
It seems very similar to (I would say it can be the same :)): #642
./autogen.sh
./configure --enable-rimage
make
sudo make install
ranj063 commentedon Dec 4, 2018
@bkokoszx yes this problem does go away after building rimage.
I just realized that BUILD_RIMAGE is set to 0 in the xtensa_build_all script.
I thought we always build rimage before building the FW.
@xiulipan do you know why we changed this?
xiulipan commentedon Dec 5, 2018
@ranj063
That maybe some old code remaining. I was intend to have some args to set rimage build to speed up CI build and local build. That change is gone somehow, but the flag used for it is still in the scripts.
Let me have some fix for that.
mengdonglin commentedon Dec 5, 2018
@xiulipan will rimage building be optional or based on the change of its dependencies?
xiulipan commentedon Dec 6, 2018
@mengdonglin
I think we need to make it optional.
lgirdwood commentedon Dec 6, 2018
@ranj063 I hit this, but it's because the top level Makefile does not recurse into the tools directory to re-make the tools. You need to do this manually.
ranj063 commentedon Jan 24, 2019
@mengdonglin closing this as the issue is fixed by building rimage