Replies: 2 comments
-
|
Hey @robotoshi did you get fprime working with FreeRTOS and deployed it on the STM board |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
FYI we now have a guide on how to work with external libraries |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello again,
I have been getting fprime set up and am very close to getting a build when cross-compiling.
I'm just having a couple linker errors when cross-compiling, where an included "library" that I've forked from the community fprime-freertos repo.
I have just pushed everything I have to a branch in our repo. I apologize for the mess, there may be some files in there that don't need to be, I just included everything I'm working with right now. This is a rough work in progress.
I've tried to make the project more "moudular" using included submodules, but I think I'm just not sure how to set up cmake properly to do that.
I've tried including files in MOD_DEPS, but I'm kind of confused exactly how it needs to be done to make it work.
If you have any other suggestions or advice for restructuring the project, I am open.
I have been using the
arm-none-eabi-g++compiler, but I don't think it matters too much since this is a cmake issue.The repo at the branch I'm sharing is https://github.com/CalgaryToSpace/CTS-SAT-1-Software/tree/wip
It includes a submodule https://github.com/CalgaryToSpace/fprime-freertos/tree/wip which I am also actively working on. I plan to separate out the interdependencies and share this repo for others to use eventually. This is where the changes need to be made to fix my linker problem.
When I try to build the Nucleo deployment, these are some of the linker errors I get. All the reset are similar.
Command:
Errors:
Thank you in advance for your help
Beta Was this translation helpful? Give feedback.
All reactions