Linus B.

Experience, achievements, and practical sense.

These are the main tools to bridge the gap between your desire to create a product and its realization.

To travel this road, you can count on my background, which began with a degree in electronics before moving on to writing firmware and drivers, all the way up to the Linux Kernel.

Writing a driver or firmware means understanding the subtleties of the controlled components. Unfortunately, just reading the documentation is not enough, and my generalist experience will make the difference. Our collaboration can be built on two pillars: Method and Skill.

⇰⇰⇰ My Method:

↣ Define the specifications: clear milestones, dated deliverables, checkpoints for adjustments.

↣ Adapt to your context: Use your reference boards, software, documentation, and state-of-the-art.

↣ Ensure autonomy & efficiency: Through refactoring capabilities in my workshop: microscope, reflow station, power supplies, logic analyzer, oscilloscope, function generator, probes (JTAG, ...).

↣ Deliver knowledge and technical production: Documented achievements in publication format (FR/EN). Atomic commits to facilitate integration.

⇰⇰⇰ My Skills (references available)

↣ Kernel performance improvement: Execution speed, memory access time, CPU consumption.

↣ Driver writing (kernel or MCU): Communication via SPI, I2C, UART, OneWire buses... Integration of diagnostic tools from the design phase.

↣ Failure analysis/debugging: in-vivo or post-mortem on kernel panics, oops, coredumps.

↣ Electronic board design: Routing, production, small series with debug capabilities, associated tests.

↣ Industrial RF: Awareness of EMC compatibility, antenna routing.

↣ Audit and State-of-the-Art: code, functions, or components. Technical proof or prototypes demonstrating in-situ performance.

See you soon on the phone or in my workshop to discuss your needs over a coffee (Irish or regular 😊).