west.ytml: update to Zephyr 650227d8c47f (July 3rd)

[kv2019i]

Update Zephyr baseline to 650227d8c47f

Change affecting SOF build targets:

32d05d360b93 intel_adsp/ace: power: fix firmware panic on MTL
a3835041bd36 intel_adsp/ace: power: Use MMU reinit API on core context restore
a983a5e399fd dts: xtensa: intel: Remove non-existent power domains from ACE30 PTL DTS
a2eada74c663 dts: xtensa: intel: Remove ALH nodes from ACE 3.0 PTL DTS
442e697a8ff7 dts: xtensa: intel: Reorder power domains by bit position in ACE30
d1b5d7092e5a intel_adsp: ace30: Correct power control register bitfield definitions
31c96cf3957b xtensa: check stack boundaries during backtrace
5b84bb4f4a55 xtensa: check stack frame pointer before dumping registers
cb9f8b1019f1 xtensa: separate FATAL EXCEPTION printout into two
e9c23274afa2 Revert "soc: intel_adsp: only implement FW_STATUS boot protocol for cavs"
1198c7ec295b Drivers: DAI: Intel: Move ACE DMIC start reset clear to earlier
78920e839e71 Drivers: DAI: Intel: Reduce traces dai_dmic_start()
9db580357bc6 Drivers: DAI: Intel: Remove trace from dai_dmic_update_bits()
f91700e62968 linker: nxp: adsp: add orphan linker section

• [BUG] DSP panic with Zephyr on Intel MTL, regression 27th June #9268
• [BUG] SOF fails to load on MTL (with Linux 6.8 or older driver) #9243
• [BUG] Noisy DMIC recording with concurrent audio playback over speakers #9205

Also:

• [BUG] Zephyr panic with pause-resume test on LNL/nocodec #9245

[kv2019i]

@andyross @marc-hb So now fuzzer fails? Seems to segfault immediately in Printf()...?

[andyross]

Odd, I was building and running the fuzzer against recent (late June) Zephyr as recently as last week for the UUID PR. Will take a look. Nothing's changed in the native-sim code recently that I've noticed.

[andyross]

Ah, it was this patch, merged last Tuesday: zephyrproject-rtos/zephyr@6e977ae

Seems not unreasonable to have broken something in native-sim, especially since both the host libc and sanitizer code may well demand that their own constructors run before entry to the OS kernel they're instrumenting. Honestly don't know how this was working before, @aescolar is the author of both and might have a better guess than me.

FWIW: simply reverting that is enough to recover the SOF fuzzer. I'll see if there's a more kconfig-ish workaround available before trying to dig in to see what the changes were.

[aescolar]

Ah, it was this patch, merged last Tuesday: zephyrproject-rtos/zephyr@6e977ae

Apologies for that regression.
As mentioned in zephyrproject-rtos/zephyr#75399 you should be able to switch your target to native_sim (from native_posix) and it should work,
or a fix for the issue itself is queued here: zephyrproject-rtos/zephyr#75404

[marc-hb]

Both MTL https://sof-ci.01.org/sofpr/PR9278/build6183/devicetest/index.html
and LNL and LNL https://sof-ci.01.org/sofpr/PR9278/build6182/devicetest/index.html are 100% green!

CAVS25 is 100% green except for 1 model missing.

I recommend we don't block this on the other, unrelated sparse and fuzzer fixes which are already submitted and successfully tested elsewhere.

[plbossart]

we should merge this to unlock CI tests, for now we only have failures on MTL and LNL

[kv2019i]

Let's proceed with this and solve the fuzzer issue (thanks for quick reaction @andyross !) in a follow-up PR.