-
Notifications
You must be signed in to change notification settings - Fork 168
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
latest SW support for pulpissimo #398
Comments
Unfortunately we don't have the bandwidth to add better software support right now. You can try out https://github.com/pulp-platform/pulp-freertos which has better driver support |
Hi @bluewww, Thanks for response, I've tried the pulp-freeRTOS setup above you mentioned. I'm able compile tests and its fine. but when I try to simulate those tests on core: cv32e40p, my test get stuck. After some debugging, I find out that the freeRTOS setup is checking for 'direct mode' but the 'cv32e40p' only supports the 'vector mode'. Is this freeRTOS setup copmatible with 'cv32e40p' core? Thats why I'm not able to use freeRTOS right now, or is there a different kernel setup we have to resolve this issue? thanks! |
If you find a bug please report it in the freertos and if possible propose a fix |
Hi, I wanted to ask what is the latest SW support for pulpissimo that is compatible? I've been looking into pulp-runtime and pulp-rt but while configuring having issues running the peripherals test.
Firstly, I'm able to configure the pulp-runtime, and also able to run the basic tests of which uses stdlib/stdio etc functions.
But when it comes to peripherals testing like i2c, spi it doesn't work. I've tried to add the driver functions from pulp-rt into pulp-runtime but it gives some missing's or mismatched functions issues, that seems hard to resolve.
So, in this regard what is the lasted SW support available that after I configure can test everything, main goal is to write/run test for all peripherals of pulpissimo.
Suggestions and comments are highly appreciated. Please let me know if I'm following the wrong path or what?
Million thanks!
The text was updated successfully, but these errors were encountered: