Category

Blog

CIP on display at ELC-NA

By | Blog

Last month, CIP participated in The Linux Foundation’s Embedded Linux Conference + OpenIoT Summit North America in Portland, Oregon. Around 730 embedded and IoT technologists from 360 companies and 31 countries around the globe attended the event to collaborate with experts on a wide range of topics of embedded Linux and industrial IoT issues. This was an increase from last year, making this an important industry event for embedded and IoT developers. In fact 75% of attendees already said they are planning on attending next year.

CIP, which sponsored the event at the Gold level, had a strong presence at the show. In fact, Philip DesAutels, Senior Director of IoT for The Linux Foundation, mentioned CIP during his keynote. He was speaking about the increasing trend of how hardware functionality is moving into software and identified CIP as an important Linux Foundation project that is mission critical for the future of smart cities and industrial IoT by providing long term software support.

Philip DesAutels giving his keynote speech at OpenIoT Summit

 

CIP also had a booth in the technical and demo showcase that featured demos from Renesas, which displayed the Real Time Linux Patch, and Plat’Home, which showed the CIP kernel connected to its IoT devices.  Each day of the conference, the showcase hall was packed with attendees who wanted to learn about the latest projects and products, view hands-on demos and interact with other community members. In fact, 98% of attendees survey said they visited sponsor booths.

Additionally, 15 CIP technical experts attended the event from member companies including Renesas, Hitachi, Siemens, Plat’Home, Toshiba and Codethink for a face-to-face TSC meeting, collaborate with other projects and to attend the 12 keynotes and some of the 90 breakout sessions.

Yoshitake Kobayashi, Senior Manager of Open Source Technology at Toshiba’s Software Development and Engineering Center and Chair of CIP’s TSC, also gave a talk about CIP’s mission to develop an open source industrial-grade software for civil infrastructure projects, starting with a 10-year Super Long-Term Support (SLTS) Linux kernel built around the LTS kernel. CIP expects to add other similarly reusable software building blocks that meet the safety and reliability requirements of industrial and civil infrastructure. CIP supports electrical and power grids, water and sewage facilities, oil and gas plants, and rail, shipping and transportation systems, among other applications. If you missed the session, you can watch the video here or view the presentation here.

Yoshitake Kobayashi presenting CIP to ELC attendees

 

Other CIP members Wolfgang Mauerer and Jan Kiszka, both from Siemens AG, also showed their technical passions for other topics. Wolfgang shared best practices, how to design and run automated statistical tests that capture relevant information, and how to properly evaluate the resulting data. Jan offered a deep dive into the Xenomai community, plans to revive it, maintaining the core and defining its relationship to PREEMPT-RT. The presentation is available here.

Wolfgang Mauerer from Siemens giving a talk about statistics and evaluation

Jan Kiszka from Siemens sharing plans to revive the Xenomai community

 

Overall, the CIP members interacted with other open source projects, learned more about IoT best practices, shared their knowledge about embedded and Linux and got a chance to have some fun.

For more about CIP, read the latest coverage:

Additionally, CIP will be attending Open Source Summit Japan on June 20-22 and the Embedded Linux Conference (ELC) Europe/OpenIoT Summit Europe in the UK on October 22-24. Stay tuned here for more details or come see us there!

CIP Member Spotlight: Codethink

By | Blog

The Civil Infrastructure Platform (CIP) project aims to speed implementation of Linux-based civil infrastructure systems, build upon existing open source foundations and expertise, establish de facto standards by providing a base layer reference implementation, and contribute to and influence upstream projects regarding industrial needs. CIP is driven by some of the world’s leading manufacturers of civil infrastructure systems and industry leaders including Codethink, Hitachi, Plat’Home, Renesas, Siemens, Moxa and Toshiba.

This spotlight series highlights CIP members and how they are contributing to open source software solutions that will benefit the world’s technical systems. Today, we highlight Codethink in a conversation with Agustín Benito Bethencourt, Principal Consultant and active CIP member.

What does your company do and what is your role?

Codethink is an independent engineering and consultancy services company. We specialize in system-level infrastructure to support advanced technical applications, working across a range of industries including finance, automotive, aerospace, medical and telecoms. We deliver critical technology services and solutions for international corporates. We develop and maintain system-level software and infrastructure within three practices: Enterprise, Devices and Automotive.

We have a wealth of experience in truly understanding the software development life-cycle and are happy to provide specialist expertise to slot into an existing project/product team, or to handle the turnkey supply of a complete solution to a managed budget, time or quality. We are experts in Free and Open Source Software (FOSS). We participate in upstream and are active contributors to a wide range of FOSS projects.

As a consultant at Codethink, I have two main roles: I help customers to transition from traditional embedded delivery models to modern ones, embracing Open Source best practices and agile principles, either in R&D or in production environments with a special focus on automotive at the moment. Additionally, I represent Codethink at The Linux Foundation and CIP project.

Why is your company investing in an open source “base layer” of industrial grade software?

Historically, Codethink has a very strong Open Source Software background. We believe that within the civil infrastructure industry there is plenty of room for sharing effort in the open, to create a commodity base system that can be maintained and shaped long term, enabling numerous stakeholders to participate and consume such software and knowledge for product development. Open Source ecosystems offer good opportunities for companies like Codethink to learn and demonstrate capabilities by actively participating in and contributing to CIP.

Why did your company join CIP?

Modern software practices are moving towards producing and deploying software fast enough so that it can be kept up to date. A significant part of our business revolves around that idea. There are environments though, in which following this approach is particularly challenging. The Civil/Social Infrastructure industry is one of them.

When it comes to software delivery or maintenance, for instance, the time perspective and economics for developing products that will still be operating in 50 years, is new to most of those coming from Open Source, especially when applied to safety critical environments. This is the main reason we wanted to participate in the foundation of CIP. The Linux Foundation project represents – for us – the perfect forum to challenge ourselves while helping others to embrace an Open Source mindset.

How are you currently active in CIP?

Our previous experience in open source community environments, helped Codethink to play an important role in shaping and foster CIP as an open source forum. As the project shifted its focus to the CIP kernel, Codethink led the testing and maintenance effort. We currently share the responsibility with Siemens, who is managing the real-time version of the CIP kernel we maintain.

Additionally, Codethink supports CIP on several other fronts such as promotion, content creation, participating in CIP governance forums, building strategic relations with other projects, etc.

How are you going to use the software?

Since Codethink is a consulting company, we don’t ship products based on CIP’s industrial grade software, but some of our customers do, especially those in industries where safety is critically important. For example, our Automotive OEMs customers are great candidates for the software.

What benefits have you seen or what do you expect to achieve?

In the kernel front, for instance, CIP takes advantage of all the work done by the kernel community on the 4.4 LTS process. CIP is adding additional effort to that process, contributing directly upstream instead of creating a separate and independent process where upstream is just an input, which requires additional effort to close the circle when contributing back to upstream. Our current simple process has proved to be very efficient.

Once the current LTS process ends, CIP will be maintaining such a critical component on its own. That will be the moment of truth for CIP. The same will apply to the rest of the components of CIP’s “base layer”, called CIP Core, which relies on Debian sources.

If the learning process we are currently following at CIP is successful, and the consolidation of the project reaches the required activation threshold, CIP will become a key forum for all those parties that ship long lasting Linux based products. Otherwise, the scope of the Initiative will be solely determined by the needs and efforts of the current members which, looking at the size of some of them, might be a bright future too.

Where do you see civil infrastructure systems in 20 years?

I see civil infrastructure systems following the general path that embedded industries and automotive are following, where the commoditization of part of the software stack is the only approach to tackle the increasing complexity, leaving enough resources to focus on differentiation factors that add value to customers. This process should push companies towards sharing more effort and resources. Open Source enables the healthiest environment in which to do so.

I think that the same principle will apply to safety critical related systems, although the adoption there will probably be slower but inexorable.

In summary, the overall transition from being Open Source consumers to producers first and contributors later, will take place faster than most think, just like it has in other industries before the Civil/Social Infrastructure.

Real-time patchset for the CIP Kernel

By | Blog

By Daniel Wagner, CIP member and kernel maintainer and Embedded Linux Developer at Siemens AG

CIP aims to establish a “base layer” of industrial-grade tooling using the Linux kernel and other open source projects. This base layer will be available for use by developers creating software building blocks that meet safety, security, reliability and other requirements that are critical to industrial and civil infrastructure projects.

As part of this mission, CIP provides super long term support (SLTS) for the kernel. This is an important base and the CIP kernel maintainers, like myself and Ben Hutchings, are working within various environments in order to meet Industrial Grade requirements. As we’re working on the SLTS, we realized that it was missing the real-time aspect of the operation system.

While the Linux Foundation’s Real-Time Linux collaborative project is working on getting the final features from the RPEEMPT_RT patchset into mainline kernel, there is no direct support a -rt flavor for the CIP kernel. There are stable real-time patches for 3.2, 3.10, 3.18, 4.1, 4.4 and 4.9. They are based on top of the LTS trees maintained by Greg Kroah-Hartman, Sasha Levin and Ben Hutchings.

The use cases CIP project is targeting have a life cycle of for more than 10 years. In theory, this is the time in which products shipped with the CIP kernel will be under maintenance. However, identifying and backporting relevant fixes becomes increasingly difficult as upstream kernel development diverges further from a stable branch. Any given SLTS branch is unlikely to be maintainable for more than 10-20 years.

Since the first CIP kernel is also 4.4 based, maintaining a variation of the 4.4-rt stable patchset is possible without too much overhead. The CIP real-time patchset will be follow the 4.4 stable-rt patchset as close as possible. The stable-rt patchset won’t gain new features (e.g. hrtimer rework, cpu hotplug rework, no_hz fixes) because backporting has a high risk of breaking stable-rt. Therefore, the stable-rt maintaining goals overlap with the cip-rt goals, which allows keep the variations of the real-time patchset smaller.

For more details, visit the CIP kernel maintenance wiki page. If you want to join the conversation or ask questions, subscribe to the CIP Dev List.

CIP Member Spotlight: Siemens

By | Blog

The Civil Infrastructure Platform (CIP) aims to speed implementation of Linux-based civil infrastructure systems, build upon existing open source foundations and expertise, establish de facto standards by providing a base layer reference implementation, and contribute to and influence upstream projects regarding industrial needs. CIP is driven by some of the world’s leading manufacturers of civil infrastructure systems and industry leaders including Codethink, Hitachi, Plat’Home, Renesas, Siemens and Toshiba.

This spotlight series highlights CIP members and how they are contributing to open source software solutions that will benefit the world’s technical systems. Today, we highlight Siemens in a conversation with Urs Gleim, Head of the Central Smart Embedded Systems Group.

What does your company do and what is your role?

Siemens is a global company providing products and solutions in the domains power generation and transmission, medical diagnosis, building technologies, industry, as well as rail and road mobility solutions. I head the “Smart Embedded Systems” group at the central unit “Corporate Technology”. This is a central expert center working for all of the business units as well as driving global strategic topics for the company.

How would you describe your company in a few sentences?

Siemens comes from the electrification and automation sector and is sometimes considered “old industry” in the middle of the transformation of a world of connected complex and heterogeneous systems. In the past, there were single purpose devices. But now, almost every device that has computing power, has an operating system that gets connected and can run different types of software. This transformation massively changes business models and technology. Siemens is one of those changed business models and technology.

Why is your company investing in an open source base layer of industrial grade software?

Today, we have lots of products that are Linux-based. Many of these products were developed independently, which resulted in a huge number of different Linux versions and distributions. With all of these different versions in use, developers work to maintain all them in parallel.

Furthermore, having more and more products connected increases the demand for providing security patches on short notice. Developers have worked in this way for a long time but this set-up is not scalable and cannot be managed like this in the future. To make matters more complicated, many companies are doing the same thing and maintaining several software stacks in parallel.

The solution to this complicated issue is the harmonization of the Linux versions used in products. This is called the base layer and it’s the foundation of what CIP is working on. As member companies collaborate on this base layer will save money, resources and time in the long-run.

Why did your company join CIP?

The idea of having an industrial-grade, long-term maintained Linux kernel was discussed for several years. At Siemens, there are some internal harmonization and cost effective work sharing activities but the real traction comes from close collaboration with upstream projects. From our point of view, this is only possible in an Open Source project driven together by partners who have the same problems. The Linux Foundation connected Siemens with other industry-leading companies that have the same vision. This is how we became a founding member of CIP.

How are you currently active in CIP?

As a founding member, Siemens has several people on the technical steering committee who help drive the strategic direction of the project. We are also active in CIP Core, in the testing effort, build environment and are driving the real-time support. Additionally, I am also the chair of the Governing Board.  

How are you going to use the software?

Based on the CIP kernel and CIP Core, we are building our internally used Linux distribution for different hardware platforms used in products. Beside the above mentioned cost savings, this harmonized approach also reduces OSS clearing of kernel and base packages as well as allows a central security & vulnerability management.

What benefits have you seen or what do you expect to achieve?

We expect reduced cost per product for patch and vulnerability management, maintenance, testing, and open source software clearing. We already see an increasing test coverage since the test tool chain and the tests are continuously improved by all members.

Where do you see civil infrastructure systems in 20 years?

Some of the ones we install now will still be here in 20 years. That’s why we need the Civil Infrastructure Platform.

 

 

When Nature strikes in 2018, CIP has your back

By | Blog

Natural disasters such as hurricanes, tornadoes, wildfires and floods have devastating effects on communities across our country. This year alone, we had back-to-back Hurricanes with Harvey, Irma and Maria and it took many months for the affected areas to begin rebuilding their electricity, water and waste management, communication and transportation systems after they were down.

These systems deliver essential services and social interactions that are crucial for daily life. They are among what IHS estimates are  20 billion connected devices this year that will continue to increase dramatically next year and onward. These connected systems and devices are being adopted in a widespread of different industries that are stored at the edge, which means edge computing at every level will become the norm. This trend highlights the urgent need for security, reliability and feature-rich software that will maintain these systems.

This exemplifies the mission of the Civil Infrastructure Platform (CIP). CIP aims to provide a base layer of industrial grade open source software components, tools and methods to enable long-term management of critical systems. Hosted by The Linux Foundation, CIP is driven by some of the world’s leading manufacturers of civil infrastructure systems such as Codethink, Hitachi, Plat’Home, Renesas, Siemens and Toshiba. These member companies are working together to create a reliable and secure Linux-based embedded software platform that can be sustained more than 10 years and up to 60 years.

CIP Members at ELC-Europe

 

CIP has already made huge strides since launching in April 2016. In fact, this year CIP members created the CIP Core, a ​reference ​minimal file system ​that offers a customizable environment that developers can use to test the CIP kernel and core packages and Board AT Desk (B@D) v1.0, a customized and easy to deploy instance of the kernelci.org and LAVA projects that allows developers to test Linux kernels on boards connected to their own development machines using the tooling provided by kernelci.org. In addition, CIP also continued to maintain the kernel and make ongoing updates, bug fixes and support maintenance.

As 2018 quickly approaches, CIP will continue its momentum. The new year will bring a focus on functional safety, an exploration of how CIP can help safety standards and certification in automobiles and more collaboration with industry influencers like Debian and other open source projects. CIP will also be making testing efforts more harmonized with the Linux Kernel community, particularly with LTS maintained by Greg Kroah-Hartman. CIP is planning to build an infrastructure to contribute the test results to LTS. Ultimately, these efforts will get CIP closer to its mission of creating industrial grade software that is resilient, secure and reliable so that when weather disasters strike, there won’t be as much of an issue to bring systems back online.

 

CIP Member Spotlight: Renesas

By | Blog

The Civil Infrastructure Platform (CIP) project aims to speed implementation of Linux-based civil infrastructure systems, build upon existing open source foundations and expertise, establish de facto standards by providing a base layer reference implementation, and contribute to and influence upstream projects regarding industrial needs. CIP is driven by some of the world’s leading manufacturers of civil infrastructure systems and industry leaders including Codethink, Hitachi, Plat’Home, Renesas, Siemens and Toshiba.

This spotlight series highlights CIP members and how they are contributing to open source software solutions that will benefit the world’s technical systems. Today, we highlight Renesas in a conversation with Takehisa Katayama, Manager at Renesas Electronics Corporation.

What does your company do?

Renesas Electronics Corporation delivers trusted embedded design innovation with complete semiconductor solutions that enable billions of connected, intelligent devices to enhance the way people work and live—securely and safely.

To develop a safer, healthier, greener, and smarter world, Renesas offers three layers of solutions to provide optimal services with added value for customers in our three focus domains: Automotive, Industrial and Broad-based.

What is your role?

In Renesas, I am responsible for developing/maintaining the Linux kernel and open source software components that work on Renesas RZ/G MPU targeting industrial market.

In the CIP project, I am a member of the Technical Steering Committee (TSC) and the Governing Board as representative from Renesas. Renesas provides RZ/G1M boards as a reference board in the project so we can aggressively contribute the drivers upstream based on “upstream first” policy. We also contribute to advance Board At Desk (B@D), CIP’s testing environment, which just launched a new version.

Why did your company join CIP? Can you provide a use case scenario?

Devices currently used in the industrial field are getting more advanced with networking capabilities, as result of the standardization of IoT and Industry 4.0, and multimedia functionalities such as video and graphics processing. An increasing amount of Renesas customers are considering making the switch to Linux because that OS supports a wide array of software for implementing such functions.

However, in the industrial field, after the introduction of equipment, it is necessary to operate for a long period of time, usually more than 10 years. In addition, improvement of reliability and real-time operation is also a requirement.

The CIP project was launched to provide a platform that will meet this need. Renesas considers this project extremely important in terms of providing industrial solutions to support the “smart society” of the future. As a semiconductor manufacturer, by participating in the project, Renesas aims to substantially reduce the additional development and maintenance burdens for customers associated with boosting the reliability and real-time responsiveness of software for industrial devices.

How are you currently active in CIP?

Renesas was the first semiconductor manufacturer to join the CIP project and help provide an industrial grade software base layer for the civil infrastructure system supporting the lifeline. In addition to these activities, Renesas actively carries out activities to provide super long-term support, high reliability, and robust security for embedded devices for industrial use.

How are you going to use the software?

In October 2016, Renesas released the “RZ/G Linux Platform” which enables manufacturers of industrial products to reduce the Total Cost of Ownership (TCO) targeting the domestic Japanese market.

Renesas built upon this by releasing a new RZ/G platform this month based on CIP SLTS kernel for worldwide. This release is a direct result of our CIP activities and the collaboration with other members. Renesas is expecting that Linux will become more popular for embedded industrial products that require high reliability.

What benefits have you seen or what do you expect to achieve?

RZ/G is targeting the industrial market and almost all customers in this field have demands like fixing security holes to ensure a stable kernel for long term operation. The CIP kernel maintenance policy meets the above demands by backporting the latest functionality for 5 years and applying “Bug-fixes” to current kernel for 15 years or more. Renesas is expecting CIP and members to help respond to these various demands and ensure long-term operation.

Where do you see civil infrastructure systems in 20 years?

We hope we can see everywhere in the industrial market.

CIP Launches CIP Core

By | Blog

Author: Daniel Sangorrin, CIP TSC member

Today, at Embedded Linux Conference Europe, the CIP Project announced the new CIP Core. The CIP Core project aims to provide minimal reference file system images and SDK’s to test and demonstrate the use of the CIP kernel and the CIP Core packages, a selected set of open source software components that require super long-term support.

Within the open source base layer, the CIP Core connects the CIP Kernel with non-CIP packages (see figure 1).

The implementation of the CIP Core is based on the Deby distribution, a reproducible and maintainable embedded Linux distribution based on poky. Deby overlays meta-debian on top of poky to build file system images out of Debian long-term supported source code packages. The associated source code (metadata) is available on the CIP Core repository and this first release contains support for the following CIP reference hardware:

  • iWave RZ/G1M Qseven Development Kit
  • Beaglebone Black
  • QEMU x86_64
  • DE0-Nano-SoC development kit.

Users of CIP Core can easily extend or customize the reference file system by adding some of the packages already supported by Deby (non-CIP packages).

For more about CIP Core, visit the wiki page, follow the quickstart or check out the source code. You can also register in the CIP’s public mailing list to learn more about CIP’s technical roadmap and participate in discussions.

CIP Launches B@D v1.0

By | Blog

The Civil Infrastructure Platform (CIP) project, hosted by The Linux Foundation, announces the publication of a new version of Board At Desk v1.0, a customized and easy to deploy instance of the kernelci and LAVA projects that should allow developers to test Linux kernels on boards connected to their own development machines using the tooling provided by one of the most successful Open Source testing projects.

Board at Desk (B@D) v1.0 is provided in two forms:

  • As a vagrant VM recipe.
  • As a VM image, widely called a B@D box.

Please visit the CIP Testing project Download page to download the latest Board At Desk (B@D v1.0) box.

With this effort, the CIP project is moving towards a “shared and trusted testing” targeting not just those directly involved in maintaining the CIP kernel but any kernel developer that has physical access to a board. This reduces deployment, configuration and maintenance costs. B@D introduces a “local” approach to kernelci.org which is a distributed service centrally managed. In addition, CIP intends to increase the number of developers and organizations willing to participate in upstream kernel testing by providing a simple mechanism to evaluate the technologies developed by that community (LAVA and kernelci) which CIP considers upstream.

Some of the most important new features shipped with this B@D release include:

  • LAVA has been updated to 2017.7 version.
  • B@D now works on Windows 10 systems.
  • B@D now works behind a webproxy.
  • initramfs is now built locally, increasing reliability.

Newer version of LAVA

The LAVA community releases a new LAVA version every month. CIP testing team have updated Board at Desk LAVA version to 2017.7, released this past July. It comes with many new features, enhancements and bug fixes that allow the CIP testing project to introduce more verbose reports, prevents issues related with partitions being filled with system logs, etc..

B@D supports Linux and Windows as host OS

The previous version only supported Linux based systems as host OS. This new version of B@D also supports Windows 10 expanding the potential targets to those engineers who use this proprietary operating system in their development machines.

B@D now works behind a webproxy

Many organizations works behind a webproxy. B@D needed to give an answer to this use case, popular among CIP Members. Thanks to some contributions from Daniel Sangorrin, a Toshiba developer, Board at Desk now works behind a webproxy.

initramfs is now built locally

Previously Board At Desk was using the initiramfs provided by Linaro in their infrastructure. This created in B@D a dependency on the network connection latency that, under certain circumstances led to errors due to timeouts. Now initramfs is built locally which improves the speed of the tests, removing that need to access to internet.

In addition to the above, other features have been added and several bugs has been fixed, making Board at Desk more robust and reliable than before. Further information about this new Board At Desk (B@D v1.0) release can be found at the B@D Feature Page.

If you are interested in testing kernels using Board at Desk, meet the developers at the cip-dev mailing list. If you find bugs in KernelCI or LAVAv2 themselves, please report them upstream. If you find them in the configuration or any of the previously described topics, please report them in the CIP-testing bug tracker. More general information about the CIP testing project can be found in the CIP wiki.

Join CIP at Embedded Linux Conference Europe

By | Blog

Are you planning on going to the Embedded Linux Conference Europe? ELCE, located in Prague, Czech Republic from October 23-25, 2017, is the premier technical conference for companies and developers using Linux in embedded products. Traditionally, ELCE has had one the largest collection of sessions dedicated exclusively to embedded Linux and embedded Linux developers.

This year is no different. Vendors and kernel and systems developers will collaborate with the maintainers and experts building the applications running on embedded Linux platforms. This year, developers will have the opportunity to learn about the Civil Infrastructure Platform (CIP) and how to get involved with industry leaders such as Codethink, Hitachi, Plat’Home, Renesas, Siemens and Toshiba.

The Civil Infrastructure Platform (CIP) is creating a super long-term supported (SLTS) open source “base layer” for industrial grade software, components, tools and methods that will help key systems have a more sustainable workflow and less outdated software. The base-layer consists of an SLTS kernel, a basic set of open source software and standardization concepts that enable long-term management of technical systems such as electric power, transportation, water and waste management, healthcare and communication.

CIP Members Yoshitake Kobayashi, Senior Manager of Open Source Technology Department at Toshiba, and Urs Gleim, head of the Research Group, Smart Embedded Systems at Siemens Corporate Technology, will provide an update CIP on Wednesday, October 25 from 9:50–10:10 a.m. in Congress Hall 1.

They will introduce attendees to the project’s strategy, use cases, technical roadmap, policies and milestones. Participants will also get a look into technical details, development tools, testing and more for the CIP SLTS kernel. Add this to your ELCE schedule here.

CIP also invites Linux developers and maintainers to open workshops in the Athens room at the Hilton Prague that takes place before the conference begins. On Sunday, October 22, CIP members will lead three workshops for testing, collaboration and Q&A sessions. The workshop schedule is below. For more information or to register for a session, visit the CIP wiki page.

Workshops on Sunday, October 22:

2 p.m.: AGL Testing & B@D Collaboration Discussion

4 p.m.: B@D 101

5:30 p.m.: CIP Kernel Maintenance Q&A

Additionally, CIP members will host a Developer’s Meeting on Tuesday, October 24 at 1 p.m. The meeting is open to any and all developers interested in CIP, LTS, Linux maintenance and Debian. For more information, visit the CIP wiki.

Live demonstrations will be on display at the Embedded Linux Conference Europe taking place on October 23-25, 2017. The CIP booth (Booth M17) will be filled with innovative member solutions from Codethink, Plat’Home, Renesas, Siemens and Toshiba.

Please see below for the demo descriptions:

  • Renesas will be showcasing the CIP kernel in action with real-time capabilities of the RZ/G1M SoC with an iWave iwg20m board. The demo will display the benefit of low and stable latency, and the value of RT-PREEMPT patch set.
  • Siemens will link traditional industrial computing with Internet-of-Things (IoT) technologies based on IOT2000 devices, which are part of CIP’s long-term support commitment. The demo shows how to combine state-of-the-art sensor technology with proven, solid industrial approaches, and uses novel software mechanisms to describe automation processes.
  • Codethink Ltd will showcase at the event Board At Desk v1.0, released a few days earlier, the CIP testing environment based on KernelCI, so any developer can test a kernel or a simple system locally in a board connected to her machine and share the results and logs. During the demo, the latest CIP kernel will be tested on the Beaglebone Black and  Renesas RZ/G1M boards.
  • Plat’Home will show the demonstration with IoT. It runs on original product, “OpenBlocks IoT VX1” with CIP kernel. OpenBlocks IoT VX1 is the compact server for IoT gateway. It uses Environment Sensor made by OMRON.  It shows environment values at venue, such as temperature, humidity, atmospheric pressure, sound pressure, illuminance and ultraviolet radiation.

If you’re attending ELC Europe, we look forward to seeing you there. If you’re not, stay tuned. We’ll add pictures and updates on the our blog post and @CIP_Project.

 

CIP Member Spotlight: Toshiba

By | Blog

Civil infrastructure systems are the core of our daily lives. These technical systems deliver essential services such as electric power generation, transportation, water and waste management, healthcare and communication. The Civil Infrastructure Platform (CIP) project, hosted by The Linux Foundation, aims to establish a base layer of industrial grade open source software components, tools and methods to enable long-term management of these systems. CIP is driven by some of the world’s leading manufacturers of civil infrastructure systems and industry leaders including Codethink, Hitachi, Plat’Home, Renesas, Siemens and Toshiba.

Photo by Creative Commons Zero

Launching today, this blog series will highlight CIP members and how they are contributing to open source software solutions that will benefit the world’s technical systems. Please read on for the first member spotlight – Yoshitake Kobayashi, Chief Specialist of Software Engineering and Technology Center for Toshiba Corporation.

What does your company do?

Toshiba is a company that channels world-class capabilities in advanced electronic and electrical product and systems into four focus business fields: Energy that sustains everyday life, that is cleaner and safer; Infrastructure that sustains quality of life; Storage that sustains the advanced information society; and Digitalization that sustains optimized and secure society. Guided by the principles of “Committed to People, Committed to the Future,” Toshiba promotes global operations and is contributing to the realization of a world where generations to come can live better lives.

What is your role in CIP?

I am the chairman of the CIP Technical Steering Committee (TSC) and also a member of the Governing Board as Toshiba’s representative. As a part of my activity as TSC chairman, I have given presentations in various conferences such as the Embedded Linux Conference and the Open Source Summit.

Toshiba is also contributing to several projects inside CIP, such as the reference implementation of the base-layer (CIP Project-X) and the testing effort (Board@desk). Outside of CIP, Toshiba is also contributing to the Debian Long Term Support (LTS) project, whose source code is used within the CIP Project-X.

Why is your company investing in an open source “base layer” of industrial grade software?

Toshiba wants to contribute to a sustainable society on business domains such as civil infrastructure systems. In recent years, civil infrastructure systems are changing towards more connected architectures and using open source software. Toshiba products, which have rather long life time spans, need to guarantee high levels of reliability and security. To achieve our goals, we are committed to the creation of a secure, reliable and maintainable software platform for infrastructure systems.

Why did your company join CIP? Can you provide a use case scenario?

As one of the founding members the CIP project, we believe that collaborating with other leading companies that have similar requirements, will help us develop a common base layer more quickly and efficiently. By sharing the cost of developing this base layer, Toshiba will be able to focus more on the added value in our products.

How are you going to use the software? What benefits have you seen or what do you expect to achieve?

Toshiba will use the CIP base layer as the core for creating the operating system for our products. Since CIP aims to provide a super long term support (SLTS) for its base layer, we believe this is one of the most critical concepts for us. Additionally, we want to solve other common problems that affect our systems such as real-time support or the Y2038 issue, an issue due to a limitation of the maximum number of seconds (relative to Jan 1, 1970) that can be represented in a 32-bit signed integer.

Where do you see civil infrastructure systems in 20 years?

Linux will be the master of the world and everyone will be using it.

To learn more about CIP, please see the below resources: