A key part of your product is going to the end of life? Keep shipping without starting from zero.
We replace end-of-life (EOL) and NRND parts in your product. We redesign the board, port the firmware to a new microcontroller, or do both. Your product keeps its features, and we aim to keep its enclosure and connectors.
A notice from your supplier gives you two choices. You buy enough stock for the rest of the product’s life, or you redesign. We help you pick the cheaper path and then do the work.
| Last-time buy | Redesign | |
|---|---|---|
| Cost now | Cash tied up in stock for years | Engineering cost, spread over a few months |
| Risk | You guess future demand. Too little stops sales, too much is waste. | New board and firmware need testing |
| Best when | The product ends within 1 to 2 years | The product still sells and will keep selling |
| Extra gain | None | Lower BOM cost, new features, a supply chain that lasts |
Many teams do both. They buy a bridge stock to cover sales while the redesign runs.
You choose the part of the work we take. Your team keeps the rest.
Hardware redesign: We pick a replacement microcontroller or part with long-term supply, such as STM32. We redesign the schematic and PCB layout around it. We keep the board outline, connectors, and pinout where we can so the enclosure and cables stay the same.
Firmware port: Your team builds the new board. We move your firmware to the new microcontroller or wireless module. We keep every existing function, and we can move bare-metal code to an RTOS such as FreeRTOS on the way.
Hardware and firmware together: One team handles both sides. Board and firmware issues get found and fixed in the same place, so you deal with one supplier.
MCU families we work with: STM32, Nordic nRF52 and nRF53, and ESP32-D0WD.
If your product also needs new features, see Electronic product redesign (V2) at /solutions/electronic-product-redesign/.
Review: We check your BOM, schematic, and firmware. We list every part at risk, not only the one in the notice, and propose replacements with long-term supply.
Plan: We agree the scope, what must stay the same, and what tests prove the new version matches the old one.
Redesign and port: We build the new board, the new firmware, or both. You see progress in weekly calls and in your own repository.
Verify: We test the new version side by side with the old one. We flag any change that affects your certifications early, so you can plan the retest.
Hand over: You get the design files, the source code, a test report, and production files for your manufacturer.
The microcontroller in a customer’s engine controller was discontinued. Without a fix, they could not sell the product any more. Their team designed new STM32 hardware in-house and asked us to port the firmware.
We moved the bare-metal application to STM32 with FreeRTOS. We split it into tasks for CAN, display, memory, and the main control loop. Every existing function stayed intact.
Result: The customer keeps selling the product to new and existing users.
You send the BOM, the schematic, and the supplier notice. If we port firmware, add access to the source code. Within a few working days you get a written review with:
If you go ahead, we do the work. If you do it in-house, the review is yours to keep.
German contract: You sign with Oxeltech GmbH in Berlin. NDA first, then work.
Microcontroller experience: We have shipped firmware on STM32 for battery management systems, engine controllers, and RED-compliant IoT hardware, and on Nordic nRF5340 for BLE wearables.
One team for firmware and hardware: We find board errors during firmware work, so you avoid a second supplier.
Your code stays yours: We work in your repository. You get all source code and design files.