-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Update sabre-6quad with QEMU #8438
Conversation
Summary: - Since QEMU does not report L2CC information correctly, NuttX stops if DEBUG_ASSERTIONS=y. - This commit adds DEBUG_ASSERTIONS=y to citest/defconfigs and disables L2CC related configs. - Also, it disables RAMLOG to show the crash information Impact: - None Testing: - Tested with QEMU-7.1 Signed-off-by: Masayuki Ishikawa <Masayuki.Ishikawa@jp.sony.com>
Summary: - This commit updates README.txt regarding QEMU with DEBUG_ASSERTIONS=y Impact: - None Testing: - Tested with QEMU-7.1 Signed-off-by: Masayuki Ishikawa <Masayuki.Ishikawa@jp.sony.com>
@xiaoxiang781216 |
Hmm, it seems that heap corruption happened.
|
I can reproduce the crash.
It seems that we need to add -m 1024
I will fix common.py in this PR. |
Summary: - I noticed that nuttx crashes if DEBUG_ASSERTIONS=y - This commit fixes this issue by changing QEMU options Impact: - None Testing: - Tested with QEMU Signed-off-by: Masayuki Ishikawa <Masayuki.Ishikawa@jp.sony.com>
It seems all the tests passed.
|
@jerpelea |
Summary
NuttX stops if DEBUG_ASSERTIONS=y.
and disables L2CC related configs.
Impact
Testing