Continue to Site

Welcome to our site!

Electro Tech is an online community (with over 170,000 members) who enjoy talking about and building electronic circuits, projects and gadgets. To participate you need to register. Registration is free. Click here to register now.

  • Welcome to our site! Electro Tech is an online community (with over 170,000 members) who enjoy talking about and building electronic circuits, projects and gadgets. To participate you need to register. Registration is free. Click here to register now.

Planning for Embedded Operating System

Status
Not open for further replies.

jab99407

Member
This is a hypothetical question to understand concept. Suppose we have Embedded System that is running operating system ( linux ) and we have source code of operating system available. Now we have to write user application program for the project. Before writing code for application program we do planing. I don't understand what planning is needed to write an application program.

I don't have any idea, how programmer decides How many tasks be or How many tasks should be
 
"Planning" is down to working out all the possible (and practical) tasks the end user may need the program to perform, whatever it is for. Then outline how to do each.

As long as the compiler in use can build for whatever operating system the program will be used on, the functional part of the program should be pretty much the same for any OS.

Any differences are likely down to different display types, if it's a graphical program; but you can largely work around that by using a display library such as QT, as long as your program is written to adapt to different display resolutions.

For compiling user programs on Linux, you don't need the whole source so much as the .dev versions of packages that will be involved in the compilation - they provide the header files and APIs for the various libraries.

If it's an embedded system you cannot add a compiler to, then you will need to cross-compile everything on a full system, with the embedded system set as the target.
 
As long as the compiler in use can build for whatever operating system the program will be used on, the functional part of the program should be pretty much the same for any OS.
What do you mean by functional part ? What will the function part for any OS ?
 
What do you mean by functional part ? What will the function part for any OS ?
The stuff it's intended to do for the user - word processing, playing music, a video game or whatever.

As opposed to the "hidden" side, the compiler library routines etc., and any graphics libraries if used, plus any other routines you need to add or customise that adapt the program to a specific type of computer system.
 
The stuff it's intended to do for the user - word processing, playing music, a video game or whatever.

As opposed to the "hidden" side, the compiler library routines etc., and any graphics libraries if used, plus any other routines you need to add or customise that adapt the program to a specific type of computer system.



Having explained all that what you are presenting to us does not look or feel like an embedded system.
 
Status
Not open for further replies.

Latest threads

New Articles From Microcontroller Tips

Back
Top