-
Hi! I am completely new to modm, but it seems like a great project and exactly what I have been looking for: a high quality C++ library for embedded devices. I would be interested in using it at work for a CubeSat mission. The problem is that the VA41620 that we'll use is not supported (which is not surprising since it's radiation hard and not very common). I am willing to try to add support for it myself, but I have no idea how much work that would be and therefore if it would be worth it or feasible for our project. The chip is a Cortex-M4, and we have an SVD file, CMSIS headers, and PDF documentation, but nothing like a device file or something that could be parsed automatically. I know giving effort or time estimations is super difficult, but would you guess a full-time developer can support a new device in hours, days, weeks, or months? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
I would estimate days to get You can create a minimal device file by hand and put it here (don't bother with modm-devices for now) and then start on implementing the If you want to start this, please open a PR even if it doesn't work at all, so I can help you directly. It's just way faster that way. |
Beta Was this translation helpful? Give feedback.
I would estimate days to get
modm:platform:core
running and then weeks to implement the peripherals.There is an (out of date) checklist here of what to do.
You can create a minimal device file by hand and put it here (don't bother with modm-devices for now) and then start on implementing the
modm:platform:core
module and using themodm:platform:cortex-m
module. A long time ago we added a new platform (ATSAM), but a lot of code has changed since then.If you want to start this, please open a PR even if it doesn't work at all, so I can help you directly. It's just way faster that way.