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, some other ones may not trust the tools (and we can explain why).
Yet the return of 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 functionnal 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 (Zephyr) is done.
This talk was presented at OSS
Lorient, France – September 13rd 2021 – IoT.bzh, an open source software company for embedded & secured solutions, today announced the release of its first redpesk® OS version called « Arz 1.0 ».
A ready-to-start full feature community edition is available online with its documentation.
« 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 » said Fulup Le Foll, IoT.bzh CEO.
redpesk® Arz 1.0 includes the following key features :
- A new application framework AFB-V4 engine compatible with AGL-V3 up to 10 times faster
- A new security model that can understand Smack but also an early access version for SELinux
- +2 500 pre-built ready-to-use binary packages
But also many others as:
- Cross-compilation for X86 & ARM architectures
- SDK enabling fast native iteration cycles for developers
- Automatic testing facility for both real & virtual environments
- Extended QA through scanning tools
- Release management solution
- Reporting interface
- Reference implementation for Over-the-Air updates
- Core optional platform services (health monitoring, identity management etc)
All these features are supported on multiple SoC architectures and reference boards: Renesas H3/M3 ULCB, Raspberry PI 4, UP board & virtual machine QEMU-x86_64
redpesk® is a secure embedded Linux dedicated to Industrial IoT and redpesk® OS (www.redpesk.bzh) provides:
- A free developer edition aligned with CentOS Stream®
- A subscription based LTS version aligned on a fork of RHEL®
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).
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 Live Embedded Event 2021
Slides: [click here]
Video: [click here]
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 Live Embedded event 2021.
Slides: [click here]
Video: [click here]
- Cross debugging on Linux : A history, current state of the art and coming improvements
- Release of redpesk Arz 1.0
- Introduction to SMACK and SELinux
- From embedded Linux boat sensors to the cloud, a data journey
- Running Zephyr and Linux on the same SoC: making both worlds live together !
- Hardware Isolation Running RTOS Concurrently with AGL on Renesas R-Car
- Data continuity, from vehicle sensors to cloud databases in the AGL ecosystem
- From Smack To SELinux
- redpesk® factory demo video
- Embedded Linux, case of AGL. Lesson at ENSTA 2019
- Current Market Conditions for Automotive Supply Implies Long Term Support
- Cloud based test infrastructure to enhance software quality assurance (SQA) in AGL application developments
- Current market condition for automotive supply implies Long Term Support
- AGL-Supervision : From AGL Supervisor to platform global data collection
- AGL-µBinder : a fast, secure and seamless option to connect AGL to small ECUs?
- Wlroots : a potential foundation for Next Generation of AGL Wayland Compositor
- L4RE hypervisor consolidating multiple AGL profiles
- Updated overview of AGL signaling
- Cybersecurity for Connected Vehicle with AGL (Automotive Grade Linux)
- Boot & Secure Boot
- Skim down AGL Application Framework to bridge AGL with hard realtime subsystems
- AGL application design
- 4A (Audio Advanced Architecture) Kickstart with AGL/FF
- Moving AGL toward production with the latest test/monitoring tools.
- From Connected Cars to Connected Boats
- Presentation of AGL
- AGL Development Tools, what's new in FF
- AGL & Real Time: Architecture Options
- Véhicule Connecté Cybersécurité et Open Source
- Projet Etudiant ENSIBS - Analyseurs Statiques de code
- Binding API version 3
- X(cross) Development System update - April 2018
- Vehicle 2 Cloud - Telematics and Data collection - April 2018
- AGL 4a and audio roadmap - April 2018
- Vehicle 2 Cloud - Signaling and Data collection - April 2018
- Industrialisation of applications build in embedded environment
- AGL Audio Advanced Architecture
- IoT.bzh and AGL presentation to ENSIBS' students
- Updated AGL Security Blueprint
- Deploy AGL OS and SDK as a Binary Packaging Distribution for Developer
- AGL integration of systemd and user management
- The AGL Swiss Knife for Quick Application Prototyping
- X(cross) Development System - make AGL app development easier
- Vehicle to Cloud: Connecting Cars to Non-Automotive Internet Services
- Low level CAN binding for AGL: a generic way to handle CAN signals
- AGL Development Kit - Features and Roadmap
- Vehicule Signaling Leveraging OpenXC
- AGL Security Framework Review
- Homescreen a New AGL Platform Service