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

samples: smp_svr: enable support for both small and big heaps #82966

Closed

Conversation

butok
Copy link
Contributor

@butok butok commented Dec 13, 2024

  • Fix non-functional smp_svr for platforms with RAM < 256KB. By default they have support for small heaps only (CONFIG_SYS_HEAP_SMALL_ONLY).
  • Use CONFIG_SYS_HEAP_AUTO=y for the project. It enables support for both small and big heaps.
  • Proven on a platform with 128KB RAM.

- Fix non-functional smp_svr for platforms with RAM < 256KB.
  By default they have support for small
  heaps only (CONFIG_SYS_HEAP_SMALL_ONLY).
- Use CONFIG_SYS_HEAP_AUTO=y for the project.
  It enables support for both small and big heaps.
- Proven on a platform with 128KB RAM.

Signed-off-by: Andrej Butok <[email protected]>
Copy link
Collaborator

@nordicjm nordicjm left a comment

Choose a reason for hiding this comment

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

What here is needing heap? Heap is disabled by default when you configure this and I've ran this many times on devices with less than 256KiB of RAM without issue

@butok
Copy link
Contributor Author

butok commented Dec 16, 2024

Hi @nordicjm

What here is needing heap? Heap is disabled by default when you configure

Right, even if KERNEL_MEM_POOL is enabled, the heap size is zero.

and I've ran this many times on devices with less than 256KiB of RAM without issue

Switching from SYS_HEAP_SMALL_ONLY to CONFIG_SYS_HEAP_AUTO has helped for frdm-mcxa156.
I will try to find other boards with 128KB of RAM,
and to investigate if this is a common issue or a problem specific to mcxa156.

It's not critical. If you want, I can close the PR for further investigation.

@nordicjm
Copy link
Collaborator

What transport/commands are you running or where is the error shown/in response to what? Will try it on a board here

@butok
Copy link
Contributor Author

butok commented Dec 16, 2024

Closing, after further testing, a problem was on my side.

@butok butok closed this Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants