OS Abstractor

Section description:

What is OS Abstractor and Cross OS Development Platform
Can I start developing my application with the OS Abstractor APIs without a RTOS?
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 use OS Abstractor with my proprietary OS?
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 reused? 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?
How would you classify the OS Abstractor version of Linux? For example, do these versions have significant code reuse when compared to previous versions? Or, can they be considered child or rehosted versions of a mature product?
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?
There are three processes, A, B and C, created of the same priority and are in ready state. If process A create new task D, with a priority higher than other three processes, then will Process D start first? If priority D is lower, then will process A keep executing? If priority D is equal to other processes, will the application execution be in this series: A -> B -> C -> D -> A,,,, ?
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)?
How about sig_sem (signal semaphore)?
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?
What do I do if I get OS_ERR_RESOURCE error code when creating the OS Abstractor resources?
What do I do if I get OS_ERR_NOT_OWNER error code when using any OS Abstractor resources?
I see some functions inside the OS Abstractor library that starts with “INT_”. Can we also use these functions in our applications?
Is all access to a memory pool serialized among all threads (tasks)? Does each thread lock the memory pool when allocating or deallocating from that memory pool?
What happens if a memory pool is deleted while there are still open handles to that memory pool? Or what happens to the memory behind the pointers that are still held?
Does the application have direct access to OS Abstractor control blocks?
Does OS Abstractor dynamically allocate memory at run-time?
Can I set up a memory pool at a specific physical address and share it across multiple process and processors?
What are the important design goals of OS Abstractor?
Does OS Abstractor support DLL calls?
How can I use the process feature within a single or multiple executable images?
How can I pass parameters (such as void *, Char *, etc.) to task functions?
How is memory defragmentation handled in the OS Abstractor product on Linux and VxWorks?
Since I do not have a source code for OS Abstractor, it is difficult to understand your products. Is it possible to send me the full source code?
Which latest Linux kernel version do you support?
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 OS Abstractor product

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 A...
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 reused? 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...
Are there possible software modes where function or performance would be anomalous? If so, how does the software enter such modes?

OS Abstractor does not enter into any anomalous modes (though the target OS may do so, which is beyond OS Abstractor’s control). OS Abstractor returns failure codes if a function fails. For serious pr...
How would you classify the OS Abstractor version of Linux? For example, do these versions have significant code reuse when compared to previous versions? Or, can they be considered child or rehosted versions of a mature product?

OS Abstractor releases have significant code re-use when we add support to new OS. Once the product is validated for a specific OS (not specific OS versions), the code base is fully separated for each...
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

Yes. Please let us know what information that you would specifically need. Here are some examples of what we usually do: Test logs: We run the test suite and capture the log results under specific tar...