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

flash usage reduction ideas #10947

Closed
dagar opened this issue Nov 29, 2018 · 2 comments
Closed

flash usage reduction ideas #10947

dagar opened this issue Nov 29, 2018 · 2 comments

Comments

@dagar
Copy link
Member

dagar commented Nov 29, 2018

Small flash saving Ideas

  1. generated parameters array split by type and store volatile separately
  2. board/ defined startup mechanism (rc.sensors_board) - allow boards to supply an rc.board init #10960
  3. Change runtime DEVICE_DEBUG to PX4_DEBUG (Drivers switch most DEVICE_DEBUG -> PX4_DEBUG #9770)
  4. uORB messages split message fields string into pieces (allows dedup)
  5. ModuleBase - consider design options that could allow refactoring with a base class such that more could be shared instead of duplicated template code.
  6. Add support for parameter instances. There are a significant number of parameters that are identical other than an index (eg CAL, RC, PWM). The same underlying parameter metadata could be shared.
  7. review Param template (there are possible ideas here we can come with 1. to reduce some code bloat)
  8. delete old/advanced mode switches
  9. Review ROMFS airframes and mixers (quite a few unused and nearly identical configurations and mixers)
  10. add minimal build option that disables various strings (PX4_INFO, PRINT_MODULE, etc) as mentioned by @bkueng (FLASH space analysis #9460 (comment))

Larger Projects

  1. NuttX compressed ROMFS (huge savings, but large effort to update NuttX)
  2. Driver updates (refactor common code, delete IOCTLs, etc)

Related - #9460

@stale
Copy link

stale bot commented Feb 28, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Mar 14, 2019

Closing as stale.

@stale stale bot closed this as completed Mar 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant