You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the openMMC project has grown, it accumulated some cruft that made it difficult to port to new boards and hard to debug. I propose bellow some enhancements that I think would greatly benefit the overall user and programmer experience. This list is not set in stone and may it change according to our priorities.
Better documentation: Document all functions using doxygen that are not documented yet. When implementing a functionality defined by some standard, cite the standard, page number, chapter, etc.
Move bootloader source to uncontroller port as it is microcontroller specific
Medium-term (requires careful planning):
Avoid creating a new task for each sdr
Check every memory allocation and do proper handling of out-of-memory and memory fragmentation situations
Detect and report stack overflow cases (FreeRTOS already has support for detecting stack overflows, what is left to do is printing the task backtrace to de serial console and resseting the firmware)
Avoid macro functions, use static inline where adequate
As the openMMC project has grown, it accumulated some cruft that made it difficult to port to new boards and hard to debug. I propose bellow some enhancements that I think would greatly benefit the overall user and programmer experience. This list is not set in stone and may it change according to our priorities.
Short-term (can be implemented now):
Medium-term (requires careful planning):
Long-term (low priority, requires more complex changes):
The text was updated successfully, but these errors were encountered: