Report
2 years, 7 months ago.

Migration from mbed OS 3

migration from mbed OS 3 doesn't seem to be straight forward, is it even recommended? one of my project makes heavy usage of different yotta modules, is this still supported? Will mbed 3 still be maintained?

Question relating to:

Comment on this question

2 Answers

2 years, 7 months ago.

Hi Martin,

Look out for some articles around upgrade migration from mbed OS 3 over the next month, once the event scheduler library is fully released. Most of the drivers APIs are remaining the same (even though the internals have been upgraded), so the main change is moving from MINAR to a MINAR-like library that can be used in any thread (of course, your application could have just one thread) - or of course you may want to take advantage of some of the RTOS features.

Component library modules are supported and used, and are the preferred way to pull in and compose an application around the mbed OS core. They just directly reference other repos to pull in at specific versions to make things simpler and reproducible (i.e. no step via an archive registry), but assuming you have your modules already in git or mercurial repos (say Github), that is all supported and the tweaks needed to the module to make that work should be minimal.

Thanks! Simon

2 years, 7 months ago.

Is yotta still used under there somewhere? What about targets?


To post an answer, please log in.