µCross can be seen as the glue-layer between the BSP and the customers specific application:
µCross compliments the BSP that usually comes with the hardware board - either from the board or chipset manufatcurer. Only the hardware specific parts of the BSP are needed, i.e. bootloader, kernel and eventually specific drivers. Everything else is supplied by µCross.
Currently µCross supports the following architectures:
µCross is completely package oriented, based on the specially for embedded and mobile use tailored tool "opkg". All components of µCross are installed package by package into the target system. This enables package oriented updates also in the field after the product has been deployed - instead of having to rewrite the whole filesystem image.
The feeds currently contain more than 6000 packages for each architecture supported by µCross.
Creating a runtime system can be a time consuming task. Many tools depend on other tools or additional libraries. Sorting all those out manually can become quite an effort on its own. Concerting all of those poackages together into a system that starts up cleanly and behaves as expected will be the next challenge, maintining this system the on after that.
µTIB lowers the effort tremendously. Using µTIB you can create a simple abstract description of which functions you to see in your runtime system and µTIB will take care about all the dependencies. µTIB also allows to include custom files, e.g. a customer application, specific configurations, etc. As a result µTIB creates within a few minutes a ready-made runtime system either as .tar.gz archive or flashable-image, ready to deploy.
Using µTIB is simple and does not require any up-front knowledge. A simple GUI helps to get started.
µCross is based upon man years of experience from the open source OpenEmbedded project and more than 15 years of business experience in the embedded field of kernel concepts.