Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
5 years ago.
Dependencies of various components.
We are looking to migrate to mbed os from FreeRTOS, we are working on safety critical systems, hence we would like to exclude all the unwanted/unused components from the target. I tried to start with a bare minimum configuration with only RTOS + file system + storage first. So I disabled all the features in .mbedignore, In this process, I found that the QSPI storage component is dependent on mbed-trace which in turn depends on nanostack-libservice, I was able to compile after removing storage and file system support. Continuing further I also noticed the USB MSD also has a same dependency tree. I would like to know how is the various components are dependent with each other on this eco system? Is there a way to understand the dependencies between the existing components, other than going through all of the code?
Just some thoughts. What coding guidelines/standard are you following? For a safety-critical system the guidelines should have something to say on this topic. For example, you often see guidelines to not include any unused code in your project and the mbed-os library includes a ton of unnecessary code for any given target. This could argue for forking mbed-os and physically deleting unused files rather than relying on build system to exclude them. Or MISRA C 14.1, There shall be no unreachable code. It seems like this could be interpreted as not allowing for some of the branching in core mbed-os functions (such as oscillator configuration). Of course this all depends on your specific project. If there is some sort of code review or firmware approval process it might be worth talking to those people and seeing if they can provide guidance as well.
posted by Graham S. 03 Apr 2019We are trying to use this mbed in medical devices, we are coming from bare metal environment. we are planning to do a dynamic analysis(i.e code coverage) for the mbed code, hence we don't want to include any of the unused unwanted features, I am trying to figure out if that is possible.
posted by siva l 04 Apr 2019