Firmware & software reconstruction

Abandoned by the manufacturer.
Not by us.

When a vendor discontinues a device, the hardware keeps working but the software around it falls behind. The admin page stops opening in current browsers, the encryption is years out of date, and nobody ships security fixes. We rebuild the firmware and software from scratch, so the equipment stays secure, reachable and on the network it already belongs to.

  • TLS 1.3 and modern ciphers
  • Works in current browsers
  • No rewiring or recommissioning

Platforms we've brought back

  • Singer Futura embroidery
  • Echelon i.LON 100
  • Echelon RNI
  • Echelon SmartServer
  • IFSF fuel dispensers
  • Payment card readers
  • ARM & MIPS embedded Linux

The problem

Equipment outlives its software

Industrial and professional hardware is built to run for twenty years. Vendor software support rarely lasts half that.

The admin page won't open any more

Current browsers refuse the old encryption, and the Java applets, Flash or ActiveX controls the interface was built on no longer run anywhere.

The device is a weak point on your network

Cleartext Telnet and FTP, shared factory passwords and a kernel from the 2000s. A forgotten controller is an easy way into a building or plant network.

The PC software won't install

It was written for Windows XP, needs an unsigned driver, or phones home to an activation server that was switched off years ago.

Replacing it costs far more than the device

Swapping a controller that sits on a field bus means rewiring, recommissioning and downtime. New firmware for the box you already have is usually cheaper and safer.

Security

Secure the device. Protect the network it sits on.

Every rebuild gets current cryptography, a minimal attack surface and a way to keep receiving updates. Below is what we typically find on a discontinued controller, and what we replace it with.

Area Vendor firmware, as shipped After Unsunset
Protocol SSL 3.0, TLS 1.0 TLS 1.3, with TLS 1.2 (AEAD suites only) for older clients
Ciphers RC4, 3DES-CBC, static RSA key exchange AES-256-GCM, ChaCha20-Poly1305, X25519 forward secrecy
Certificate RSA-1024 with SHA-1, self-signed, often expired ECDSA P-256 from your own CA, or renewed automatically over ACME
Remote admin Telnet and FTP, passwords sent in cleartext SSH with Ed25519 keys and SFTP. Cleartext services off by default
Credentials One factory password shared by every unit Unique per unit, changed at first login, optional LDAP or RADIUS
Operating system RTOS or kernel from the 2000s, no patches Long-term-support Linux kernel on a published patch schedule
Updates Unsigned images, no way back if a flash fails Signed images, A/B install, automatic fallback to the last good version

Least exposure

A default-deny firewall. Only the ports the device actually needs are open, and management can be bound to a separate VLAN or interface.

Logs you can use

Authentication, configuration changes and faults are sent over syslog to your SIEM, so the device stops being a blind spot.

When the hardware can't keep up

Some devices are too small for modern cryptography. We put a hardened gateway in front that speaks TLS 1.3 to your network and the old protocol on an isolated link.

Tested, not assumed

Every release is scanned for weak protocols, open ports and known vulnerabilities before it ships. You receive the report with the image.

Paperwork for compliance

We document the security controls on each device against IEC 62443-4-2, which helps with NIS2 and Cyber Resilience Act obligations.

Security fixes that keep coming

Support plans include kernel and library patches, certificate renewal and advisories when a vulnerability affects your devices.

Modern browsers

Open it from any current browser

Since 2020, Chrome, Firefox, Safari and Edge have refused TLS 1.0 and 1.1. Java applets, Flash and ActiveX are gone completely. For many older devices that means the admin page shows a security error or a blank frame.

  • A new web interface in standard HTML, with no plugins and no "IE mode"
  • Works in current Chrome, Firefox, Safari and Edge, on desktops, tablets and phones
  • Direct USB and serial connections from the browser via WebUSB and WebSerial, with no drivers to install
  • Existing integrations such as SOAP, Modbus/TCP and BACnet keep working
https://ilon-boilerhouse.plant.local

This site can't provide a secure connection

ilon-boilerhouse.plant.local uses an unsupported protocol.

ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Drop-in

The device stays where it is. So does your network.

We change the software inside the box and nothing around it. Addresses, wiring, field-bus bindings and the systems that talk to the device carry over unchanged.

  1. Unchanged

    Supervisory system

    Your BMS, SCADA or back office keeps the same endpoints and data points.

  2. Unchanged

    IP network

    Same IP address, hostname, VLAN and firewall rules.

  3. New firmware

    The device

    Same hardware and mounting. Configuration is imported from the running unit.

  4. Unchanged

    Field bus

    LonWorks, Modbus or serial addresses, bindings and wiring stay as they are.

Reversible. Wherever the hardware allows it we keep the original boot loader, so a unit can go back to the vendor firmware.

Rolled out unit by unit. One device at a time, during normal maintenance windows, with a rollback plan written down for each one.

Selected work

Devices we've brought back

Each project starts with hardware the vendor no longer supports and ends with software you can run, read and maintain.

Building automation · Firmware

Echelon i.LON 100 & RNI: from VxWorks to Linux 6.6

These LonWorks/IP servers still run heating, ventilation and lighting in many buildings, on an operating system that has been out of support for over a decade. We ported a current long-term-support Linux kernel to the original MIPS hardware and reconstructed the driver for the LonWorks chip from the vendor firmware.

Before
VxWorks 5.5.1
After
Linux 6.6 LTS, Yocto
CPU
Au1000, MIPS32 BE, 264 MHz
Boot image
1.6 MB, about half the original
  • Original bootrom kept, so the vendor firmware can still be booted
  • Upgrades fall back automatically to the previous image if one fails
  • Every build tested under emulation before it reaches real hardware

Embroidery · PC software

Singer Futura, now in the browser

The Futura machines needed Windows-only software and a USB driver that no longer loads. We recovered the USB protocol and wrote a new app that runs in Chrome or Edge over WebUSB, including on a Chromebook.

  • Imports DST, EXP, JEF and native designs, with validation
  • Stitch editor, lettering, fills, satin and appliqué
  • None of the vendor's code, only the same protocol

Building automation · Server

Echelon SmartServer

Maintenance for controllers whose vendor support has ended. That means security patches, certificate renewal, and integration with current BMS and IoT platforms.

  • Cleartext services replaced, TLS 1.3 throughout
  • Documented upgrade path for every unit

Fuel retail & payments

Dispensers, card readers and more

IFSF dispenser protocol simulators, card-reader SDK research, and ports of discontinued vendor software to current ARM boards such as Raspberry Pi and Rockchip.

  • Protocol implementations that follow the published standards
  • Replacement drivers for new host hardware

Services

What we do

Firmware reconstruction

New boot chains, kernels and root filesystems for discontinued hardware, built reproducibly with Yocto and Buildroot.

Replacement PC & web apps

Modern, cross-platform software for machines tied to dead operating systems, including browser apps over WebUSB and WebSerial.

Security hardening

Modern TLS, key-based admin access, a closed attack surface and signed updates for devices that have to stay on the network.

Protocol recovery

USB, serial, field-bus and network protocols captured, decoded and written up as specifications you can build against.

Hardware emulation

QEMU-based device models, so firmware is tested automatically before it is flashed to scarce real units.

Long-term support

Maintenance measured in years, with a clear update channel and an engineer who answers when a unit misbehaves.

Process

How a device gets a second life

  1. 01

    Assess

    We review the device, scan it for security problems, and agree what a good outcome looks like. You get a written report and a fixed-scope proposal.

  2. 02

    Recover

    Flash dumps, bus captures and binary analysis. We document how the device behaves before we change anything.

  3. 03

    Rebuild

    New firmware or software written from the recovered specification. It is original code, structured so others can maintain it.

  4. 04

    Validate

    Automated tests in emulation, then on real hardware, plus a security scan of every release candidate.

  5. 05

    Support

    Rollout unit by unit, full documentation and source handover, and optional long-term maintenance.

Working with us

Three ways to start

Every engagement is fixed price, agreed before work starts.

Assessment

For when you need to know where you stand.

  • Review of one device model
  • Network and security scan
  • Written report with risks ranked
  • Options, timeline and a fixed quote

Rebuild

New firmware or software for a device family.

  • Reverse engineering and specification
  • Firmware, web interface or PC app
  • Testing in emulation and on your hardware
  • Source code, build system and documentation

Support plan

For devices that have to stay safe for years.

  • Security patches and certificate renewal
  • Vulnerability advisories for your fleet
  • Agreed response times
  • Annual compatibility and security review

Principles

Clean code, clean conscience

Reverse engineering for interoperability is lawful in most jurisdictions, and we work strictly within those limits.

Original code only
We reimplement behaviour, not binaries. Vendor code is never copied into what we ship.
Interoperability first
The goal is to keep hardware you own working. We don't break DRM or defeat licensing.
Documented by default
Every protocol and every build step is written down, so you are never stranded a second time.
You own the result
Source code, build systems and specifications are handed over. You are not locked in to us.

Toolbox

  • Yocto
  • Buildroot
  • U-Boot
  • Linux LTS
  • ARM
  • MIPS
  • PowerPC
  • C / C++
  • Rust
  • Python
  • TypeScript
  • WebUSB
  • WebSerial
  • TLS 1.3
  • OpenSSH
  • nftables
  • ACME
  • LonWorks
  • IP-852
  • BACnet
  • Modbus
  • IFSF
  • QEMU
  • Ghidra
  • Frida
  • Logic analysers

FAQ

Questions we get asked

Something else? Ask us directly.

Is this legal?

In the EU and the US, reverse engineering to make independent software work with hardware you own is permitted under specific conditions (EU Software Directive 2009/24/EC, Article 6, and 17 U.S.C. §1201(f)). We check each project against those conditions and never redistribute vendor code. This is not legal advice, and we're happy to work with your own counsel.

Can we go back to the original firmware?

Wherever the hardware allows it, yes. We keep the original boot loader and give you a documented way back. If a device can't be made reversible, we tell you during the assessment, before any work starts.

Do we need to change our network or wiring?

No. The device keeps its IP address, hostname and field-bus configuration, and the systems that talk to it keep working. You can optionally move management to a separate VLAN.

What if the device is too old for modern encryption?

Some processors and memory sizes can't run TLS 1.3 at a usable speed. We then put a small hardened gateway next to the device that handles encryption towards your network and talks to the device over an isolated link.

Do you need a physical unit?

Usually one or two sample units for the reconstruction work, which we return. Any firmware images, manuals and captures you already have make the work faster.

Who owns the code?

You do. You receive the source code, the build system and the specifications. We can keep maintaining it under a support plan, but you are never dependent on us.

How long does a project take?

An assessment usually takes about two weeks. The assessment report gives a timeline and a fixed price for the rebuild, which depend on the device and on how much of it needs to change.

Contact

Have a device the vendor gave up on?

Tell us what it is and what stopped working. We reply within two working days with an initial assessment, at no cost.

What do you need?