-
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
Support configurable RISC-V chip extension #773
Conversation
Added the FREERTOS_RISCV_EXTENSION option to allow the user to select which chip extension they want included. Removed the port for pulpino to instead use the new option.
Hi @JoeBenczarski |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #773 +/- ##
=======================================
Coverage 93.64% 93.64%
=======================================
Files 6 6
Lines 2549 2549
Branches 608 608
=======================================
Hits 2387 2387
Misses 107 107
Partials 55 55
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
* Add two rics-v generic ports to support FREERTOS_RISCV_EXTENSION config
@JoeBenczarski
Please help to take a look at this [PR] suggestion(JoeBenczarski#1) |
Add port GCC_RISC_V_GENERIC and IAR_RISC_V_GENERIC
Good idea. I just merged that PR. |
Thank you. I will also update the description of this PR and ask for another reviewer's opinion. |
Kudos, SonarCloud Quality Gate passed! |
Support configurable RISC-V chip extension with cmake
Description
In this PR:
Existing RISC-V cmake port only support the following combinations:
To support other combinations, two generic port targets are created:
User has to specify FREERTOS_RISCV_EXTENSION in the cmake file to use these ports:
Test Steps
n/a
Checklist:
Related Issue
#772
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.