OBD access
OBD access uses the vehicle diagnostic connector and is normally the least invasive workflow. Availability can depend on ECU software, unlock state, virtual-read support and the functions licensed in the programming tool.
A virtual read is not necessarily a byte-for-byte read from the installed unit. Confirm how the tool obtains the file and whether the returned software matches the vehicle identity before calibration.
Bench access
Bench communication takes place with the control unit removed or electrically isolated and connected through its external connector. Correct pinout, stable regulated voltage, ground integrity and tool-specific wiring are essential.
Bench can provide a useful route when OBD access is unavailable, but the label ‘Bench’ does not guarantee identical memory coverage across ECUs and tools.
Boot access
Boot access generally requires opening the unit and using designated pads or pins to place the processor in a service mode. It can provide deeper memory access and recovery options, while adding physical handling and sealing risks.
ESD control, correct opening technique and manufacturer-specific connection instructions matter. Do not rely on a generic family diagram when board revisions can differ.
Selection and recovery checklist
Confirm ECU identifiers, protocol version, read type, checksum behavior, expected file size and recovery capability. Maintain a stable power supply and prevent vehicle systems from entering sleep or waking unexpectedly during OBD work.
The safest method is the one explicitly supported for the exact hardware and software with a known recovery path—not automatically the fastest method shown in a marketing table.