Skip to content

Updating Reference to F Prime v4#28

Open
kevin-f-ortega wants to merge 32 commits into
mainfrom
pico2
Open

Updating Reference to F Prime v4#28
kevin-f-ortega wants to merge 32 commits into
mainfrom
pico2

Conversation

@kevin-f-ortega

Copy link
Copy Markdown

No description provided.

@kevin-f-ortega kevin-f-ortega self-assigned this Jun 23, 2025
@kevin-f-ortega kevin-f-ortega marked this pull request as draft June 23, 2025 22:20
@kevin-f-ortega kevin-f-ortega marked this pull request as ready for review August 14, 2025 18:42
@ethancheez

Copy link
Copy Markdown
Collaborator

I'm a bit confused here. I thought barmetal-reference was supposed to be an example of a deployment with sensors, radios, etc.

With the deletion of everything except BaseDeployment (which now became ReferenceDeployment, what is the difference between this repo and fprime-tutorial-arduino-blinker?

@LeStarch LeStarch left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I question the lack of core cdh subtopology.

Comment thread Components/LedBlinker/LedBlinker.cpp Outdated
@ethancheez

Copy link
Copy Markdown
Collaborator

I question the lack of core cdh subtopology.

I think core cdh contains some components that aren't necessary for baremetal. Especially if we are trying to minimize the memory usage. For example health and version.

@kevin-f-ortega

kevin-f-ortega commented Aug 14, 2025

Copy link
Copy Markdown
Author

I'm a bit confused here. I thought barmetal-reference was supposed to be an example of a deployment with sensors, radios, etc.

With the deletion of everything except BaseDeployment (which now became ReferenceDeployment, what is the difference between this repo and fprime-tutorial-arduino-blinker?

I'm a bit confused here. I thought barmetal-reference was supposed to be an example of a deployment with sensors, radios, etc.

With the deletion of everything except BaseDeployment (which now became ReferenceDeployment, what is the difference between this repo and fprime-tutorial-arduino-blinker?

You are right. As of now, this repo and the fprime-tutorial-arduino-blinker is the same. But, the idea with fprime-baremetal-reference repo is to move towards using https://github.com/fprime-community/fprime-sensors to start including different sensors and radios via subtopologies. This will be more inline with how we want to present these reference projects. As we start buidling up fprime-sensors, we can build up the baremetal reference project to be more than the fprime-tutorial-arduino-blinker.

What are your thoughts on this approach?

@kevin-f-ortega

Copy link
Copy Markdown
Author

I question the lack of core cdh subtopology.

I think core cdh contains some components that aren't necessary for baremetal. Especially if we are trying to minimize the memory usage. For example health and version.

I agree

@ethancheez

Copy link
Copy Markdown
Collaborator

You are right. As of now, this repo and the fprime-tutorial-arduino-blinker is the same. But, the idea with fprime-baremetal-reference repo is to move towards using https://github.com/fprime-community/fprime-sensors to start including different sensors and radios via subtopologies. This will be more inline with how we want to present these reference projects. As we start buidling up fprime-sensors, we can build up the baremetal reference project to be more than the fprime-tutorial-arduino-blinker.

What are your thoughts on this approach?

That works for me. Just making sure we don't have duplicates of projects.

@kevin-f-ortega

Copy link
Copy Markdown
Author

That works for me. Just making sure we don't have duplicates of projects.

Thanks for keeping a vigilant eye!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants