Cross-OS Development Platform

Section description:

What is OS Abstractor and Cross OS Development Platform?
What value does Cross-OS Development Platform provide?
How does the OS changer abstraction layer works? Is it VM? Does HW support needed?
Why not use an in-house abstraction?
Why develop portable code?
Why use a standardized OS interface?
Why support multiple operating systems?
Why should I leverage open source code in my platform?
Are the Cross-OS Development Platform APIs CPU dependent?
Which POSIX Standard is your product conformant to?
How do you support Process Model?
Could you give one example of target OS which gives hardware protection & true process and which does not provide?
Could you give any key difference between software process model and hardware assisted model as supported by OS abstraction layer? Please also give details of any key difference vs Linux process model
How do you support Memory Management - VM, Shared Library, demand paging etc? If yes, is it "arm-linux-eabi" complaint?
Could you give more details of support levels for "Shared Library" & "demand paging" in the OS Abstraction Layer?
How do you support Linux Extensions like - SysV IPC/cgroups/inotiy/futext/readahead/udev etc?
Is it possible for Mapusoft to check feasibility to implement these features at the OS Abstraction Layer?
Do you support extensions to include TCP/IP stack which may not be provided as part of underlying RTOS?
Do you support necessary WiFI, BT kernel Interfaces, so that native OS Connectivity frameworks can be re used? Ex: BlueZ, Connman etc.
How do you schedule process in multi-process application? Does this depend on target OS?
Are there possible software modes where function or performance would be anomalous? If so, how does the software enter such modes?
Do you have safety data that you can provide us with? Examples include but are not limited to: Traceability matrix, Code review records, Functional Testing Results, Stress Testing Results, Stability Testing Results, Condition/Decision Coverage
I generated source code for Windows XP as the target in AppCOE, compiled, and executed the program in VC++. Are the resultant tasks scheduled by the Windows scheduler?
If I select µITRON as a target OS, who schedules the task? Do the AppCOE libraries call µITRON dispatcher?
What is the default maximum stack size for QNX in the main thread?
If three same priority processes, A, B and C are created, which process starts execution first? When will it switch to another process?
If a task is created with priority 100, and it is changed to priority 50, then will the created task start executing? Is it not possible to set higher priority than the parent process?
OS Abstractor document says that we can use target OS native IO functions if I set MAP_OS_ANSI_IO to OS_FALSE. Does this mean that I can also call other target OS APIs from application program?
If target OS is uITRON, can I call set_tim (set system time API)?
If target OS is uITRON and it has Windows compatible file system and TCP/IP which support BSD Socket, then can the developer use open, close, read, write functions for file related operation?
If target OS is uITRON and it has Windows compatible file system and TCP/IP which support BSD Socket, can the developer use socket functions such as socket, accept, listen., etc by calling native OS system call?
Why do the POSIX function names in OS Abstractor starts with “PX_” first?
Can OS Abstractor and Interface libraries be built as shared libraries? What about as DLLs?
How is memory defragmentation handled in the OS Abstractor product on Linux and VxWorks?
Which latest Linux kernel version do you support?
Linux comes with varity of scheduling policy. Do you support any of them? These may not be supported in underlying RTOS
Do you provide any NAND flash based file systems?
What kind of security abstraction features are supported in the OS Abstraction layer? Ex: SMACK, SELinux, DAC etc

Find quick answers to your questions about Cross-OS Development Platform

How do you support Process Model?

We support process models for all the supported target OS (around 25 of them). If the target OS offers hardware protection & true process, then we will use that model, when it does not, we offer softw...
Could you give one example of target OS which gives hardware protection & true process and which does not provide?

Linux (also VxWorks 6.x and higher) provides hardware protection and full process. ThreadX (also MQX, etc.) does NOT provide full hardware protection and process support....
Could you give any key difference between software process model and hardware assisted model as supported by OS abstraction layer? Please also give details of any key difference vs Linux process model

The software process model uses private memory area that is dedicated to each process for local memory. It creates all resources (eg timers) by default private (however the scope can be changed to “sy...
How do you support Memory Management - VM, Shared Library, demand paging etc? If yes, is it "arm-linux-eabi" complaint?

Mapusoft support ANSI memory, dynamic pool memory, partitioned memory, tiered pool memory (dynamic memory build using layers of partitions like a wedding cake) and then shared tiered pool memory and a...
Could you give more details of support levels for "Shared Library" & "demand paging" in the OS Abstraction Layer?

Under NDA we can provide the reference manuals for our shared memory support. You can use the native Linux shared memory ‘as is’ in addition to what OS Abstractor offers. We do not do any demand pagin...
How do you support Linux Extensions like - SysV IPC/cgroups/inotiy/futext/readahead/udev etc?

Our level of support is posix 1003.1, 1003.1b and 1003.1c. In addition, the POSIX that we provide will automatically be able to take advantage of many of the real-time features from the specific OS Ab...
Is it possible for Mapusoft to check feasibility to implement these features at the OS Abstraction Layer?

Currently our OS Abstractor runs on over 25 different target OS and their versions. We need to know the additional levels of support and also on what needed target OS to be supported then we can work ...
Do you support extensions to include TCP/IP stack which may not be provided as part of underlying RTOS?

Yes. But for selected OS, we offer BSD compliance implemented using the net stack from the appropriate vendors offering. For example, we offer BSD complaint interface for Nucleus NET stack....
Do you support necessary WiFI, BT kernel Interfaces, so that native OS Connectivity frameworks can be re used? Ex: BlueZ, Connman etc.

As far as the device drivers itself, we do not offer our own across every OS. What we offer is a unix device driver I/O system framework to connect to many target OS so that the application code can b...
How do you schedule process in multi-process application? Does this depend on target OS?

We do not schedule process. All OS Abstractor processes are created equal and each thread within a process competes directly with the threads from the other. Also, we do not have a concept of parent/c...