fupsrl

10 — Troubleshooting, Validation, and Support Bundle

3 min read Updated 15 July 2026

This checklist follows the workflow order: model configuration, code generation, local toolchain, artefact generation, deployment, then calibration-tool connection. Record the exact model, EPK, target profile, WSL distribution/sysroot, and target image before investigating a fault.

Build and toolchain issues

Symptom Likely cause Action
Compiler is not found Selected WSL distribution lacks the cross compiler. Leave AutoProvisionToolchain=true, set WslDistribution explicitly, or configure the compiler fields manually.
Wrong ELF architecture Profile/compiler does not match the target ABI. Select the matching TargetProfile; inspect the generated ELF before deployment.
Target cannot start the runtime GLIBC/dynamic-loader mismatch or missing target userspace libraries. Build with a sysroot matching the oldest supported Linux image; verify on the board with loader/error output.
Stage-directory error Stage path overlaps a protected project/output/dependency path. Use the default dedicated xcp_build or a safe external staging directory with AllowExternalStage=true.
Missing model parameter variable Legacy base-workspace initialisation did not run. Check modelParams.m, set ModelInitScript, or move values into a data dictionary/model workspace.

A2L and calibration issues

Symptom Likely cause Action
DWARF address resolution fails Unstripped debug ELF is missing, incompatible, or the generated object layout changed. Use the build ELF, not the stripped runtime; rebuild the complete artefact set and inspect generated parameter storage.
Lookup appears as separate vectors Table/axes are input ports, expressions, lookup objects, n-D, or not simple dialog parameters. Use an explicit 1-D/2-D standard lookup with named dialog parameters when one CURVE/MAP instrument is required.
Dangling axis reference error A filter excluded a dependent lookup axis. Review CalibrationAllow/CalibrationDeny; retain the table and its axes together.
No calibration object Parameter is not tunable or is filtered out. Make the parameter tunable, verify its generated storage, then review filters.
EPK mismatch A2L, HEX, and runtime are from different builds. Re-import the matched A2L/HEX after every rebuild and deploy the corresponding runtime.

Deployment and connection issues

Symptom Likely cause Action
SSH timeout Board is powered off, address/routing is wrong, or port 22 is blocked. Confirm reachability outside MATLAB, correct host/user/host key, then retry deployment.
Deploy rejected in offline mode Offline=true intentionally blocks network operations. Use Offline=false only for the deployment call.
INCA/CANape cannot connect Wrong A2L endpoint, service not running, network/firewall issue, or wrong TCP port. Set XcpHost correctly before A2L generation; verify target service and port 5555 or the configured port.
Model overruns with DAQ active CPU contention or too much measurement traffic. Separate cores, reduce signal/raster load, review diagnostics, and increase queue/memory only when justified.
GPIO status reports failure Bad chip/line mapping, pin mux, or permissions. Validate the board profile, device tree, and /dev/gpiochip* access on target.

Minimal validation sequence

  1. Run offline build successfully and archive the A2L/HEX/ProF artefacts.
  2. Validate output ELF architecture and target userspace compatibility.
  3. Deploy one runtime and verify service start.
  4. Connect XCP; measure diagnostics at each model raster.
  5. Change one safe calibration parameter; validate readback/checksum and persistence if needed.
  6. Flash a matched runtime in a controlled environment and confirm restart/EPK.
  7. Document target image, model version, EPK, and result for traceability.

Support bundle to collect

When requesting support, include the MATLAB error/output, model name, MATLAB release, target profile, exact toolchain/sysroot, generated A2L/HEX EPK, target service log, and the calibration-tool connection/flash log. Never include live passwords in a ticket or documentation screenshot.