Start joining the needs analysis phase
Feasibility study of MyOS (51) has ended. From all aspects of information proven, I can do a set of operating systems in two months. The reasons are as follows:
1. First, the reserves of basic knowledge are basically enough. If there is an unknown technical issue during practice, it is also possible to complete learning and accumulation within the time range of tolerance. Because the theme knowledge architecture has been completed. Therefore, the technical risk is I can overcome.
2. Time risk takes into account all the time it is used to do this, so it should be enough in accordance with two months.
3. In terms of fund risk, for the design of 51, it is intended to purchase a 51 EVB public. To make software testing, the price should be around 200 yuan, it is I can withstand. Other places where you use money may be more buying two technical books. Therefore, the risk of funds I can withstand.
4, as for other risks, such as if I specifically designed a PCB for verifying my operating system. It is necessary to take into account the risk of outsourcing the drawbox.
For requirements, MyOS (51) must have the following features:
Multi-task concurrent execution, must!
The system has real-time, the primary target is a system with a task deadline while having a friendly interactive interface.
The system has a sickness, and for a particular item, a partial function using Myos (51) can be cut.
Because the operating environment is predictable, it is only a static establishment task.
In order to take advantage of existing resources, the API of the driver and the operating system is as long as possible with the popular RTOS. Specific selection of Linux or UC / OS-II or SMALL RTOS51, waiting to argue in detailed design.
If the energy is perhaps, consider the design of MYOS (51) into a distributed operating system, coordinated and communicating with a 64K RAM as public memory.
Considering the 51-series MCU memory is small, some relative luxury system functions use XDATA when prepared.
