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
How Mapusoft OS helps to develop RTOS application?
What is benefit of AppCOE simulator?
What is the benefit of profiler?

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

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?

OS Abstractor API’s does not provide socket APIs, so the target OS needs to supply them. We have developed a BSD compliance wrapper for many netstacks on a custom solution basis if needed....
Why do the POSIX function names in OS Abstractor starts with “PX_” first?

This is intentionally done so that there would be no conflict at link time with the POSIX functions provided by the OS itself and the ones by the OS Abstractor. Please refer to the POSIX Interface sec...
Can OS Abstractor and Interface libraries be built as shared libraries? What about as DLLs?

OS Abstractor and Interface libraries can be built as shared libraries. This would be the recommended option if you develop multi-process applications. As far as DLL, the current release does not supp...
How is memory defragmentation handled in the OS Abstractor product on Linux and VxWorks?

OS Abstractor always prefers to use the OS defrag methods for pools created using OS_Create_Memory_Pool API. Under VxWorks, the pool management and defrag is handled by the OS itself. Under Linux, we ...
Which latest Linux kernel version do you support?

We basically support every version and distribution out there for Linux...
Linux comes with varity of scheduling policy. Do you support any of them? These may not be supported in underlying RTOS

We support, priority, time slice, combination and then run-to-completion scheduling at the OS Abstractor level. In addition we offer support for various scheduling done by OS like VxWorks, POSIX, etc....
Do you provide any NAND flash based file systems?

We provide ANSI interface to various file systems offered by the RTOS vendors...
What kind of security abstraction features are supported in the OS Abstraction layer? Ex: SMACK, SELinux, DAC etc

We do not have any encryption support. Access to objects contained in shared memory are restricted only when they are accessed using our APIs....
How Mapusoft OS helps to develop RTOS application?

MapuSoft provide the libraries and headers of the RTOS apis.The definition of these kernel resources api have the charateristics and functionality of the native corresponding RTOS apis. Internally the...
What is benefit of AppCOE simulator?

MapuSoft AppCOE IDE is an eclipse based IDE embedded with RTOS libraries and header. The benfits are : a. Help to develop RTOS applications using the RTOS apis, where the api libraries and the header...