Softwareentwicklung

Software Development

Your complete ready-to-use system: With the Garz & Fricke Group to a complete ready-to-use 

Trust the decades of experience of the Garz & Fricke Group specialists and our modular and comprehensive approach for software development. We offer you exactly the depth of service you need on the way to your operational system.

We supply complete "application-ready" platforms with turnkey pre-integrated operating systems including the required drivers and tools. This relieves you, for example, of tiresome bootloader and operating system integration. Creating your own Board Support Packages (BSPs) is no longer necessary.

If you have nothing to do with software development at all or want to buy a complete turnkey system including application software from us, this is no problem: With e-GITS as part of the Garz & Fricke Group, we offer you the services of a specialist for customized software development directly from one source. You can find out more about e-GITS here.

To make software development and distribution even easier for you, we rely on GNU/Linux as a proven standard. Other platforms are possible on request.

With GNU/Linux as an open-source system, the continuous development is partly carried out by the community, whereby Garz & Fricke also constantly maintains and develops its BSP. All our current embedded systems are based on Yocto™. We support different kernel versions, both manufacturer-specific, but also mainline. Furthermore also kernels with the real-time extension PREEMPT_RT.

Software development

Show all answers
Hide all answers
  • What is the year 2038 problem?

    Unix-based 32-bit systems represent the time through the seconds that have passed since January 1, 1970, and store it as a signed 32-bit integer value. Accordingly, the period is limited and there will be an overflow on 19 January 2038. This overflow can have a negative impact especially on poorly implemented timeouts in the software.

    Is this answer helpful?  

  • Which software components are affected by the 2038 problem?

    The overflow problem can affect many software components, such as libraries, compilers, APIs, services, applications, file systems, and also network protocols. However, timeouts in the Linux kernel and drivers are based on jiffies rather than clock counter. Since, according to current information, the Garz & Fricke Linux systems do not use cron jobs or something similar the systems should continue to work stable. However, an incorrect time will be displayed.

    For other applications or any customer software, it depends on the concrete implementation of the timeouts, whether the "Year 2038 problem" has a negative impact.

    Is this answer helpful?  

  • Will an update be necessary for the 2038 problem?

    This problem is already well-known in the Linux community and is currently being worked on in the kernel and in other libraries such as the glibc. It is recommended to create options for software updates in order to be able to carry out any necessary software updates if the appropriate software will be available for the kernel used. It should also be taken into account to change to newer devices or OS versions with a more recent kernel to increase the chance to get appropriate software support in the future. According to the current status (August 2019), however, no date can be mentioned. It will probably take a few more years for the above adjustments to be completed.

    Is this answer helpful?  

  • Do adjustments need to be made to the customer application for the 2038 problem?

    It will not be enough to do an OS update. As mentioned above, the application's time-out functions must be checked. If they are implemented in a way that they can be affected by the overflow, the functions must be reworked. It must also be taken into account that any customer applications in the case of a system update has to be compiled and linked against the new libraries, etc. again, even if no timeout functions are used. It is also possible to carry out tests beforehand by artificially setting the system time to an appropriate date in order to force the overflow and to observe possible effects on the application.

    Is this answer helpful?