-
Notifications
You must be signed in to change notification settings - Fork 14
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
fprime v3.5.0 compatibility issues #31
Comments
Yes, this is being prepped as we speak! |
Try out the |
@ethancheez Using commit 293b221 I'm seeing an error on Environment
ErrorI have verified the board definition is installed:
and I'm using a relatively recent version of
Edit: It looks like there was an update to in I noticed that there seems to be some work-in-progress in the arduino-cli cmake wrapper repo. Are you building with a different version of the wrapper than what I get when I Edit 2: Confirmed that I could generate after reverting 1efa713. I filed a separate issue for this #33. |
I'm running into an issue on
I thought this might be something I need to update in my deployment so I copied over the changes to the cookie cutter but that did not seem to help. My deployment's #####
# 'BroncoDeployment' Deployment:
#
# This registers the 'BroncoDeployment' deployment to the build system.
# Custom components that have not been added at the project-level should be added to
# the list below.
#
#####
# Deployment is only compatible with the Arduino platform
restrict_platforms(ArduinoFw)
###
# Topology and Components
###
add_fprime_subdirectory("${CMAKE_CURRENT_LIST_DIR}/Top/")
# Add custom components to this specific deployment here
# add_fprime_subdirectory("${CMAKE_CURRENT_LIST_DIR}/MyComponent/")
set(SOURCE_FILES "${CMAKE_CURRENT_LIST_DIR}/Main.cpp")
set(MOD_DEPS ${FPRIME_CURRENT_MODULE}/Top)
# choose_fprime_implementation("Os_File" Os_File_Stub)
register_fprime_deployment()
finalize_arduino_executable("${FPRIME_CURRENT_MODULE}") |
@nathancheek And to make sure your project is importing
|
I'm getting closer. I'm able to generate without errors now. Then I ran into the fatal logger issue on build that you fixed in nasa/fprime#2986. Finally I upgraded my
Looks like this macro was removed in nasa/fprime#2956. So I reverted
I tried upgrading my rp2040 board definition from 3.9.5 -> 4.1.1 and found a slightly different error in the same vein:
I'm not really sure where to go from here. Any thoughts on this? |
A RAM overflow is very common in baremetal systems because there is much smaller onboard memory compared to beefier computers (like a raspberry pi). The RPi Pico has 264 KB RAM so it looks like your specific project exceeded that amount. The solution for this is to modify the
This is my first time seeing this error but I believe that it is equivalent to the prior error on Also, as a side note, I was unable to get any RP2040 toolchains building for versions newer than |
I'm having a similar issue with fprime 3.5
|
Do you have a custom |
I don't, I could try that, but I get a similar error when compiling for the teensy, which I wouldn't expect to see due to the larger flash size
I wouldn't expect that as I'm at this step in the arduino LED blinker tutorial, I haven't added a component or anything |
The default configuration in The big ones are:
|
You can also download the fprime-baremetal sizing utility for debugging of component/deployment/binary sizes. Instructions are in the README. |
Using the rp2040 as a target I notice that the 3.4->3.5 upgrade fails with some compatibility issues.
It looks like the baremetal os files were removed from
fprime
during the OSAL and task refactors leading to the v3.5.0 release.Related PRs:
Task refactor nasa/fprime#2672
OSAL cleanup nasa/fprime#2933
Error:
The text was updated successfully, but these errors were encountered: