micro-ROS / micro-ROS/micro_ros_stm32cubemx_utils
Dual ucHeap memory regions.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 275
- Forks
- 100
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I'm making a project based on FreeRTOS in STM32CubeIDE.
Build Analyzer shows two memory regions named ucHeap in RAM. I believe these two objects come from the custom_memory_manager.c and FreeRTOS's heap4.c. Is it normal these two objects coexist? Why are their sizes defined in FreeRTOS config? Why do they have the same name?
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing custom_memory_manager.c with FreeRTOS's heap4.c and reviewing the FreeRTOS configuration referenced by the Build Analyzer output. Document whether the two ucHeap objects are expected to coexist, why their sizes come from the configuration, and why they share a name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100