With the aim of reducing development costs and cyber risks, two years ago we decided to switch from C/C++ to Rust for the application layers.
 
This presentation provides feedback on the use of Rust for the development of an electric vehicle charging station, carried out in collaboration with an automotive equipment manufacturer. The system is deployed on an embedded Linux platform that implements an application framework optimised for security.
 
We will outline the specifics of using Rust in this context, the advantages it offers, and the challenges we encountered during development and integration, such as interfacing with asynchronous C libraries and the lack of mature, certified Rust cryptographic libraries.
 
We will open the discussion on a review of the Rust community's current efforts to address these challenges.

 
Project's Github page<a href= "https://github.com/tux-evse">ici</a>
Presentation's PDF version <a href="https://iot.bzh/download/public/2025/rust_ev_charger.pdf">here</a>

Rust in embedded systems: feedback on the development of a charging station for electric vehicles

The rapid adoption of complex connected embedded systems, such as electric vehicle (EV) charging stations, telematics units, or battery controllers, has increased the need for a robust approach to cybersecurity and auditability. 

 

This talk delves into the application of cybersecurity methodologies to embedded Linux systems, using the design of an EV charging station as a representative example.
It will explain how the security of an EV charger can be enhanced both on the runtime side—using a microservice architecture for software component isolation and fine-grained permission control, alongside a memory-safe language—and on the supply chain side, by ensuring all software components are described with associated vulnerabilities and that the build platform itself is secure.

 

- [COB25 - Cybersecurity of an EV charger.pdf](https://iot.bzh/download/public/2025/Cybersecurity_of_an_EV_charger.pdf)

thumbnail_COB_vert@2x.png

COB_vert@2x.png

Cybersecurity and auditability of embedded systems - the case of an EV charger

thumbnail_Fulup_300.JPG

Fulup_300.JPG

Asymmetric multiprocessing (AMP) leverages heterogeneous cortex integrated on a single System on Chip(SoC). Typically embedded boards run on ARM systems where AMP provides a native hardware isolation in between classes of CPUs. Linux runs on a set of Cortex-A while safety operations are delegated to realtime Cortex-M/R. Both world exchanged data through a pool of shared mailbox/memory. This model is an efficient approach to mitigate cybersecurity/safety cohabitation and allows one to distribute software services to different types of CPU. Typical safety related operations run on a dedicated DSP, AI accelerator or a 32bit microcontroller through a realtime micro-kernel, while Linux handles higher layers of applications and cybersecurity on multiple 64bit cores.

 

- Slides : [asymetric_multiprocessing.pdf](https://iot.bzh/download/public/2025/asymetric_multiprocessing_CYBER_On_Board_2025.pdf)
- White paper : [asymetric-multiprocessing-white-paper.pdf](https://iot.bzh/download/public/2025/asymetric-multiprocessing-white-paper.pdf)

Mitigate cybersecurity/safety constraints with asymmetric multiprocessing

fosdem-2025-sbom_opt.jpg

In the context of a Linux software factory dedicated to building embedded software, we will discuss the choices and challenges we encountered in integrating SBOM file generation into a software supply chain involving many packages.

 

The talk will begin with a brief overview of the various formats (SPDX, CycloneDX, ...), tools and ecosystems surrounding SBOM, highlighting the essential knowledge required to integrate these features into a supply chain. Then, this presentation will address the challenges we faced in retrieving accurate and reliable information to generate various BOMs: How do we ensure the data is correct and up-to-date? What are the common pitfalls in data collection? Which format best suits your needs, and what are the trade-offs between different solutions? Finally, we will explore the importance of having SBOMs and the necessity of tracing and signing each element in the supply chain to ensure integrity (focusing here on SLSA).

 

- [Watch talk's video](https://ftp.fau.de/fosdem/2025/h2213/fosdem-2025-5784-lessons-learned-from-integrating-sbom-in-a-supply-chain.av1.webm)
- [SBOM-SebD-Fosdem-02-2025.pdf](https://iot.bzh/download/public/2025/SBOM-SebD-Fosdem-02-2025.pdf)
- [FOSDEM 2025 schedule event](https://fosdem.org/2025/schedule/event/fosdem-2025-5784-lessons-learned-from-integrating-sbom-in-a-supply-chain/)

 

![fosdem-2025-sbom_opt.jpg](/images/uploads/articles/fosdem_2025_sbom_opt_822c55a14d.jpg)

large_FOSDEM_logo.svg.png

medium_FOSDEM_logo.svg.png

small_FOSDEM_logo.svg.png

thumbnail_FOSDEM_logo.svg.png

FOSDEM_logo.svg.png

Lessons learned from integrating SBOM in a supply chain

fosdem-2025-secure-boot_opt.jpg

Verifying the integrity of the entire boot process is today mandatory for embedded systems. Secure Boot is typically a feature that ensures the integrity of loaded binaries (such as vendor firmware, bootloaders, initramfs and the Linux kernel) to unauthorized modifications of essential boot components. If the bootloader or the Linux kernel does not match with what's expected, the boot process will be halted. After securizing as possible the boot process, there are other methods to enforce the rootfs like using dm-crypt for encryption, dm-verity for integrity...

 

This presentation will explore these security features in the context of an embedded operating system called redpesk OS. How can they enhance system security? Can they be applied to specific embedded systems? These are some of the key topics we will cover, with general security features then we'll explain some difficulties we had by deploying boot security features in a restricted environment (old Linux kernel version, CPU & memory usage).

 

- [Watch talk's video](https://video.fosdem.org/2025/ub4136/fosdem-2025-5244-lessons-learned-from-deploying-boot-security-features-on-embedded-systems.av1.webm)
- [Secure_redpesk_FOSDEM_2025.pdf](https://iot.bzh/download/public/2025/Secure_redpesk_FOSDEM_2025.pdf)
- [FOSDEM 2025 schedule event](https://fosdem.org/2025/schedule/event/fosdem-2025-5244-lessons-learned-from-deploying-boot-security-features-on-embedded-systems/)

 

![fosdem-2025-secure-boot_opt.jpg](/images/uploads/articles/fosdem_2025_secure_boot_opt_70227410c4.jpg)

Lessons learned from deploying boot security features on embedded systems

tux-evse_opt.jpg

We introduce Tux-EVSE, an open-source suite of embedded software components for building a complete Electric Vehicle (EV) charging system using readily available hardware on Linux. Tux-EVSE is designed with a strong focus on security and ease of integration, utilizing a lightweight micro-service framework (AFB) that isolates components for flexible development and testing. This modular structure allows developers to efficiently test and refine each component on a local machine before deploying to the final embedded hardware. The framework also embeds a security layer so that fine-grained permissions can be requested and granted to the application and / or services.

 

Written primarily in Rust, Tux-EVSE supports modern EV charging protocols, including ISO 15118-2x, DIN SPEC 70121, SLAC, and OCPP.

 

We will detail the different components of the charger: which kind of hardware components it can use, how the charging logic is implemented and how the modular architecture could allow one to adapt the charger to ones needs.

 

- [Watch talk's video](https://video.fosdem.org/2025/h2214/fosdem-2025-5399-tux-evse-an-open-source-ev-charger.av1.webm)
- [FOSDEM_2025_tux_evse.pdf](https://iot.bzh/download/public/2025/FOSDEM_2025_tux_evse.pdf)
- [FOSDEM 2025 schedule event](https://fosdem.org/2025/schedule/event/fosdem-2025-5399-tux-evse-an-open-source-ev-charger/)

 

![tux-evse_opt.jpg](/images/uploads/articles/IMG_20250202092912_opt_c5cca4c2a4.jpg)

Tux-EVSE, an open-source EV charger

In a world where embedded systems are increasingly connected (cars, planes, trains, etc.), cybersecurity has become much more than just a buzzword: it's an absolute necessity. Today, we're sharing with you an ambitious initiative supported by France 2030 that we're working on with other partners, aimed at improving the protection of our critical embedded systems and their sensitive data.
 
 
Besides[ IoT.bzh](https://iot.bzh/), HyGARDE includes companies such as [IDEMIA](https://www.linkedin.com/company/idemiagroup/) Secure Transactions (project coordinator) and [SOLENT](https://www.linkedin.com/company/solent-ingenierie/). Our engineers are working together to develop an all-in-one platform capable of securing and maintaining connected equipment throughout their lifecycle - from development to maintenance. A particular focus is placed on pre-certification and automatic generation of documentation to reduce costs associated with cybersecurity certification.
 
 
A use case: the energy transition. In partnership with the startup Solutions Hydrogène, HyGARDE's first concrete application will secure new renewable hydrogen storage equipment for residential homes, complementing solar and wind energy. This project is set to conclude in 2026, with a first prototype nearing completion.
 
 
[IoT.bzh](https://iot.bzh/) engineers are delighted to put their expertise to work on this ambitious project led by the global leader [IDEMIA](https://www.linkedin.com/company/idemiagroup/) Secure Transactions!
 
 
For more details, please refer to [this article](https://www.idemia.com/press-release/idemia-secure-transactions-and-three-french-technology-companies-create-hygarde-consortium-address-cybersecurity-challenges-connected-equipment-2024-11-13).

HyGARDE: How We Secure Future Connected Embedded Systems

Immerse yourself in the world of charging infrastructure for electric cars with this captivating presentation. Discover the technical architectures behind communications between charging stations and electric vehicles, through the experience of the ‘Tux-Evse’ project.
The talk covers cybersecurity challenges and solutions, lessons learned from using Rust versus C/C++, and the Linux/RTOS cohabitation model for ensuring functional safety.
As a bonus, learn how to build a state-of-the-art smart charging point at home, using open source components.

- [Link to talk](https://www.youtube.com/watch?v=KzgN8LLeh0Q&ab_channel=Codedarmor)
- PDF Link: [IoT-charger-tux-evse.pdf](<https://iot.bzh/download/public/2024/IoT-charger-tux-evse.pdf>)

logo_devfest2024.jpg

Feedback on the use of RUST/Linux in an electric vehicle charging station

During the icnc24 conference in Berlin, IOT.bzh was happy to present 1st fully open source ISO15118 simulator. 

Written in Rust, the ISO15118 simulator is available either in source code from GitHub, or as a "ready to use" binary package for Linux (Fedora, OpenSuse, Ubuntu) at IoT.bzh Redpesk SDK repository. The EVCC injector side is the main target, nevertheless, the simulator also proposes a responder for the EVSE part. You can define your own scenarios or import existing ones captured with tcpdump. 

 
 
<li className="markdownBulletList">Presentation video [<a href="https://player.vimeo.com/video/1004557448">here</a>]</li>
<li className="markdownBulletList">Source Code [<a href="https://github.com/tux-evse">github</a>]</li>

thumbnail_icnc24.png

icnc24.png

1st fully open source #ISO15118 simulator

small_l_portfolio_4.jpg

thumbnail_l_portfolio_4.jpg

l_portfolio_4.jpg

Presentation of cybersecurity challenges of an Electrical Vehicle charging station ISO 151118 in the framework of "Cyber Breakfast" seminars organised by BDI with breton cyber ecosystem.

- PDF Link: [Tux-EVSE Ev-Charger & Cybersecurity.pdf](https://iot.bzh/download/public/2024/Jose-IoTbzh-EvSE.pdf)

Tux-EVSE Ev-Charger & Cybersecurity

Rust is a very hype programming language that provides good practices to reduce potential attacks opportunities, nevertheless it is far from being perfect. This talk proposes a summary of our lessons learnt while moving some of our embedded code from C/C++ to Rust. It highlights some of difficulties Rust as a language introduces when dealing with low level and hardware components. It also exposes some of the options we implemented to reduce SBOM dependencies and address CVE tracking and CI infrastructure.

<a href="https://www.unlockyourbrain.bzh/en/presentations-eng/#LEFOLL-ENG" >Link to talk</a>
<a href="https://www.unlockyourbrain.bzh/en/unlock-your-brain-2/">Link to conference</a>
<a href="https://iot.bzh/download/public/2023/Fulup-IoTbzh-Rust-Embeddedc.pdf">Fulup-IoTbzh-Rust-Embeddedc.pdf</a>

RUST & embedded

Linux virtualization & isolation bring lots of advantages but also lots of conflict of interests. This presentation explains the various technical solutions including our IoT.bzh ultra-lightweight container redpak.

 - PDF Link: [Container-Linux-Isolation.pdf](https://iot.bzh/download/public/2023/Container-Linux-Isolation.pdf)

Linux Virtualization & Isolation

- Video link : [CentOS Automotive SIG - June 7, 2023](https://youtu.be/lwbyy9huXJk?t=105)
- PDF Link: [IoT.bzh-Yocto-To-CentOS-Automotive_v1.0.pdf](https://iot.bzh/download/public/2023/IoT.bzh-Yocto-To-CentOS-Automotive_v1.0.pdf)

Yocto BSP vs redpesk/centos BSP

Even though significant efforts attempt to prepare Linux for safety certifications, it seems obvious that these initiatives cannot deliver before years, if not decades, due to the magnitude of the work remaining. However, at the same time, the global automotive industry must comply today with many new certifications, including for cybersecurity (UNECE R155) and Over-The-Air software updates (UNECE R156) as well as those existing for safety (ISO-26262). This talk offers a pragmatic approach by leveraging existing hardware platforms and modern OSS software patterns to solve (partially!) certification issues related to safety, real-time and cybersecurity. This approach includes (but is not limited to) a small companion OS running within the same SoC (like Zephyr, FreeRTOS or AutoSAR) to perform certain critical functions. It also tries to use the latest techniques in containers and software isolation to satisfy security, privacy and safe updatability. 
 
 
- Conference link : [https://ossjapan2022.sched.com/event/1D13N](https://ossjapan2022.sched.com/event/1D13N)
- Video link : [ALS22_IoTbzh-Implement_Safety_with_Linux_and_RTOS.mp4](https://vimeo.com/778154200)
- PDF link : [ALS22_IoTbzh-Implement_Safety_with_Linux_and_RTOS.pdf](https://iot.bzh/download/public/2022/ALS/ALS22_IoTbzh-Implement_Safety_with_Linux_and_RTOS.pdf)

thumbnail_app-icon.png

app-icon.png

Toward a Linux safety compliant architecture through a RTOS companion.

The new generation of car combines incredible software complexity with a full Internet connectivity. As a result cybersecurity and IDS become a “must have feature” of modern software defined vehicle. Nevertheless even if within the new generation of connected cars hardware resources have significantly improved; embedded software capabilities remain very different from what is possible in a data centre or cloud context. When traditional IDS tends to duplicate network traffic to run detection algorithms based on well-known attack signatures; this embedded IDS architecture proposes a very different architecture that leverage Linux kernel probes to detect unexpected behaviours. All this with a minimal impact on the running system and without duplication of network traffic.
 
<ul>
<li className="markdownBulletList">paper [<a href="https://iot.bzh/download/public/2022/DSC/Fulup-IDS-paper-IoTbzh-DSC2022.pdf">here</a>]</li>
<li className="markdownBulletList">slides [<a href="https://iot.bzh/download/public/2022/DSC/Fulup-IDS-slides-IoTbzh-DSC2022.pdf">here</a>]</li>
<li className="markdownBulletList">video [<a href="https://vimeo.com/user116419595/iot-bzh">here</a>]</li>
<li className="markdownBulletList">conference website [<a href="https://dsc2022.org/">here</a>]</li>
</ul>

dsc.png

 IDS (Intrusion Detection System) for embedded systems

fosdem2022_redpak.pdf

thumbnail_clement_300x300.png

clement_300x300.png

Choosen by the French Government in the Big Cyber Challenge, Redpak is the new embedded container engine to run programs under heavy ressource constraints within microseconds. 

 

While Linux “name space” provides a good foundation for embedded application isolation, popular containers mostly focus on Linux fragmentation, and none of the Docker, LXC, Snap or Flatpak focus on embedded systems constrains. Everyone understands that installing a software component on millions of cars, on a submarine or in a train is very different from installing a new application on a desktop or a phone. Embedded containers target managed systems that, on one hand require less composability than phone or desktop, on the other hand require a stronger control on package qualification and resources usage.

 

This talk presents how to run containerise programs under heavy resource constrains. It exposes how containers permit to operate multiple flavors of a given toolkit and finally exposes how containers simplify configuration management, security and hierarchical model, SOTA.

 

* [Download Slides here](/images/uploads/articles/fosdem2022_redpak_7433a7d154.pdf)

 

<object data="/images/uploads/articles/fosdem2022_redpak_7433a7d154.pdf" type="application/pdf" width="100%" height="600px"/>*

Redpak: Ultra light weight container for embedded systems

small_vincent.jpg

thumbnail_vincent.jpg

vincent.jpg

With redpesk, we provide customers with the ability to cross-build an embedded, CentOS Stream-based Linux distribution in the cloud. This requires a significant infrastructure: Koji/RPM builders, Angular-based WebUI, Gitlab forge, network and RPM package dependency management, Qemu test lab management, all need to come together and be connected, in a mix of Qemu virtual machines and LXC containers. Fortunately, Ansible and Proxmox comes to the rescue to manage this complexity. 
In this talk, we'll present our architecture of a self-contained CI/CD environment in the cloud, to cross-build RPM packages and Linux images. We will then dive into the specifics of using Ansible to drive Proxmox and deploy a mix of Packer-built Qemu virtual machines and LXC containers. These provide a full Koji build system (hub and builders), an Angular frontend, Go backend, a Gitlab forge as well as network isolation/firewalling and a Qemu virtual target lab. We'll continue with lessons learned from doing these deployments for multiple customers. We will finish by describing solutions we are currently working on, like Ansible AWX, to address the challenges of doing it at scale and increase automation.
 
This talk was presented at <a href="https://fosdem.org/2022/schedule/track/infra_management/">FOSDEM 2022</a> in the Infra Management Devroom
 
Slides: [<a href="https://iot.bzh/download/public/2022/FOSDEM/ansible_proxmox_rpmbuild/Deploying_An_Embedded_Distro_Build_Factory_With_Ansible_And_Proxmox-Lessons_Learned.pdf">click here</a>]
 
Videos: [<a href="https://iot.bzh/download/public/2022/FOSDEM/ansible_proxmox_rpmbuild/ansible_proxmox_rpmbuild.mp4">click here for MP4</a>] [<a href="https://iot.bzh/download/public/2022/FOSDEM/ansible_proxmox_rpmbuild/ansible_proxmox_rpmbuild.webm">click here for WEBM</a>]

thumbnail_logo_osxp_aplat.png

logo_osxp_aplat.png

Using Ansible and Proxmox to manage an embedded RPM distro build factory: lessons learned

small_l_portfolio_47.jpg

thumbnail_l_portfolio_47.jpg

l_portfolio_47.jpg

With the exponential growth of software complexity, and in order to keep under control the cost and time of critical embedded application development, a continuous testing infrastructure is a must have feature.
 
Not only should software tests be run early and automatically each time a developer pushes a new code commit in the system, but furthermore, as developers typically never get enough physical board to test from, it is a key to initially run tests in a virtualized environment. Nevertheless we should keep enough real hardware in the loop to limit virtualization/reality deviation and ensure developers can transparently move tests from virtualization to the real world.
 
This presentation shows how virtualization may ensure early code integration to reduce development/testing cycle, while at the same time keeping track of real hardware, to ensure that the application is also running correctly on the final production device. Finally it gives feedback on the different challenges Iot.bzh faced while deploying its solution of continuous tests. Then focuses on the way virtualization and real targets can be combined to offer to developers a complete and efficient CI infrastructure.
 
This talk was presented at <a href="https://events.linuxfoundation.org/automotive-linux-summit/">Automotive Linux Summit</a> and at <a href="https://fosdem.org/2022/">FOSDEM 2022</a>
 

Slides: <a href="https://iot.bzh/download/public/2021/als-2021-japan/Armand-CT-in-cloud-infra-virtual-real.pdf">[click here]</a>
 

Video: <a href="https://iot.bzh/download/public/2021/als-2021-japan/ALS2021_CT_in_cloud_based_infra_with_virtual_real.mp4">[click here]</a>

large_Automotive_Grade_Linux_logo.svg.png

medium_Automotive_Grade_Linux_logo.svg.png

small_Automotive_Grade_Linux_logo.svg.png

thumbnail_Automotive_Grade_Linux_logo.svg.png

Automotive_Grade_Linux_logo.svg.png

Testing Continuously Applications Using a Cloud Based Infrastructure Using Virtualization and Real Hardware in the Loop

The modern, connected, embedded Linux IoT device is facing a fundamental problem: the more connected it gets, the more cybersecurity threats it faces. Data link reliability, especially in the marine case, also makes it hard to efficiently push sensor data to the cloud.
 

This talk shows how to implement a reliable sensor data path from a marine IoT device running the redpesk embedded distribution to the cloud. It starts with lessons learned from real-world use cases: sending data from thousands of sensors to a cloud backend served by a choppy connection. It then dives into the IoT.bzh microservice framework, its security model (based on SMACK and SELinux) and how we coupled it with RedisTimeSeries.
 

All this, in addition to an OpenID Connect service, allows one to securely and selectively funnel data from that target to the cloud. The talk concludes with a proposal on how this open infrastructure can be used by the community at large.
 

This talk was presented at <a href="https://www.opensource-experience.com/">Open Source Experience 2021</a> (<a href="https://www.sido-osxp.com/en/session/a25fd218-1e28-ec11-ae72-a04a5e7d345e">direct link to session)</a>
 

Slides: <a href="https://iot.bzh/download/public/2021/open-source-experience/OSXP-2021-Connected-ships-and-data-flows-from-the-on-board-sensor-to-the-cloud.pdf" target="_blank" rel="noopener">[click here]</a>

Connected ships and data flows: from the on-board sensor to the cloud

Cross debugging, and more generally, remote debugging, is something that may be unknown, or badly used, by either beginner engineers, or sometimes even by senior engineers, for several reasons. Some people simply do not know that remote debugging tools exists, some might consider the complex setup as a show-stopper, others may not trust the tools (and we can explain why).
 

Yet the return on investment of such tools is significant, provided that they are used appropriately.
 

This presentation talks about the first-fruits of cross-debugging, going through some real experiences, some architecture schemes and functional descriptions, comparing the existing solutions (eg, gdb-server vs lldb vs tcf ...), and their integration in IDEs (Eclipse, VsCode).
 

A technical chapter about the debugger mysteries, explains, in particular, why multithread, or SMP debugging is a complex issue, and how existing debuggers deal with it.
 

A chapter of performance analysis tools (eg, valgrind) is presented, too, in order to offer a kind of swiss army knife to the listeners.
 

As a conclusion, a short presentation of the debug tools on another OpenSource OS (<a href="https://www.zephyrproject.org/">Zephyr</a>) is done.
 

This talk was presented at <a href="https://events.linuxfoundation.org/embedded-linux-conference-north-america/">OSS</a>
 

[<a href="https://iot.bzh/download/public/2021/oss/Cross-debugging.pdf">Slides</a>]
 

[<a href="https://iot.bzh/download/public/2021/oss/OSS-cross-debugging.mp4">Video</a>]

small_ossNALogo.png

thumbnail_ossNALogo.png

ossNALogo.png

 Cross debugging on Linux : A history, current state of the art and coming improvements

devfest.pdf

Tous les programmes ont potentiellement des vulnérabilités qui peuvent être utilisées pour pénétrer dans votre système. Ainsi pour diminuer la portée des cyberattaques, les programmes devraient avoir des accés limités sur le système et ne devrait pas pouvoir écrire, lire, ... d'autres ressources que celles nécessaires.

 

C'est ce que propose les modules de sécurité Linux(LSM) comme SELINUX ou SMACK qui permettent de renforcer le contrôle d'accès obligatoire en créant des règles gérées par un architecte de sécurité.

 

Cette présentation présente comment LSM fonctionne et comment les régles peuvent être automatisées dans un framework comme redpesk.

 

* [Download slides ici](/images/uploads/articles/devfest_8153542108.pdf)
* [devfest website](https://devfest.codedarmor.fr/2021/)

 

<object data="/images/uploads/articles/devfest_8153542108.pdf" type="application/pdf" width="100%" height="600px"/>*

thumbnail_devfest-perros-guirec.png

devfest-perros-guirec.png

Automatisation des modules de sécurité Linux en intégration continue

redpesk-arz-team-1024px.jpg

redpesk-fish-avatar-with-title_512px.png

thumbnail_Sebastien_300.JPG

Sebastien_300.JPG

Lorient, France – September 13rd 2021 – IoT.bzh, an open source software company for embedded &amp; secured solutions, today announced the release of its first redpesk® OS version called «&nbsp;Arz 1.0&nbsp;». A ready-to-start full feature <a href="https://community-app.redpesk.bzh/signup">community edition </a> is available online with its <a href="https://docs.redpesk.bzh/">documentation</a>.
 
«&nbsp;Thanks to redpesk®, customers can now focus on their differentiating applications relying on an easy-to-use CI/CD Long Term Supported platform (+10 years) with best of modern IT features adapted to embedded’s constraints&nbsp;» said Fulup Le Foll, IoT.bzh CEO. redpesk® Arz 1.0 includes the following key features&nbsp;:
 
<ul>
<li className="markdownBulletList">A new application framework AFB-V4 engine compatible with AGL-V3 up to 10 times faster</li>
<li className="markdownBulletList">A new security model that can understand Smack but also an early access version for SELinux</li>
<li className="markdownBulletList">+2 500 pre-built ready-to-use binary packages</li>
</ul>
 
But also many others as: <img src="/images/articles/small_redpesk_fish_avatar_with_title_512px_f0e162aefd.png" alt="" style="float: right; width: 150px; border: 0px; margin-right: 5px;" />
 
<ul>
<li className="markdownBulletList">Cross-compilation for X86 &amp; ARM architectures</li>
<li className="markdownBulletList">SDK enabling fast native iteration cycles for developers</li>
<li className="markdownBulletList">Automatic testing facility for both real &amp; virtual environments</li>
<li className="markdownBulletList">Extended QA through scanning tools</li>
<li className="markdownBulletList">Release management solution</li>
<li className="markdownBulletList">Reporting interface</li>
<li className="markdownBulletList">Reference implementation for Over-the-Air updates</li>
<li className="markdownBulletList">Core optional platform services (health monitoring, identity management etc)</li>
</ul>
 
All these features are supported on multiple SoC architectures and reference boards: Renesas H3/M3 ULCB, Raspberry PI 4, UP board &amp; virtual machine QEMU-x86_64
 
&nbsp;
<h5>About redpesk®</h5>
 
redpesk® is a secure embedded Linux dedicated to Industrial IoT and redpesk® OS (<a href="https://redpesk.bzh/">www.redpesk.bzh</a>) provides:
 
<ul>
<li className="markdownBulletList">A free developer edition aligned with CentOS Stream®</li>
<li className="markdownBulletList">A subscription based LTS version aligned on a fork of RHEL®</li>
</ul>
 
&nbsp;
<h5>About IoT.bzh</h5>
 
IoT.bzh is an expert software company with strong recognition inside the global open source community for its Linux and cybersecurity solutions dedicated to embedded markets (automotive, maritime, military, aeronautics, energy etc).
 
&nbsp;
&nbsp;<img src="/images/articles/redpesk_arz_team_1024px_353429fce1.jpg" alt="" class="pull-center" style="width: 90%;" />

Release of redpesk Arz 1.0

An introduction to the fundamentals of SMACK and SELinux administration.
 
This conference was presented for the association <a href="https://hack2g2.fr/">HACK2G2</a>.
 
Slides : <a href="https://iot.bzh/download/public/2021/hack2g2/Presentation_MAC.pdf" class="wf_file" title="[click here]">[click here]</a>

small_hack-logo-light-512px.png

thumbnail_hack-logo-light-512px.png

hack-logo-light-512px.png

Introduction to SMACK and SELinux

small_540-596-max.png

thumbnail_540-596-max.png

540-596-max.png

Modern SoCs contain heterogeneous processor devices that can be used to execute specific tasks. While Linux often runs on Cortex Ax processors, it is possible to run Zephyr on smaller cores like Cortex M or R. That way it's possible to isolate critical functions from a Linux rich environment. Applications can be found for safety use cases, power management purposes (wake up word, wake on sensor), or isolating realtime tasks. This talk is about solutions we found at IoT.bzh to make both world cooperate: How to communicate thanks to the RPMSG framework and how to start this remote processor from Linux using the remoteproc subsystem.
 

This talk has been given for <a href="https://www.youtube.com/playlist?list=PLn7YTy5_SF4-FRyY-5zwsKuTCOBRUkY_h">Live Embedded event 2021</a>.
 

Slides:&nbsp;<a href="https://iot.bzh/download/public/2021/live-embedded-event/running-zephyr-and-linux.pdf" target="_blank" rel="noopener">[click here]</a>
 

Video:&nbsp;<a href="https://www.youtube.com/watch?v=R79bsHpTml4" target="_blank" rel="noopener">[click here]</a>
&nbsp;

live-embedded-event-2021.jpg

Running Zephyr and Linux on the same SoC: making both worlds live together !

The modern, connected, embedded Linux IoT device is facing a fundamental problem: the more connected it gets, the more cybersecurity threats it faces. Data link reliability, especially in the marine case, also makes it hard to efficiently push sensor data to the cloud.
 
This talk shows how to implement a reliable sensor data path from a marine IoT device running the redpesk embedded distribution to the cloud. It starts with lessons learned from real-world use cases: sending data from thousands of sensors to a cloud backend served by a choppy connection. It then dives into the IoT.bzh microservice framework, its security model (based on SMACK and SELinux) and how we coupled it with RedisTimeSeries.
 

Those, in addition to an OpenID Connect service, allows to securely and selectively funnel data from that target to the cloud. The talk concludes with a proposal on how this open infrastructure can be used by the community at large.
This talk was presented at <a href="https://www.youtube.com/playlist?list=PLn7YTy5_SF4-FRyY-5zwsKuTCOBRUkY_h">Live Embedded Event 2021</a>
 

Slides: <a href="https://iot.bzh/download/public/2021/live-embedded-event/From-embedded-Linux-boat-sensors-to-the-cloud-a-data-journey.pdf" target="_blank" rel="noopener">[click here]</a>
 

Video: <a href="https://youtu.be/KiPWsM_dcrE" target="_blank" rel="noopener">[click here]</a>

From embedded Linux boat sensors to the cloud, a data journey

Modern SoCs contain heterogeneous processor devices that can be used to execute specific tasks. Renesas R-Car Gen 3 embeds a Cortex-R7 that can access any memory mapped devices.
 
Taking advantage of this processor allows to have critical applications that should bring the proof of their robustness (realtime, safety, power consumption..).
 
This talk start with a presentation about technical constraints about having a MCU running RTOS.
 
This talk also gives an introduction on how to manage this processor lifecycle from Linux side and how to communicate between both worlds (AGL and Zephyr).
 
This talk was presented at the AGL All Member Virtual Meeting 2021.
 
Slides:&nbsp;<a href="https://iot.bzh/download/public/2021/agl-amm/March17_JulienMassot_Hardware-isolation-running-rtos-concurrently-with-agl-on-renesas-r-car.pdf" target="_blank" rel="noopener">[click here]</a>
 
Video:&nbsp;<a href="https://iot.bzh/download/public/2021/agl-amm/March17_JulienMassot_Hardware-isolation-running-rtos-concurrently-with-agl-on-renesas-r-car.m4v" target="_blank" rel="noopener">[click here]</a>

thumbnail_AGL-AMM-logo.png

AGL-AMM-logo.png

Hardware Isolation Running RTOS Concurrently with AGL on Renesas R-Car

This talk given at the AGL All Member Meeting [VIRTUAL] of Spring 2021 presents how the application framework and its core components can shift from being based on Smack to SELinux.
 
The Linux kernel has many security mechanisms: capabilities, credentials, cgroups, namespaces, security modules, SELinux, AppArmor, Smack, ...
 
The talk reviews their benefits. As of today, the AGL application framework leverages these security features in order to achieve safety, security and privacy of the system, applications and users.
 
The talk summarizes the current state of the application framework.
 
Finally, the talk presents the work done in replacing Smack with SELinux and shows the designs that make the transition transparent to application developers while providing the same level of security.
 
Slides: <a href="https://iot.bzh/download/public/2021/agl-amm/March18_JoseBollo_From-SMACK-to-SELinux.pdf" target="_blank" rel="noopener">[click here]</a>
 
Video: <a href="https://iot.bzh/download/public/2021/agl-amm/March18_JoseBollo_From-SMACK-to-SELinux.m4v" target="_blank" rel="noopener">[click here]</a>

From Smack To SELinux

This video is a short introduction of the redpesk® factory WebUI. As you can see, the following features are available :
 
<ul>
<li className="markdownBulletList">easy workflow to create a new project and an application</li>
<li className="markdownBulletList">team and user management</li>
<li className="markdownBulletList">integrated specfile editor</li>
<li className="markdownBulletList">automated CI tests based on virtual lab / targets</li>
</ul>
 
<video controls="controls" width="80%"> redpesk video presentation <source src="https://iot.bzh/download/public/2021/ademe/Redpesk_Factory.mp4" type="video/mp4" /> </video>
 
<video controls="controls" width="80%"> 
redpesk video presentation 
<source src="https://iot.bzh/download/public/2021/ademe/redpesk_intro_FR.mp4" type="video/mp4" /> </video>

redpesk® factory demo video

The modern vehicle is facing a fundamental problem: the more connected it gets, the more cybersecurity threats it faces.
 
Data link reliability or bandwidth changes caused by roaming also make it much harder to reliably push car sensor data to the cloud.
 
This presentation is about implementing a reliable Vehicle to Cloud (V2C) scheme in the AGL ecosystem.
 
It starts with lessons learned from real-world use cases: sending data from thousands of sensors to a cloud backend served by a choppy connection.
 
It then describes how the AGL microservice framework and its security model, coupled with RedisTimeSeries, can be used to securely and selectively funnel data from the target to the cloud.
 
The talk concludes with a proposal on how this infrastructure could be integrated into the core of AGL to benefit the community at large.
 
This talk was presented at the AGL All Member Virtual Meeting 2021.
 
Slides: <a href="https://iot.bzh/download/public/2021/agl-amm/March18_VincentRubiolo_Data-continuity-from-vehicle-sensors-to-cloud-databases-in-the-AGL-ecosystem.pdf" target="_blank" rel="noopener">[click here]</a>
 
Video: <a href="https://iot.bzh/download/public/2021/agl-amm/March18_VincentRubiolo_Data-continuity-from-vehicle-sensors-to-cloud-databases-in-the-AGL-ecosystem.m4v" target="_blank" rel="noopener">[click here]</a>
&nbsp;

Data continuity, from vehicle sensors to cloud databases in the AGL ecosystem

As today, AGL has mostly been sponsored by the Automotive Industry. Nevertheless, many of the AGL requirements are not unique to this industry. Reusing AGL within non-automotive projects would save money, improve time to market and extend the community of adopters. To be active in 15 years from now, AGL should handle not only cars, but also robots, boats, trains…no project can survive in the jungle of open-source without a global adoption.
 
The Marine Grade Linux project by IoT.bzh provides a customized flavor of AGL that addresses marine specific requirements. For signaling, NMEA2000, CanOpen, Ethercat and Modbus were added. Cloud connectivity is designed to handle random connectivity with a balance of 4/5G and satellite data link. Some core marine services as nautical charts, safe routing, or radar are still under development and should be added in the near future. Last but not least, a 30 years old ship is pretty common and maintenance/update on 15 years is required.
This presentation exposes the outcome of the three marine projects IoT.bzh is currently developing for this industry. It starts exposing gaps in business models, then exposes some of the technical specificities (signaling, SOTA, LTS, …). Finally it introduces redpesk@sea the ready-to-use “Marine Grade Linux” version that IoT.bzh will propose as Christmas gift to the maritime open-source community.
 
This is the video streamed during AGL Member Webinar (2020 December 16th)
 

<video controls="controls" width="80%" type="video/mpeg"> redpesk marine video <source src="https://iot.bzh/download/public/2020/redpesk_at_sea/redpesk-marine-new.mp4" type="video/mp4" /></video>

redpesk Marine Grade Linux

The main objective of this paper is to implement an Intrusion Detection System (IDS) over the Controller Area Network (CAN) data buses. In order to achieve this, we will first study the architecture of CAN buses in the automotive industry and then develop a detection method plan in order to treat various attacks.
 
Paper: <a href="https://iot.bzh/download/public/2020/IDS_CAN.pdf" target="_blank">[click here]</a>

Intrusion Detection System (IDS) on automotive CAN bus

thumbnail_Stephane_300.JPG

Stephane_300.JPG

IoT.bzh investigated on lazy object synchronization techniques combined with an appropriate serialization format and shows that performance can be improved by a ratio from 10 to 100 depending on use cases. This benefits to low-latency and/or high-throughput applications: High frequency sensors, fast CAN messaging, realtime applications, ...
 
Changing serialization format may provide a performance gain from 20% to 50%. To go further, the only solution is to reduce drastically the number of (de)serializations. This can be achieved by adopting a dual internal and external representation for objects coupled with new transport mechanisms between bindings.
 
This talk presents the benchmark results obtained by our team and proposes new ways to boost performance in the AGL Application Framework, including a new binding API v4 compatible with current API v3.
 
Slides: <a href="https://iot.bzh/download/public/2020/agl-amm/IoT.bzh-Boost_AGL_AppFW_performance_by_10-AGL_AMM_July_2020-v1.0.pdf" target="_blank">[click here]</a>
 
Video: <a href="https://vimeo.com/438457064" target="_blank" rel="noopener">[click here]</a>

Boost AGL Application Framework performance by 10+

While Linux “name space” provides a good foundation for embedded application isolation, popular containers mostly focus on Linux fragmentation, and none of the Docker, LXC, Snap or Flatpak focus on embedded systems constrains.
 
Everyone understands that installing a software component on millions of cars, on a submarine or in a train is very different from installing a new application on a desktop or a phone. Embedded containers target managed systems that, on one hand require less composability than phone or desktop, on the other hand require a stronger control on package qualification and resources usage.
 
This talk presents how to run a containerized AGL under heavy resource constrains. It exposes how containers permit to operate multiple flavors of a given toolkit and finally exposes how containers simplify configuration management, security model and SOTA.
 
<ul>
<li>slides: <a href='https://iot.bzh/download/public/2020/agl-amm/IoT.bzh-RedPak-AGL_AMM_July_2020-v1.2.pdf'>[here]</a></li>
<li>video:<a href='https://vimeo.com/435689572'> [here]</a></li>
</ul>

Ultra Light Weight Containers for Embedded Systems

This presentation was given at International Cybersecurity Forum (FIC) in Lille / France.
 
While the automotive industry has specific constrains and requirements that OpenID Connect (OIDc) did not dig in, OIDc can still be used to secure vehicle to cloud connection, in car communications or smart-cities interactions.
 
This talk introduces how IoT.bzh proposes to use OIDc inside Automotive Grade Linux (AGL) to secure the interaction in between car infotainment, instrument cluster, telematic unit or cloud operations.
 
Download slides <a href="https://iot.bzh/download/public/2020/FIC/FIC2020_IoTbzh-Pitches.pdf" target="_blank" rel="noopener">[click here]</a>
&nbsp;

thumbnail_FIC2020Lille.png

FIC2020Lille.png

Secure vehicle data exchange with "OpenID Connect"

This presentation was given at DevOps Wold / Jenkins World in Lisbona.
 
As today automotive software capabilities are one of the main motivation to choose one model over an other. Thus a modern car easily runs 50 to 100 millions lines of code distributed on more than one hundred SoC/ECU connected by ten or more different networks. At the same time, automotive remains a very strongly cost driven market where short term profits are impossible. This imposes OEMs to keep running the same hardware platform for a minimum of 5 years. OEMs have to both apply security patches and add as many new functionality as expected by the market while having little or even no margin to improve hardware. This conflict of innovation versus stability is only possible with ten years or more long term maintenance contract and a very strict test and continuous software integration process.
 
This talk details the reasons why these new trends are key for automotive and many other industries. It exposes how based on lessons learn IoT.bzh proposes a solution to fulfill embedded software long term support. How to scale it to very complex systems with “in production” multiple software versions, multiple hardware revisions, thousands of components coming from multiple sources and last but not least hundreds of developers.
 
Download slides <a href="https://iot.bzh/download/public/2019/DevOps_Lisbona_1219/Fulup-Presentation-DevOps-Lisboa-2019.pdf" target="_blank">[click here]</a>
&nbsp;

Current Market Conditions for Automotive Supply Implies Long Term Support

This slideshow was used as support for a lesson given at "École nationale supérieure de techniques avancées Bretagne (ENSTA Bretagne)" (University of Brittany).
 
It presents many aspect of AGL, its security and its framework. It can be used as starter overview browsing every AGL feature.
 
Download [<a href="https://iot.bzh/download/public/2019/ENSTA/embedded-security-AGL.pdf" target=_blank>here</a>]
&nbsp;

thumbnail_index.png

ensta.png

Embedded Linux, case of AGL. Lesson at ENSTA 2019

thumbnail_Yann_300.JPG

Yann_300.JPG

This presentation was given at AGL All Member Meeting in Monte Carlo, Monaco.
 
Cars remain expensive, customers expect long warranty and strong aftersales services. For OEMs car development costs increase making short term profits impossible. They must leverage software update to add new features while keeping same hardware during minimum 5 years of serial life. So, OEMs LTS contract requirements may quickly extend to 20 years.
 
Cybersecurity legislation moves. Following European Cybersecurity Act, the ENISA passed a cybersecurity certification schema. If until now OEMs had limited interest in this topic, they will be forced to take seriously into consideration these new legal constraints and propose security patches during the whole vehicle lifetime.
This talk details the reasons why these new trends are important for OEMs and exposes how based on lessons learnt IoT.bzh proposes a solution to fulfill LTS and cybersecurity certifications requirements.
 
Download slides <a href="https://iot.bzh/download/public/2019/AMM_MonteCarlo_1019/Yann-Presentation-AMM-Monte_Carlo-2019.pdf" target="_blank">[click here]</a>
 
Show Redpesk Video <a href="https://iot.bzh/download/public/2019/AMM_MonteCarlo_1019/RedPesk-Overview-Oct2019.mp4" target="_blank" rel="noopener">[click here]</a>
&nbsp;

Current market condition for automotive supply implies Long Term Support

This presentation was given at Automotive Linux Summit in Tokyo.
 
AGL natively supports secure micro-services through its Application Framework binder/binding mechanism. A ready to go system may easily run tens or hundreds of micro-services. Consequently monitoring exchanges between binders/bindings is critical. Monitoring may need to be “realtime” to help debugging, or offline when tracking global performances and security issues.
 
This talk starts by presenting current AGL Application Framework monitoring capabilities to track basic inter-bindings communications. It then exposes how existing supervision service can be used to analyze end-to-end transactions when crossing multiple bindings. Finally it illustrates how AGL supervision can leverage Time Serie Database to collect data, allowing monitoring frameworks like Grafana to render a global vision of the system both in term of performance and cybersecurity.
 
Download slides <a href="https://iot.bzh/download/public/2019/ALS_Tokyo_0719/AGL-XDS_Supervision_ALS_Tokyo_2019.pdf" target="_blank">[click here]</a>
&nbsp;

medium_als.png

small_als.png

thumbnail_als.png

als.png

AGL-Supervision : From AGL Supervisor to platform global data collection

This presentation was given at Automotive Linux Submit in Tokyo.
 
In order to embrace the global automotive ecosystem, AGL micro-services architecture should support not only all Linux in a car, but also seamlessly retrieve data from small ECUs and securely send collected information to the cloud.
 
Because of existing application framework dependencies, as today, AGL bindings run only on Linux. In order to extend to global automotive ecosystem, AGL’s binders/bindings architecture needs to be reviewed. On one hand, remove Linux’s systemD dependencies and extend security model. On a second hand, support ‘alien’ transport protocols including non TCP/IP ones.
 
This talk presents the lesson learned from a POC to run a subset of current AGL binder onto a micro-controller with Zephyr. How to solve binder/binding dependencies, how to map the transport onto a non TCP/IP link, how to extend AGL security model, ...
 
Download slides <a href="https://iot.bzh/download/public/2019/ALS_Tokyo_0719/AGL-uBinder-Fulup-IoTbzh-Tokyo-ALS2019.pdf" target="_blank">[click here]</a>
&nbsp;

AGL-µBinder : a fast, secure and seamless option to connect AGL to small ECUs?

This talk presents, the motivation and options chosen by AGL to address automotive cybersecurity. Its first addresses secure functionally targeted by AGL applications security model, then exposes how we extend the model from Linux entertainment to vehicle to cloud, cluster, telematics, ... This talk remains at the architecture level. It explains targeted security concerns and exposes proposed software architecture but does not aim at digging into specific implementation details.
 
Download pdf slide <a href="https://iot.bzh/download/public/2018/CESA-5.0/Fulup-IoTbzh-CyberSecurity-AGL-CESA-Dec2018.pdf">[here]</a>

thumbnail_sesa.jpeg

sesa.jpeg

Cybersecurity for Connected Vehicle with AGL (Automotive Grade Linux)

thumbnail_300-220-max.png

Jonathan_Aillet.png

Cette présentation à été utilisée pour donner une conférence à l'Université de Bretagne Sud à Lorient (UBS) le 26 Octobre 2018.  

Elle introduit le fonctionnement de la chaîne de boot, les bootloaders étant capables de lancer un OS, la vérification des binaires pendant le boot dans les systèmes embarqués, et l'environnement d'exécution sécurisé (TEE).  

Téléchargement [ Ici ](http://www.iot.bzh/download/public/2018/UBS/JonathanAillet_Boot-SecureBoot-UBS-20181026.pdf)

ubs.png

 Boot & Secure Boot

small_thierry.jpg

thumbnail_thierry.jpg

thierry.jpg

This talk presents options to bring a subsystem of AGL Application Framework into realtime operating systems like AutoSar Foundation, VxWorks, Zephyr, QNX.In order to bridge smaller controllers with AGL systems, current Application Framework should be skimmed down to a portable, OS-independent and realtime enabled core. To get certified, this small realtime core should be come with 100% code coverage. It should work on microcontrollers, or on a PREEMPT-RT patched linux. It should have a set of realtime API and communication API with the non realtime world. As an example, the presentation shows how to push CAN data to Infotainment.
&nbsp;
 
&nbsp;PDF presentation available <a href="https://iot.bzh/download/public/2018/amm-dresden/realtime_binder_presentation.pdf">here</a>

thumbnail_AGL_logo.png

AGL_logo.png

Skim down AGL Application Framework to bridge AGL with hard realtime subsystems

After a presentation of the security framework that rules the applications, this presentation browse the effective well known use cases of applications. The use cases covered are HTML apps, QML apps, general services, audio 4A service, signal composer service, ... For each use cases are presented the software architecture, the security context, the interaction with the AGL system, the typical dialog between application, binding and services, the programming model using binding version 3 as available in AGL/FF.
 
Download [<a href="https://iot.bzh/download/public/2018/amm-dresden/AGL-app-design.pdf">here</a>]
&nbsp;

AGL application design

small_romain.jpg

thumbnail_romain.jpg

romain.jpg

This presentation will cover the latest test and monitoring tools available in AGL. Most of all, it presents the new test binder answering the following, how to write test for AGL API and how is it integrated within AGL. Then I present the Application Framework Monitoring feature which provides you a binding insights view. At the end, we see another handy Application Framework feature in the name of Supervision that makes available all sort of metrics from the working binder.
 
Download slides [<a href="https://iot.bzh/download/public/2018/amm-dresden/test-monitoring-supervision-romain.pdf" target="_blank" rel="noopener">here</a>]

Moving AGL toward production with the latest test/monitoring tools.

Pourquoi et comment sécuriser les véhicules connectés de prochaines génération. Présentation dans le contexte du HichHack 2018 à l'ENSIBS de Vannes.
 
présentation [<a href="http://www.iot.bzh/download/public/2018/ENSIBS/CyberSecurity-HichHack-2018-Fulup-IoTbzh.pdf">cliquer ic</a>i]

thumbnail_ENSIBS.png

ENSIBS.png

Véhicule Connecté Cybersécurité et Open Source

Presentation at Karlsruhe of the ongoing refactoring of binding APIs.
 
The new API named V3 (version 3) is going be compatible with previous versions.
 
Download slides <a href="https://iot.bzh/download/public/2018/f2f-karlsruhe/apiv3-prez-2018-04.pdf" class="wf_file" title="Bindings Api v3">[Click here]</a>

Binding API version 3

This presentation was given at AGL F2F meeting in Karlsruhe. It's an update of XDS project (current version v1.1.1) and roadmap (next version v2.0.0).
 
Download slides <a href="https://iot.bzh/download/public/2018/f2f-karlsruhe/XDS_Presentation_Apr_2018.pdf" target="_blank">[click here]</a>
&nbsp;

X(cross) Development System update - April 2018

This presentation was given by Romain Forlot and Sebastien Douheret at AGL F2F meeting in Karlsruhe by and presents work done and next steps around the Vehicle To Cloud domain. The first part of this presentation is an update of Signal Composer component and the second part exposes IoT.bzh solutions for&nbsp;Telematic and Debugging data. 
Download slides <a href="https://iot.bzh/download/public/2018/f2f-karlsruhe/AGL-V2C-signaling-data-collection.pdf" target="_blank">[click here]</a>
&nbsp;

Vehicle 2 Cloud - Telematics and Data collection - April 2018

small_fred.jpg

thumbnail_fred.jpg

fred.jpg

<div style="float: left; margin: 8px 32px 16px 8px">
<img src="/images/uploads/articles/small_AMM_2018_fred_ff468f411e.png"/>
</div>
<div style="text-align: justify;">The main purpose is to present an architecture to build and test embedded applications automatically. Frédéric Marec take time to make an overview of Jenkins architecture and latest features. Then he put the focus on Jenkins V2 and the advantages in using pipelines. He make an overview about X(cross) Development System tool. Finaly he show how to pipeline and XDS to build an application, test it, publish it.</div>
 
Download the presentation :&nbsp; <a href="http://iot.bzh/download/public/2018/amm-tokyo/presentation-frederic-marec_AMM-2018.pdf" style="font-size: 12.16px;">(PDF format)</a>
<div>&nbsp;</div>

Industrialisation of applications build in embedded environment

small_Ronan.jpg

thumbnail_Ronan.jpg

Ronan.jpg

Yocto SDKs or images are currently deployed as monolithic archives. Projects are more and more complex resulting to larger archives and&nbsp; consequently, SDKs or target images updates are not efficient at all. This talk presents a new solution based on incremental updates and binary packages deployment, which is closer to standard Linux distribution packaging.&nbsp; This solution offers an easy way to update development environment (SDK) on the development machine and makes packages management simpler on the target side. This allows among other to install a minimal set of packages in order to reduce the target filesystem size.
 
<a href="https://iot.bzh/download/public/2017/AMM-Dresden/SDK-Yocto-incremental-SDKs.pdf" title="Yocto-incremental-SDKs">Yocto-incremental-SDKs</a>

Deploy AGL OS and SDK as a Binary Packaging Distribution for Developer

The AGL controller is a new binding that was initially developed to address the lack of AGL mechanism to support policy/access-control in AAAA. The outcome of this effort is a fully generic controller that allows to “glue” many different components directly from a simple JSON configuration file. The resulting service is exposed as a native AGL binder. It is a real Swiss Knife and can be used to many different things for applications or services.AGL Controller is a pure Vanila AGL binding. It can be added transparently to any existing binder through the standard application framework import mechanism. The controller is fully compliant with AGL security model and offers for dynamic APIs the same level of protection that AGL already offers to static APIs.AGL controller is powerful and flexible. It allows developers to simply assemble pre-existing AGL APIs, to expose as AGL native binder a legacy/proprietary technologies. Finally it supports Lua as scripting language to glue everything together. Mixing Native/Script language is supported and a developer may choose to fast track demo in Lua script and later to port all/part in native C/C++ to improve performances.The presentation will show the architecture, the different components and will walk though a set of examples. At the end of the talk attendees should have a clean understanding on how to leverage AGL controller in their own applications.
 
Download the detailed PDF presentation: <a href="https://iot.bzh/download/public/2017/AMM-Dresden/AGL-Controller-Binding.pdf">[here] </a>(AGL/AMM Dresden/Germany Oct-2017)

The AGL Swiss Knife for Quick Application Prototyping

xds_arch.png

<div style="float: left; margin: 8px 32px 16px 8px">
<img src="/images/uploads/articles/small_xds_arch_b9c17db1c1.png"/></div>
This presentation was given at ALS 2017 in Tokyo.
 
To reduce as much as possible the entry cost for developing automotive applications, AGL should be integrated to IDE and Source Debugger. Traditionally, installation of an embedded development environment with cross compilation has been difficult and more tortuous that it should. Any developer and especially non system expert, should easily succeed in setting up the AGL development environment on both target &amp; host independently of their preferred OS (Linux, Windows, Mac).
 
This talk presents a solution that tends to a zeroconf installation of AGL development environment, independently of the chosen target/host.The presented solution allows to locally edit sources with your favorite IDE (i.e. Eclipse, Visual Studio Code, Netbeans...) and either compile locally your application or benefit from a remote server. It also shows how to debug application directly from your preferred editor.
 
Download the latest presentation (PDF format):  <a style="font-size: 12.16px;" href="https://iot.bzh/download/public/2017/XDS/presentation/XDS_Presentation_latest.pdf">[here]</a> 
 
Download older presentations:  <a style="font-size: 12.16px;" href="https://iot.bzh/download/public/2017/XDS/presentation/">[here]</a>

X(cross) Development System - make AGL app development easier

IoT.bzh proposes a low level CAN binding with the following features:
 
<ul>
<li className="markdownBulletList">support of CAN messages and diagnostic messages (OBD-II)</li>
<li className="markdownBulletList">signals description with OpenXC JSON notation</li>
<li className="markdownBulletList">encoding/decoding of CAN messages using OpenXC libraries</li>
<li className="markdownBulletList">API for other AGL applications and services to read/write on CAN bus(es) securely</li>
<li className="markdownBulletList">publish/subscribe model with filtering for efficiency</li>
</ul>
 
<a href="https://vimeo.com/iotbzh/canlive">See the binding in action on a Citroën C5 !</a>
 
Download the presentation <a href="https://iot.bzh/download/public/2017/F2F-Karslruhe/AGL-Signaling.pdf">[here]</a> (AGL F2F meeting, Karlsruhe, April 2017)

Low level CAN binding for AGL: a generic way to handle CAN signals

systemd.png

<div style="float: left; margin: 8px 32px 16px 8px">
<img src="/images/uploads/articles/small_systemd_ab8708ad2b.png"/></div>
The framework is presented in its current state of January 2017: its history, its features and its goals: opening securely AGL to as many companies as possible. Then, focus will turn to the expected state of the framework at end of 2017, browsing the remaining tasks and giving an agenda. This includes at least these items, reviewed technically and logistically: integration with systemd (cgroup handling, tiny namespacing, ...), permission policy and enforcement, cryptography and PKI for domain protection.
 
Slideshow of the presentation at AGL AMM Winter 2017 Tokyo : <a href="https://iot.bzh/download/public/2017/AMMQ1Tokyo/AGL-security-framework-review.pdf">[here]</a>

AGL Security Framework Review 

agl-dd.png

<div style="float: left; margin: 8px 32px 16px 8px">
<img src="/images/uploads/articles/small_agl_dd_8f1dadcc5c.png"/></div>
Keeping user experience control is critical for every OEM. To enable an easy way to tailor UI and user experience, AGL in general and homescreen in particular should provide a clear separation in between business logic and graphic rendering. This talk propose a new homescreen architecture. In this new approach the homescreen is a platform service accessible through a set of normalized API. Every OEM/Tier1 should be able to easily reshape user experience by simply connecting a new UI on a platform provided homescreen service. The new architecture should support not only both HTML5 &amp; QT user interface, but should also support multi-screens, multi-users, local &amp; remote screens and obviously should implement security built in by design.
 
Download PDF presentation:  <a href="https://iot.bzh/download/public/2017/AMMQ1Tokyo/HomeScreen-Q1AMM2017-Fulup-IoTbzh.pdf">[here]</a>

redpesk^® Publications

Rust in embedded systems: feedback on the development of a charging station for electric vehicles

Cybersecurity and auditability of embedded systems - the case of an EV charger

Mitigate cybersecurity/safety constraints with asymmetric multiprocessing

Lessons learned from integrating SBOM in a supply chain

Lessons learned from deploying boot security features on embedded systems

Tux-EVSE, an open-source EV charger

HyGARDE: How We Secure Future Connected Embedded Systems

Feedback on the use of RUST/Linux in an electric vehicle charging station

1st fully open source #ISO15118 simulator

Cookie policy

redpesk® Publications

Rust in embedded systems: feedback on the development of a charging station for electric vehicles

Cybersecurity and auditability of embedded systems - the case of an EV charger

Mitigate cybersecurity/safety constraints with asymmetric multiprocessing

Lessons learned from integrating SBOM in a supply chain

Lessons learned from deploying boot security features on embedded systems

Tux-EVSE, an open-source EV charger

HyGARDE: How We Secure Future Connected Embedded Systems

Feedback on the use of RUST/Linux in an electric vehicle charging station

1st fully open source #ISO15118 simulator

Cookie policy

redpesk^® Publications