Firmware

Summary

Firmware is software stored within an electronic component that controls how its hardware starts, communicates, and operates. In modern bicycles, firmware governs functions such as motor assistance, electronic shifting, battery management, sensor processing, suspension control, diagnostics, and component communication.

Firmware can often be updated, but it should be distinguished from user settings and the phone or computer application used to install or configure it.

Key Facts

Category: Technology / Electronic Systems
Defined as: Software embedded in a hardware component
Stored in: Non-volatile memory, commonly flash memory
Runs on: Microcontrollers inside drive units, derailleurs, batteries, displays, sensors, and other electronic components
Primary roles: Hardware control, communication, diagnostics, and protection
Updated through: Mobile apps, wired interfaces, or dealer diagnostic tools
Can affect: Assist response, shifting behavior, compatibility, reliability, and available features
Common platforms: Shimano E-Tube Project, Bosch eBike Flow, SRAM AXS, Avinox Ride, Bafang BESST Pro

Overview

Firmware is a type of software designed for a specific electronic component. Unlike a phone application, it runs directly on the component’s internal processor and remains stored when the bicycle is switched off.

An electronic bicycle does not necessarily have one firmware package. Individual components may each contain their own firmware:

• Drive unit
• Motor controller
• Battery-management system
• Display
• Handlebar controller
• Electronic derailleur
• Power meter
• Electronic suspension component
• Wireless sensor

These components may communicate over a wired or wireless network while performing different tasks. The drive unit might calculate assistance, the battery firmware might manage cell protection, and the display firmware might control the user interface.

This distributed arrangement creates capabilities that are impossible with purely mechanical components, but it also makes version compatibility and long-term software support important parts of bicycle service.

How It Works

Startup and Initialization

When an electronic component is powered on, its firmware initializes the processor, memory, sensors, communication interfaces, and connected hardware.

The component may then perform checks such as:

• Confirming supply voltage
• Verifying sensor signals
• Detecting connected components
• Checking stored settings
• Testing communication
• Loading calibration data
• Reporting faults

Some components also contain a bootloader: a small program responsible for starting the main firmware and managing updates or recovery.

Real-Time Control

After startup, firmware repeatedly reads inputs, performs calculations, and commands the hardware.

In an e-bike drive unit, this may include:

1. Reading rider torque and cadence.
2. Checking wheel speed and assist mode.
3. Calculating requested motor output.
4. Applying current and thermal limits.
5. Commanding the motor controller.
6. Monitoring the result for faults.

These operations must occur consistently and with little delay. Unstable timing or incorrect sensor interpretation can produce surging, delayed assistance, false error codes, or unexpected shutdowns.

Component Communication

Firmware defines how components exchange information. Depending on the system, the network may carry:

• Battery voltage and state of charge
• Rider torque and cadence
• Wheel speed
• Requested assistance
• Gear position
• Button commands
• Temperature
• Diagnostic information
• Component identification
• Firmware-version data

Compatible hardware can still fail to communicate if its firmware versions or system configurations do not match.

Firmware, Applications, and Settings

These terms are related but not interchangeable.

Changing an assist setting does not necessarily rewrite the firmware. The application usually changes a permitted parameter that the existing firmware reads.

Firmware itself is software; the distinction describes where it runs and how closely it is tied to the hardware.

Firmware in E-Bike Systems

Assistance Control

Drive-unit firmware contributes to:

• Assist-mode behavior
• Rider-torque interpretation
• Starting response
• Cadence sensitivity
• Maximum motor current
• Speed-related cutoff
• Motor overrun
• Traction-management functions
• Thermal derating

Two bikes with similar motor hardware can feel different because of firmware, configuration, battery capability, gearing, sensors, and bicycle-manufacturer calibration.

Firmware is therefore a major part of ride character, but not its only source.

Protection and Fault Management

Firmware monitors operating conditions and may reduce or stop assistance when it detects:

• Excessive motor temperature
• Excessive controller temperature
• Overcurrent
• Battery undervoltage
• Implausible sensor data
• Lost speed signal
• Communication failure
• Brake-cutoff activation

The battery-management system may independently enforce its own protection limits. A loss of assistance can therefore originate in the drive-unit firmware, motor controller, BMS, wiring, or another component.

Electronic Drivetrain Integration

Compatible e-bike systems can coordinate motor output with electronic shifting. Firmware may temporarily reduce motor torque, initiate a shift, select a gear automatically, or rotate the drivetrain during coasting.

Functions such as Shimano Auto Shift and Free Shift require compatible hardware and matching firmware across the drive unit and drivetrain. They are not features that can be added to any electronic derailleur through an update alone.

Firmware in Electronic Shifting

Electronic drivetrain firmware controls:

• Button interpretation
• Derailleur-motor movement
• Multi-shift behavior
• Shift timing
• Front and rear derailleur coordination
• Battery monitoring
• Wireless communication
• Fault reporting

Firmware makes derailleur movement repeatable, but it does not eliminate mechanical adjustment or wear. Shifting can still deteriorate because of:

• A bent derailleur hanger
• Worn chain or cassette
• Incorrect B-gap
• Damaged pulleys
• Frame or wheel misalignment
• Impact damage
• Poor chainline
• Incorrect micro-adjustment

An update cannot correct a mechanical fault.

Why Firmware Is Updated

Manufacturers may release updates to:

• Correct known faults
• Improve component communication
• Add supported features
• Refine motor or shifting behavior
• Support new compatible components
• Improve diagnostic reporting
• Address security or reliability issues
• Change regulatory or regional behavior

Not every update produces a noticeable performance change. Some only correct an uncommon fault or prepare the system for future component compatibility.

Firmware updates also cannot add capabilities that require missing hardware. A cadence-only motor cannot become torque-sensing through software, and a derailleur without the necessary communication hardware cannot gain full system integration through firmware alone.

Update Methods

Mobile Application

Many components can receive updates from a phone over Bluetooth. The phone downloads the package and transfers it to the bicycle component.

Examples include:

• SRAM AXS
• Bosch eBike Flow
• Shimano E-Tube Project Cyclist
• Avinox Ride

This process is often described as an over-the-air update, although the component may receive the package locally from the phone rather than directly from the internet.

Wired Interface

Some systems require a physical diagnostic interface. Wired updating may be necessary for:

• Components without wireless-update support
• Dealer-only firmware
• Failed-update recovery
• Replacement-component setup
• Older system generations
• Deep diagnostic access

Shimano notes that certain components require E-Tube Project Professional and the SM-PCE02 interface rather than wireless updating. Shimano E-Tube Project Professional

Dealer Diagnostic Tool

Some updates and configurations are restricted to authorized service centers. Dealer tools may provide access to:

• Complete-system updates
• Fault histories
• Component replacement
• Firmware recovery
• OEM-specific settings
• Diagnostic test routines

User-facing applications generally expose fewer controls.

Version Compatibility

A networked bicycle may require compatible firmware on every connected component. Updating only one part can create version mismatches.

Bosch, for example, advises that all connected components—including the drive unit, controls, battery, optional range extender, ABS, ConnectModule, and compatible shifting system—be present during a complete system update. Missing or outdated components can impair operation. Bosch software compatibility guidance

Compatibility depends on more than the newest version number. It can also depend on:

• Component generation
• Bicycle-manufacturer configuration
• Regional firmware
• Communication protocol
• Optional equipment
• Hardware revision
• Approved compatibility matrix

Firmware intended for one hardware revision should not be installed on another unless the manufacturer explicitly supports it.

Update Risks and Limitations

A firmware update writes new data to the component’s memory. Interrupting that process can leave the component unable to start normally.

Common causes of failed updates include:

• Low component battery
• Loss of Bluetooth connection
• Phone interruption
• Disconnected system component
• Incorrect service cable
• Outdated application software
• Incompatible hardware
• Power loss during installation

Some products automatically recover or retry. Others require a wired service interface or component replacement.

Firmware rollback is not always supported. Once updated, a component may not be able to return to its previous version through normal user tools.

Updates can also change settings, button assignments, calibration values, or perceived ride behavior. These should be checked afterward rather than assuming everything was preserved.

Mechanic’s Perspective

Firmware should be treated as part of the diagnostic process, not as the automatic cure for every electronic problem.

Before Updating

Record:

• Bicycle and system model
• Serial numbers where relevant
• Firmware version of every component
• Current settings and button assignments
• Error codes and fault history
• Customer’s exact complaint
• Battery levels
• Connected optional components

Photograph or export settings when the service platform permits it.

Check the manufacturer’s release notes and compatibility information. Determine whether the update addresses the reported symptom or is simply the newest available version.

Check the Hardware First

Do not use firmware to avoid basic diagnosis. Inspect:

• Battery and component charge
• Connectors and wiring
• Wheel-speed sensor alignment
• Brake cutoffs
• Derailleur hanger alignment
• Chain and cassette wear
• Motor mounts
• Water or impact damage

A firmware update will not repair corrosion, a damaged cable, a failing battery, or a bent hanger.

During the Update

• Use the current official application or diagnostic tool.
• Ensure the phone or computer has adequate charge.
• Charge all bicycle components as directed.
• Maintain a stable internet and Bluetooth connection when required.
• Connect all components included in the update procedure.
• Do not disconnect batteries, cables, or components.
• Do not operate switches unless instructed.
• Keep the bicycle stationary until installation finishes.

For SRAM AXS, each component maintains its own firmware and is updated individually through the AXS mobile application. SRAM AXS firmware guidance

After the Update

1. Confirm that every component reports the intended version.
2. Power-cycle the system if instructed.
3. Check for new or remaining fault codes.
4. Verify button assignments and assist settings.
5. Recheck derailleur micro-adjustment or sensor calibration where applicable.
6. Test every electronic function.
7. Perform a controlled ride under load.
8. Document the completed versions on the service record.

A repair-stand check is not sufficient for evaluating motor response, Auto Shift, torque sensing, or intermittent load-related faults.

Failed Updates

If a component stops responding:

• Do not repeatedly connect and disconnect power without following the recovery procedure.
• Check whether the manufacturer provides a retry or recovery mode.
• Use the approved wired interface when required.
• Preserve error messages and update logs.
• Escalate to the manufacturer or authorized service channel before replacing hardware.

A failed wireless update does not automatically mean the component is permanently damaged.

Replacement Components

A replacement motor, derailleur, battery, or display may require:

• Pairing
• Firmware updating
• System registration
• OEM configuration
• Calibration
• Region or wheel-size programming

Physical installation alone may not complete the repair.

System Dependence and Product Lifespan

Firmware can extend a product’s useful life by correcting faults and supporting new features. It can also create dependence on manufacturer servers, mobile applications, service interfaces, and continued technical support.

When evaluating an electronic system, long-term considerations include:

• Availability of service software
• Dealer-tool access
• Replacement-component support
• Mobile operating-system compatibility
• Firmware recovery options
• Manufacturer support period
• Ability to operate without an account or app

An electronic component may remain mechanically functional after its supporting application or network service is discontinued, but future configuration or replacement can become more difficult.

Common Misconceptions

“Firmware and Software Are Completely Different”

Firmware is a type of software closely tied to hardware. The term distinguishes it from applications and other user-facing programs.

“Updating Firmware Is the Same as Changing Settings”

An update replaces or modifies the component’s operating code. Changing a setting normally edits permitted configuration data.

“The Newest Firmware Will Fix Any Problem”

Updates address specific software issues. They cannot repair mechanical damage, worn components, poor connections, or incompatible hardware.

“Firmware Makes Electronic Shifting Self-Adjusting”

Firmware controls derailleur movement, but hanger alignment, drivetrain wear, setup, and calibration remain mechanical service concerns.

“Every Feature Can Be Added Later”

New functions may require sensors, processors, communications hardware, or compatible components that older systems lack.

“An Update Is Safe to Interrupt”

Loss of power or communication during memory programming can leave the component in a recovery state.

“All Components Update Together”

Some systems update the complete network, while others require each component to be selected and updated separately.

Notable Platforms

Shimano E-Tube Project: Firmware updating, component configuration, diagnostics, and Di2 or e-bike customization. Some procedures require E-Tube Project Professional and a wired interface.

Bosch eBike Flow: User-facing updates for Bosch’s smart system, with deeper diagnostics available through authorized dealers.

SRAM AXS: Individual firmware management and customization for AXS drivetrains, power meters, suspension components, and sensors.

Avinox Ride: Firmware updates, assist configuration, bike status, and connected-system functions.

Bafang BESST Pro: Diagnostics, firmware management, and approved parameter adjustment for supported Bafang systems.

Related Terms

Controller
Motor Controller
Embedded Software
Bootloader
Electronic Shifting
Shimano E-Tube Project
SRAM AXS
Pedal Assist System
Diagnostic Tool
Configuration
Calibration
Communication Protocol

References

NIST Firmware and Software Definitions
Shimano E-Tube Project Cyclist
Shimano E-Tube Project Professional
Shimano Firmware Update FAQ
SRAM AXS Firmware Updates
SRAM AXS Integrations
Bosch E-Bike Software Compatibility Guidance
Bosch Over-the-Air Updates
Avinox Drive System Downloads
Bafang BESST Pro