prevention_is_better_than_cure

FAQ

When servicing our customers, some topics show up more often than others. Below you can click through the database of the most frequently asked questions, and check out the answers that we provide.

Functional Debugger

Are there requirements on other tools / components?

The Crosshairs tools (Debugger and Interface Designer) require the Microsoft .NET framework version 3.5 to be installed.

Which architecture(s) are supported?

Currently the Texas Instruments C2000, Stellaris ARM Cortex M and MSP430 architectures are supported. For more information or questions regarding other architectures, please contact our support team.

Interface Designer

Are there requirements on other tools / components?

The Crosshairs tools (Debugger and Interface Designer) require the Microsoft .NET framework version 3.5 to be installed.

Does a deployed interface require Crosshairs tools to be installed?

There are no dependencies on Crosshairs tools or other 3rd party products for deployed interfaces. Deployed interfaces are self-contained, standalone executables.

Which architecture(s) are supported?

Currently the Texas Instruments C2000, Stellaris ARM Cortex M and MSP430 architectures are supported. For more information or questions regarding other architectures, please contact our support team.

Commros

Are there C and C++ versions of the Commros library?

Yes, Commros is available in both C and C++ libraries so there is no need to use mixed-mode (i.e. C/C++) in your application.

Can Commros be integrated into existing applicatioins?

Yes, the Commros library may be integrated at any point in an application's lifetime.

Most users integrate the library at an early stage and leave it in throughout the lifetime of the application.

Can Commros be used with an RTOS?

Yes, Commros may be integrated into applications that use an RTOS. A typical scenario is implementing the Commros service handling as a low-priority task within the application.

Note that an RTOS with MMU/Memory protection may limit the ability of Commros to read and access memory freely.

What is the footprint of the Commros library?

The footprint of the Commros library varies by architecture and configuration. The Commros library is available in Small, Regular and Full versions and for the C2000 architecture they range in size from 800 bytes to about 8k bytes.

For details regarding specific architecture / configuration combinations, please contact our support team.

Which architecture(s) are supported?

Currently the Texas Instruments C2000, Stellaris ARM Cortex M and MSP430 architectures are supported. For more information or questions regarding other architectures, please contact our support team.

Which communication methods are available?

Out of the box, serial and Ethernet communication is available. For inquires regarding other communication methods, please contact our support team.