Studio:How much time and how many resources are required to get STRIDE running in a typical embedded environment?: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Text replace - 'Category:FAQ' to 'Category:Studio:FAQ') |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
A typical environment using a common embedded RTOS can be up and running in a week or less. Custom RTOSes or environments using messaging or host-based simulators will require more time to integrate the necessary support. During this period, S2 typically works with a customer’s developer who is knowledgeable about their software architecture, RTOS primitives, and software build environment. | A typical environment using a common embedded RTOS can be up and running in a week or less. Custom RTOSes or environments using messaging or host-based simulators will require more time to integrate the necessary support. During this period, S2 typically works with a customer’s developer who is knowledgeable about their software architecture, RTOS primitives, and software build environment. | ||
[[Category:FAQ]] | [[Category:Studio:FAQ]] | ||
Latest revision as of 22:05, 20 August 2009
A typical environment using a common embedded RTOS can be up and running in a week or less. Custom RTOSes or environments using messaging or host-based simulators will require more time to integrate the necessary support. During this period, S2 typically works with a customer’s developer who is knowledgeable about their software architecture, RTOS primitives, and software build environment.