-
Notifications
You must be signed in to change notification settings - Fork 71
Create 2021-07-21-handlingmemorymessages.md #345
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| --- | ||
| title: Handling memory messages Tutorial for micro-ROS | ||
| author: Maria Merlan | ||
| --- | ||
| Having total awareness of what ROS 2 messages and types are being used for, is essential in order to handle memory correctly in an embedded C99 environment. | ||
|
|
||
| The following Tutorial “Handling messages memory in micro-ROS '' at [icro-ROS web page](https://micro.ros.org/docs/tutorials/advanced/handling_type_memory/) explains in detail how to handle messages and types memory in micro-ROS. | ||
|
|
||
| The two approaches of micro-ROS memory handling are present in this tutorial. | ||
|
|
||
| micro-ROS Foxy: Memory handling using traditional allocation approach. | ||
|
|
||
| micro-ROS Galactic: Memory handling using type support introspection. | ||
|
mamerlan marked this conversation as resolved.
|
||
|
|
||
| Type Support introspection in C in micro-ROS Galactic distribution enables the new type handling API. This package is able to auto-assign memory to a certain message structure using default dynamic memory allocators. | ||
|
mamerlan marked this conversation as resolved.
|
||
|
|
||
| Thanks to the inclusion of this feature, an automated memory handling for micro-ROS types is available, enhancing the usability of the micro-ROS API. | ||
|
|
||
| The tools related to this feature are available in the package [micro_ros_utilities](https://github.com/micro-ROS/micro_ros_utilities) and the documentation is available [here](https://micro.ros.org/docs/api/utils/). | ||
| Check this [example](https://github.com/micro-ROS/micro_ros_arduino/blob/galactic/examples/micro-ros_types_handling/micro-ros_types_handling.ino) for more information about how to avoid the message memory initialization problems in micro-ROS. | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.