07 — INCA, CANape, HEX, and ProF Flash Programming

Each completed build produces a matched calibration-tool package in xcp_out/. Keep all files from the same build together; the EPK binds the A2L, HEX, and runtime.

Files to import

INCA device setup

1. Create an XCP on Ethernet (TCP) device.
2. Use the address written by XcpHost in the A2L and the configured Port (default 5555).
3. Import the generated .a2l.
4. Import the generated .hex as the data set/program image.
5. Select the required DAQ raster for each measurement according to the model task rate.

CANape follows the same principle: create the device from the A2L, connect over XCP on TCP, and use the matched HEX for flash/data-set operations.

Install the INCA ProF package

1. Open Memory Page Manager.
2. Choose Utilities → Configure ProF → Install.
3. Select the generated <model>_XCP_Flash_ProF/ directory.
4. In Flash Programming, choose the installed configuration and the generated .hex.

What flashing does

The A2L declares a virtual application programming sector at 0xC0000000 by default. The target receives that image through XCP PGM, writes a staged executable, verifies it, then commits an atomic swap on successful completion/disconnect or program reset. A backup runtime is retained by the target for rollback.

Calibrated data versus runtime flash

Flashing updates the executable and reference/default calibration data embedded in the HEX. A calibration session may still contain edited values on the INCA working page. If INCA reports the reference checksum as matching but the working page as different, synchronize/download the working data set to the ECU working page; this is not automatically implied by flashing the application.

Quick fault isolation