Echo and Calibration Example
CD6 Echo
This handwritten application copies received Model IPC frames back to the dash
every 5 ms. It uses the public CDX callbacks and retains queued frames when the
runtime is busy. For a visible dash-channel example, start with project-template
instead.
Project Layout
1echo/
2 cdx-runtime/ Extract the runtime here; replace as a whole for updates
3 main/ Application, version and calibration headers
4 ginmake-generated/ Created automatically during the build
5 build/ Build output
6 CMakeLists.txt Your application build and packaging commands
7 CMakePresets.json Release and Debug presets
8 model-ipc.json5.in Your Ginmake configurationCopy this entire example outside cdx-runtime, then extract the runtime ZIP into
the copied project. Install the tools listed in
Installing Tools. From the copied project’s root:
1cmake --preset cm4-release -DCDX_RT_TOOLCHAIN_BIN="C:/sysgcc/arm-eabi/bin"
2cmake --build --preset cm4-releaseThe comments in CMakeLists.txt identify the application sources, optional
calibration and two runtime helpers. Common linking, generation bookkeeping and
the complete packaging command live in cdx-runtime, not in this project.
Import build/cm4-release/CD6-echo.cdxmodel into Dash Design and load the setup
onto a CD6 with model-runtime support. The finalized binary is
build/cm4-release/MDL_FIRM.bin. Do not deploy MDL_FIRM.raw.bin.
This example has no DBC interface. Do not add Model IPC DBC routes to its setup. The resulting interface mismatch prevents startup. This is a callback/queue example, not a ready-made dash display demonstration. Use the project-template example for that.
Calibration
main/version.h defines this application’s REV_NAME and REV_VERSION directly.
The generated A2L uses these values for identification.
Enable the gain/offset tutorial in a fresh build directory:
1cmake --preset cm4-release -B build/calibration -DAPP_ECHO_CALIBRATION=ON -DCDX_RT_TOOLCHAIN_BIN="C:/sysgcc/arm-eabi/bin"
2cmake --build build/calibrationKeep ginmake-generated/a2l/CD6-Echo.a2l with the matching firmware.
The first payload byte becomes min(255, byte * gain + offset). The default gain
of 1 and offset of 0 leave it unchanged. Use a matching XCP connection on external
CAN1 or CAN2 to change parameters. To save changes, request STORE_CAL and wait
for completion. Persistence requires working dash storage.
Build configurations share ginmake-generated, so build them sequentially.
Use cm4-debug for Debug. To update, follow the runtime’s
verified upgrade and backup sequence.
Keep your edits outside the runtime folder and regenerate the deployment setup
before uploading the new build.