Maintenance and takeover of electronic products and firmware
Picodev, a design office in Aix-en-Provence, takes over the maintenance of your product, even one developed by another provider: code audit, fixing persistent bugs, new features, technology upgrades and replacement of components that are no longer made. For companies that keep a product on the market alive.
Picodev, a design office in Aix-en-Provence, takes over the maintenance of your product, even one developed by another provider: code audit, fixing persistent bugs, new features, technology upgrades and replacement of components that are no longer made. For companies that keep a product on the market alive.
What we do
Audit of the existing product
We start with a review: source code, build tools, documentation, progress if a provider is still working on the product. The audit tells what works, what is missing and what is fragile, and sets priorities. It can also be used to follow the work of a provider in progress.
Taking over firmware or software
We take over a product developed by another team, even without its original documentation. First step: being able to rebuild exactly the version running in the field. Without that, no fix is safe.
Corrective maintenance
Bugs that persist across several releases often have a deep cause: missing error handling, a shared resource, an edge case never tested. We look for that cause rather than hiding the symptom.
Evolutive maintenance
New features, new hardware, new requirements: we evolve the product, and we restructure the code when needed so that the next changes stay simple.
Dependencies and security fixes
A connected product embeds libraries and often an operating system. We keep them up to date and apply security fixes, for example on a Yocto Linux distribution.
Obsolescence
When a component is no longer made, we look for a replacement, assess the impact on the board and the firmware, then adapt and test the software.
When to call on us
- Your provider or developer is no longer available.
- Bugs keep coming back despite fixes.
- A component on your board is reaching end of life.
- Your product must evolve, but nobody knows its code well any more.
- You want an independent opinion on a development in progress.
Technologies
C, embedded Linux, Yocto, STM32, PIC18, Bluetooth Low Energy, Android.
What you receive
- An audit report: review and priorities.
- The fixed and documented code.
- A documented build procedure.
How we work
- Collecting the code, the tools and the documentation.
- Audit and list of priorities, discussed with you.
- Fixes and changes in releases, tested on the real product.
- Long-term maintenance, or handover to your teams.
Related projects
- Eat Machine – Eat Machine, a connected fridge for food service: Picodev developed the firmware of several generations (embedded Linux, Android) and over-the-air updates.
- Biody Xpert – Biody Xpert by Aminogram, a professional impedance meter: Picodev created a secure BLE protocol, reworked the PIC18 firmware and built a test app.
- Legrand – Legrand, electrical and digital building infrastructure: Picodev maintains a custom Yocto embedded Linux system, with component updates and security fixes.
Before you entrust us with your project.
Can you take over a product without its original documentation?
Yes, from the source code. The audit rebuilds what is missing: architecture, build tools, weak spots.
Can you audit the work of a current provider?
Yes. We offer supervision or code audit assignments to better understand how the work is progressing.
A component is no longer made: what can we do?
We look for a replacement component, assess the impact on the board and the firmware, then adapt and test the software.
Do you work on one-off assignments?
Yes, to unblock a difficult technical situation, or over the long term, within your teams.
Let's talk about your connected device.
Fill in our project form or write to us.