Korhex MCU Access for ECU Programming with Flex

Korhex: Direct MCU Access for ECU Programming with Flex

Advanced hardware access for next-generation ECU unlocking and Boot Glitch procedures

Modern ECUs integrate increasingly advanced hardware and software protection systems. Accessing and unlocking these control units requires dedicated procedures and, in some cases, direct interaction with the ECU microcontroller (MCU).

Korhex is the hardware solution developed by Magicmotorsport to provide direct MCU access through Flex during supported ECU unlocking and Boot Glitch procedures.

What is Korhex?

Korhex is a dedicated hardware extension for the Flex ECU and TCU programmer.

It works directly within the Flex ecosystem and enables access to a specific contact point on the microcontroller of supported ECUs during advanced access, unlocking and Boot Glitch procedures.

Korhex is not a standalone ECU programmer: Flex manages the procedure, guides the operator through each step and handles the subsequent ECU programming operations.

How does Korhex work?

Korhex interacts with a specific contact point on the ECU microcontroller.

Using the dedicated Korhex accessories and masks, the device is positioned on the MCU contact point indicated by the corresponding Flex procedure.

Flex then guides the operator step by step through the required access and unlocking process.

On selected applications, Korhex uses EMFI – Electromagnetic Fault Injection technology to interact directly with the processor during the access procedure.

The result is a simpler, more controlled and repeatable ECU workflow, with fewer manual operations on the control unit.

Fewer manual operations during ECU access

Traditional Boot access procedures can require several physical operations on the ECU PCB.

On supported control units, Korhex simplifies this preparation.

There is no need to:

work on the opposite side of the PCB;
desolder resistors;
manually connect Boot pins;
perform the soldering operations required by traditional procedures.

Simply position Korhex on the designated MCU contact point and follow the guided procedure directly in Flex.

This helps reduce ECU preparation and makes advanced access procedures faster and easier to reproduce in the workshop.

Korhex + Flex: one integrated ECU programming workflow

Korhex has been developed specifically to work with Flex, Magicmotorsport’s professional ECU and TCU programmer.

Together, Flex and Korhex extend the possibilities for working on protected next-generation ECUs that require advanced microcontroller access.

The entire workflow is managed through Flex:

MCU access → ECU unlocking → ECU programming

From accessing the microprocessor to performing the unlock and continuing with Read and Write operations, the procedure remains integrated into the Flex environment.

Position. Access. Unlock. Program.

What can Korhex be used for?

Depending on the ECU and the corresponding Flex protocol, Korhex can be used for supported operations including:

direct MCU access;
ECU unlocking;
Boot Glitch procedures;
advanced access to protected ECUs;
procedures based on EMFI – Electromagnetic Fault Injection;
subsequent ECU Read and Write operations through Flex.

Supported operations depend on the specific ECU, microprocessor and Flex protocol.

Which Flex license do I need for Korhex?

Supported Korhex and Boot Glitch procedures are available with the following Flex configurations:

Flex Full

FLS0.5M / FLS0.5S

Flex Full Master
Flex Full Slave

Flex Boot Glitch

FLS0.20M / FLS0.20S

Flex Boot Glitch Master
Flex Boot Glitch Slave

If you already have an eligible Flex Full configuration, supported Korhex procedures are included.

If you use a Flex configuration other than Full, you can add the FLS0.20M/S Boot Glitch license to access the supported Boot Glitch protocols.

Which ECUs are supported by Korhex?

Korhex support continues to expand through new Flex releases.

Compatibility depends on the specific ECU, MCU, vehicle application and Flex protocol.

The supported ECU list includes next-generation control units requiring advanced access procedures and is continuously updated as new Flex protocols are released.

Check the Flex Vehicle List to verify whether a specific ECU, microprocessor or vehicle is currently supported.