-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG][ARL] no FW_READY at boot - ROM status 0x50000005, ROM error 0x0 #8418
Comments
Can we extend the boot timeout and check the status, i.e. are we running on WOVCLK instead of HPCLK |
First bisect results:
|
Closing as invalid, incorrect configuration targetted. |
Reopening, the Zephyr soc code has support for dynamic lookup of the core count, so the mtl built FW is expected to boot. |
Worth to check WOVCRO commits on 006 zephyr |
Base Zephyr smoke test boot up with SOF main, so this is potentially something on the SOF side. Still trying to get logs out or a proper panic dump. |
@abonislawski and @tmleman root-caused, addition of "watchdog2: watchdog@78500" is the thing that started causing this problem in this configuration. |
Great, so we just need to limit core count in watchdog EDIT: verified & working with a test patch: |
Tagged to v2.9 since not needed in v2.8 |
Update Zephyr to bring in following Zephyr commit: 155f866ecc2c dts: intel_adsp: ace remove dw watchdog Link: thesofproject#8418 Signed-off-by: Kai Vehmanen <[email protected]>
Update Zephyr to bring in following Zephyr commit: 155f866ecc2c dts: intel_adsp: ace remove dw watchdog Link: #8418 Signed-off-by: Kai Vehmanen <[email protected]>
This issue can be closed now. |
Describe the bug
FW build from latest SOF main does not boot on ARL system.
Last know good commit 98a20ce (tag: releases/mtl/v3.1.1, origin/mtl-003-drop-stable)
No FW_READY message is receive by kernel, FW state is FW_ENTERED, so ROM
has completed.
To Reproduce
Build firmware and boot system.
Reproduction Rate
100%
Expected behavior
FW should boot.
Impact
Showstopper
Environment
Logs
The text was updated successfully, but these errors were encountered: