Hi,
On Sat, 15 Jun 2019, Tarcatu, Dragos wrote:
For me, IPC timeout of 3sec and boot timeout of 5sec work out of the box (qemu running on a pretty low end desktop system). Trying to play a stream
In my case, the topology only seem to get loaded successfully if I disable the firmware tracing in the driver. Otherwise it's failing no matter how much I increase the timeouts.
ack, that's a known thing, interface for firmware tracing is not fully implemented in the BYT qemu model, so you have to disable it in kernel config for now.
But it should not fail the boot completely, so this is still a bug, filed as: https://github.com/thesofproject/qemu/issues/14
I also noted that we have some timing-related problem in the DSP boot. I had not noticed this before as I've run the xtensa qemu always with "-s -S" (or -d to the xtensa-host.sh script) flags. Today when I tried
I can confirm the firmware not booting up when started without the gdb
Ok, let's file a bug for this: https://github.com/thesofproject/qemu/issues/13
option. However, on my machine hooking up with gdb to the qemu dsp host doesn't seem to work either:
[...]
(gdb) target remote :1234 Remote debugging using :1234 Remote 'g' packet reply is too long (expected 304 bytes, got 632 bytes): e31b2dff006830ff00000000303a30ff306930ff2b032dbf607f32fff015cc000000000020070600446930ff20070600506930ff05aa2cbf507f32ff0000000000000000000000000c4134ff0001000000080000b4be2cbfa07f32ff043a30ff300000000ad0ea0d342030ff000000000000000000000000807f32ffdc6930ffec2330ff0a2c2dff202c2dff0000000016000000000000000500000020000000fedbb3c23e48851c2007060000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001500000000000000000000000000000000000000000000000000000000000000e31b2dff00000000e31b2dffe31b2dff26fa2cff0000000000000000000000000000000020070600200706002001060000000000000000000000000050252dff28262dff00272dffd8272dff000000000000000000000000000000000000000000000000488f000000042cff04000000000000008b9e9801000000000000000000000000000000000000000000000000000000000000000000000000b4be2cbfa07f32ff043a30ff300000000ad0ea0d342030ff000000000000000000000000807f32ffdc6930ffec2330ff006830ff00000000303a30ff306930ff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Aa, there's a fix for this. This just got merged to the 8.1 branch of sof crosstool-ng branch for sof-gcc8.1:
https://github.com/thesofproject/crosstool-ng/commits/sof-gcc8.1
Br, Kai