Skip to content
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

Add documentation regarding code generation guidelines - Stint 1 #90

Closed
3 tasks done
mfussi66 opened this issue Apr 4, 2024 · 15 comments
Closed
3 tasks done

Add documentation regarding code generation guidelines - Stint 1 #90

mfussi66 opened this issue Apr 4, 2024 · 15 comments
Assignees
Labels
documentation Improvements or additions to documentation team-dev Activity performed by Team Dev team-fix Activity performed by Team FIX

Comments

@mfussi66
Copy link
Member

mfussi66 commented Apr 4, 2024

Now that we have achieved some sort of expertise regarding code generation for an embedded board, it might be nice to create a .md document that highlights the best practices and settings to apply for an effective and flexible process.

For example, it could contain:

  • Simulink model settings
  • CMSIS settings
  • Best practices for Simulink blocks
  • Stateflow guidelines
  • a sprinkle of dictionary usage

05/07/2024 Update:
Adding a checklist of the points addressed in this Stint 1

  • Introduction and Setup of application and toolboxes
  • Model configuration parameters
  • Setting up code replacement libraries and CMSIS
@pattacini pattacini added the documentation Improvements or additions to documentation label Apr 4, 2024
@pattacini
Copy link
Member

pattacini commented Apr 4, 2024

Nice idea @mfussi66 👍🏻

However, the goal is to publish everything, including these aspects related to the policies, on our website; so, in this sense, it's very much related to:

Now that we're in a good position with the development of the architectural models, we can think of addressing the public documentation from the ground up.

Probably, we should put this on the bill for the next facility increment.

@pattacini
Copy link
Member

Well, we haven't covered the proper Software Architectures yet...
Something that we have definitely to keep in mind.

@pattacini
Copy link
Member

/remind May 06

Copy link

octo-reminder bot commented Apr 4, 2024

Reminder
Monday, May 6, 2024 10:00 AM (GMT+02:00)

@pattacini pattacini added team-fix Activity performed by Team FIX team-dev Activity performed by Team Dev labels Apr 4, 2024
Copy link

octo-reminder bot commented May 6, 2024

🔔 @pattacini

@mfussi66 mfussi66 self-assigned this May 14, 2024
@mfussi66
Copy link
Member Author

Started a draft in my fork: https://github.com/mfussi66/icub-firmware-models/blob/devel/boards/docs/The%20Techie's%20guide%20to%20code%20generation.md

@pattacini
Copy link
Member

Great!

Agreed F2F that we eventually aim to develop the website.
In the meantime, we can keep on collecting useful info as markdown files.

@mfussi66
Copy link
Member Author

At the moment I am at the Code generation part of the model configuration parameters: https://github.com/mfussi66/icub-firmware-models/blob/devel/boards/docs/The%20Techie's%20guide%20to%20code%20generation.md#code-generation

@mfussi66
Copy link
Member Author

mfussi66 commented Jun 5, 2024

In this commit, I think I concluded the draft for the Configuration Parameters window: https://github.com/mfussi66/icub-firmware-models/tree/acc4d9da907b1f4e47e525eedcf1c9d03629a18c

There is also a small section that talks about code replacement libraries with a link to the official docs.

@pattacini
Copy link
Member

Well done 👍🏻
I'm a bit overwhelmed these days. I'll try to catch up soon.

@mfussi66
Copy link
Member Author

mfussi66 commented Jun 6, 2024

Well done 👍🏻 I'm a bit overwhelmed these days. I'll try to catch up soon.

No problem! Just posting regular updates to show progress on the task.

@mfussi66
Copy link
Member Author

Given the scope of the task, maybe it will be useful to swtich this issue to a first stint?

cc @pattacini

@pattacini
Copy link
Member

Good point 👍🏻

I've turned #13 into an Epic and thus associated this issue with that Epic.
Feel free to close this task as complete and open a follow-up to be bundled to the Epic.

@mfussi66
Copy link
Member Author

mfussi66 commented Jun 18, 2024

Closing in favour of follow up #93.

@mfussi66 mfussi66 changed the title Add documentation regarding code generation guidelines Add documentation regarding code generation guidelines - Stint 1 Jun 18, 2024
@mfussi66
Copy link
Member Author

mfussi66 commented Jul 5, 2024

I updated the open post with a checklist of topics addressed in this first sprint @andreaderito .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation team-dev Activity performed by Team Dev team-fix Activity performed by Team FIX
Projects
None yet
Development

No branches or pull requests

2 participants