-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Coremark issues for NCS 3.0.0 #19958
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 3bac360580b6a8c659c0ac853bd2ed3bc12b31e4 more detailssdk-nrf:
Github labels
List of changed files detected by CI (6)
Outputs:ToolchainVersion: 342151af73 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
Drivers need to be run from non blocking thread. We need preemptive priority during init. Later we prefer cooperative priority to ensure no interference with benchmark. JIRA: NCSDK-30369 Signed-off-by: Jan Zyczkowski <jan.zyczkowski@nordicsemi.no>
80a3d5a
to
3647f0d
Compare
Add compiler flags to increase performance. JIRA: NCSDK-30665 Signed-off-by: Jan Zyczkowski <jan.zyczkowski@nordicsemi.no>
b978017
to
0ca3986
Compare
Enable the error level in the CoreMark sample. JIRA: NCSDK-30375 Signed-off-by: Jan Zyczkowski <jan.zyczkowski@nordicsemi.no>
0ca3986
to
3bac360
Compare
Set coremark main thread to cooperative priority at start of main - requirement to allow starting drivers form non-blocking context.
Add extra compiler flags to improve performance.
Change log level to enable seeing errors.