From February 25th to 27th in Nuremberg, Germany, we will have another edition of Embedded World, the leading international fair for embedded systems.
[
]
The embedded world trade fair enables the visitors to experience the whole world of embedded systems, be it security for electronic systems, distributed intelligence, the Internet of Things or e-mobility and energy efficiency.
In this edition, according to the organization, we will have more than 1,100 exhibitors, numerous speakers from 52 countries, more than 32,000 trade visitors and approximately 2,200 conference participants from 77 countries.
The Embedded World Conference 2020 is structured along 10 subject areas:
- Internet of Things
- Connected Systems
- Embedded OS
- Safety & Security
- Hardware Engineering
- Software & Systems Engineering
- Embedded Vision
- Autonomous & Intelligent Systems
- Embedded GUI & HMI
- System-on-Chip
The conference will cover different subjects, including communication protocols, RTOS, Linux, Android, Yocto Project, virtualization, security, cryptography, RISC-V, MISRA, agile for embedded, C/C++ programming, embedded GUI, ARM Cortex-M, FPGA, operating systems, industry standards, multicore, memory architectures, AUTOSAR, artificial intelligence, IoT, GPUs, containers, power management, DSP, hypervisors, OpenAMP, computer vision, Qt, and many more!
I’ll be there for the first time, being one of the speakers at the conference, alongside experts in the field like Robert Berger, Chris Simmonds, Niall Cooling, Colin Walls, Joseph Yiu, Karim Yaghmour, and many others.
My talk’s title is “Linux kernel debugging: going beyond printk messages”, with the following description:
“Debugging the Linux kernel with printk messages is a common technique. And often a good one. The problem happens when we only know this debugging technique. How to debug a kernel oops message? How to trace and understand the kernel execution? How to identify and analyze a buffer overflow? How to identify a memory leak or a deadlock in kernel space? In many situations, there are more effective kernel debugging tools and techniques, including KGDB, ftrace, addr2line, eBPF, kmemleak, and so on. In this presentation, we will go over these and many other very useful tools to identify and fix problems in the Linux kernel.”
If you happen to show up there, stop by to say hello!
About the author: Sergio Prado has been working with embedded systems for more than 25 years. If you want to know more about his work, please visit the About Me page or Embedded Labworks website.
Please email your comments or questions to hello at sergioprado.blog, or sign up the newsletter to receive updates.