Find quick answers to your questions about Cross-OS Development Platform
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...
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...
OS Abstractor does not do scheduling on any port. We use the OS scheduler. However, we configure the threads to be real-time priority (e.g. on Windows we use the threads priorities that are normally n...
µITRON scheduler will schedule the thread....
The stack size defined under OS Abstractor for QNX is as follows: #define OS_MIN_STACK_SIZE 16384 #define OS_MAX_STACK_SIZE 0xffffffff The above defines are in cross_os_def.h. It is recommended that y...
OS Abstractor processes do not compete with each other, but only the threads within them. The process will be started First In First Out (FIFO)....
You can set any priority when creating tasks. If you want it to run immediately, you pass along the flag parameter START, it will resume, irrespective of the priority....
You should be able to use any native APIs directly from the target OS (as long as the API names are not the same)....
You should be able to set_tim native uITRON API, however, that line of code will not be portable. It is recommended to use the clock routines provided by either the OS Abstractor APIs or the POSIX API...
The developer has the options to use OS_open, OS_close, etc (OR) they can set MAP_ANSI to TRUE and have open(), close() calls map to OS Abstractor APIs. The developer also has the option to use both A...