There are two approaches can use in software design and implementation:
Top-down design
Bottom-up design
I want to follow Top-down approach to design RTOS
For Example:
Code:void main(void) { init(); while (1) { getEvent(); doEvent(); } }
I want to breakdown project into many source files. which files and How many source files should I add into my project ? I will try to work on more detail when I decide source files in project
Something as complicated as an operating system, even a tiny one, begins with pencil and paper.
Not deciding on a list of filenames for source code.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
sure I will start with paper and pencil but I don't have any idea how to start with top down approach. Can you help meOriginally Posted by Salem
Have you ever designed and written any program consisting of more than one file and taking longer than a week to complete from start to end?
If you haven't, an RTOS is a tough choice.
> Can you help me
How To Ask Questions The Smart Way
Start reading.
top down approach in software engineering at DuckDuckGo
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
When I was beginner I was having trouble to write code for microcontroller but now I can write code for any peripheral of microcontroller. I can write code for whatever device is connected with microcontroller
It's not necessary to use OS in any embedded system It's depend on the programmer choice What the way he want to control device with OS or without OS. I can do without OS. that's why I want to learn to do it with OS
I want to make tiny OS to control devices connected with microcontroller
OS control resources of hardware such timer, memory
Application program run on OS
Last edited by Player777; 09-05-2021 at 12:08 AM.
