<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Custom Models (CDX) :: CD6 Manual</title>
    <link>/models/index.html</link>
    <description>A CD6 can run a custom model: your own application, generated from a Simulink® model or written in C, on a processor reserved for it. The model works alongside the display setup. It does not replace it. The CDX Model Runtime is the software you build the model with: a runtime library, public API, build tools and the cdx command-line interface.&#xA;What Models Are For&#xD;The CD6 has two processor cores. The display firmware runs on the Cortex-M7. It does everything configured in a Dash Design setup: inputs, channels, CAN, screens, logging and outputs. The Cortex-M4 is reserved for a custom model.</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="/models/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Quickstart: Hello World</title>
      <link>/models/readme.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/readme.html</guid>
      <description>CDX Runtime Quickstart&#xD;The CDX Model Runtime runs your own application, a Simulink model or C code, on the CD6’s dedicated Cortex-M4 model processor, alongside the display firmware. The model receives dash channel values, runs at a fixed rate and sends results back as new dash channels. The display setup can then show, log or transmit them like any other channel. Use a model for control strategies, calculations and logic beyond what a Dash Design setup can express.</description>
    </item>
    <item>
      <title>Installing Tools</title>
      <link>/models/doc/tools.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/doc/tools.html</guid>
      <description>Installing Tools&#xD;Building a CDX application needs an Arm compiler, CMake, Ninja and a licensed Ginmake. Programming a display needs GEMS Dash Design. MATLAB is needed only to generate code from your own Simulink models.&#xA;The Quickstart runs the install script and builds the starter. This page covers the script’s options, manual installation and compiler selection.&#xA;Install Tools Script&#xD;From the project root, run the signed installer supplied with the runtime:</description>
    </item>
    <item>
      <title>Application Template</title>
      <link>/models/examples/project-template/readme.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/examples/project-template/readme.html</guid>
      <description>CD6 Project Template&#xD;This handwritten starter receives dash analogue values through Ginmake-generated IPC getters and sends calculated values back every 5 ms using setters. It has no console output. The Quickstart creates a project from it, builds it and runs it on a CD6. This page explains how it works and how to replace it with your own model.&#xA;Project Layout&#xD;1project-template/ 2 cdx-runtime/ Extract the runtime here; replace as a whole for updates 3 main/ Application callbacks and model-owned headers 4 ipc/ DBC definitions shared with Dash Design 5 model-generated/ Optional Embedded Coder C sources 6 ginmake-generated/ Created automatically during the build 7 build/ Build output 8 CMakeLists.txt Your application build and packaging commands 9 CMakePresets.json Release and Debug presets 10 cdx-project.json CLI workflow defaults 11 model-ipc.json5.in Your Ginmake configuration&#xD;Build&#xD;Copy this example outside cdx-runtime and extract the runtime ZIP into the copy. Install the tools listed in Installing Tools. From the project root:</description>
    </item>
    <item>
      <title>Model Integration</title>
      <link>/models/integration.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/integration.html</guid>
      <description>This page explains how a CDX application connects to the dash: its project structure, the Model IPC interface, Simulink integration and calibration. Build and run the Quickstart first.&#xA;Project Structure&#xD;A CD6 application owns its source code and build configuration. The CD6 runtime release is extracted into a cdx-runtime folder inside the project:&#xA;1my-model/ 2 cdx-runtime/ Prebuilt runtime, headers and build tools 3 main/ Application callbacks and headers 4 ipc/ DBC definitions for the Model IPC connection 5 model-generated/ C sources from Embedded Coder, if used 6 ginmake-generated/ IPC sources generated by Ginmake 7 build/ Compiled firmware and model package 8 CMakeLists.txt Application build configuration 9 CMakePresets.json Release and Debug presets 10 cdx-project.json CDX CLI project configuration 11 model-ipc.json5.in Ginmake configuration&#xD;Keep your changes outside cdx-runtime. The whole runtime folder can then be replaced to change versions without replacing your application. See Updating the Runtime.</description>
    </item>
    <item>
      <title>Simulink Projects</title>
      <link>/models/doc/simulink.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/doc/simulink.html</guid>
      <description>Simulink Projects&#xD;This guide sets up a Simulink model so that cdx build and Dash Design’s CDX Project Tools generate, compile and package it without manual steps. It extends the Quickstart, which builds the hand-written starter without MATLAB. Complete that first build before adding a model.&#xA;Alternatively, start with the self-contained Simulink Bench example. Its original stock-block model is created by a MATLAB script rather than a release-specific binary model file, and its adapter demonstrates IPC, fast I/O and persistent XCP parameters without any customer project dependencies.</description>
    </item>
    <item>
      <title>Simulink Bench Example</title>
      <link>/models/examples/simulink-bench/readme.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/examples/simulink-bench/readme.html</guid>
      <description>Simulink Bench&#xD;An independent CD6 bench example, not derived from a customer application. It conditions two views of Analogue 1 with result = clamp(voltage * gain + offset, 0, 10 V): one received through normal Dash channel evaluation/Model IPC, the other acquired through the fast ADC API. Both paths execute in one 1 ms Simulink step.&#xA;Use an isolated bench CAN bus only. This example transmits diagnostic data, not an actuator command. It sends a classic eight-byte CAN1 frame every millisecond. Check bus load, identifiers, wiring and termination before use. No hardware is programmed automatically.</description>
    </item>
    <item>
      <title>Using the Model API</title>
      <link>/models/model-api.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/model-api.html</guid>
      <description>Typical Use&#xD;In a typical project, a Simulink model reads dash channels, computes outputs and sends results back to the dash. You rarely call the CAN functions yourself: Ginmake and the runtime’s CMake helpers generate that code.&#xA;Model IPC&#xD;The CD6 has two processor cores. The dash firmware runs on the CM7 core and owns the display, inputs, logging and external CAN. Your model runs on the CM4 core. Model IPC (inter-processor communication) is the virtual CAN connection between them. It has no external connector. It is not really a CAN bus at all and operates via shared memory - but familiar CAN semantics are used for message framing and signal encoding.</description>
    </item>
    <item>
      <title>Echo and Calibration Example</title>
      <link>/models/examples/echo/readme.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/examples/echo/readme.html</guid>
      <description>CD6 Echo&#xD;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.&#xA;Project Layout&#xD;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 configuration&#xD;Copy 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:</description>
    </item>
    <item>
      <title>CDX CLI Guide</title>
      <link>/models/doc/cli.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/doc/cli.html</guid>
      <description>CDX command-line workflows&#xD;Use bin/cdx.exe to generate, build, package and deploy models. This bundled, self-contained Windows x64 C#/.NET 10 executable needs no PowerShell, .NET SDK or separately installed .NET runtime. Only maintainers need the SDK to build it.&#xA;Keep the executable, libraries, MATLAB helpers and release manifest together.&#xA;This guide is a reference. To build and run a first application, start with the Quickstart.&#xA;Run as cdx&#xD;Add cdx-runtime\bin to PATH to run cdx without its directory or .exe. Do not move cdx-runtime\bin\cdx.exe out of the runtime or add . to PATH.</description>
    </item>
    <item>
      <title>Updating the Runtime</title>
      <link>/models/doc/update-runtime.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/doc/update-runtime.html</guid>
      <description>Updating the Runtime&#xD;Each CDX runtime release replaces the complete cdx-runtime folder in your project. Your application, DBCs, presets and root build files stay in place.&#xA;Identify The Installed Runtime&#xD;The installed release-manifest.json, not an old ZIP or README example, identifies your runtime. From the project root, use the project-local executable:&#xA;1.\cdx-runtime\bin\cdx.exe --version 2.\cdx-runtime\bin\cdx.exe verify-release --runtime cdx-runtime&#xD;--version identifies the executable and supported formats. verify-release reports the installed runtime version and checks its inventory. Do not copy a new executable into an older runtime or disable verification to hide a mismatch.</description>
    </item>
    <item>
      <title>Rebuilding the Runtime</title>
      <link>/models/doc/build-runtime.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/doc/build-runtime.html</guid>
      <description>Build the CDX runtime library from source&#xD;Application builds default to prebuilt CM4 libraries: lib\Release\libcdx_runtime.a or lib\Debug\libcdx_runtime.a. Sources are included for optional rebuilds of libcdx_runtime.a.&#xA;Included sources and prerequisites&#xD;source\model-runtime\src_lib: CM4 startup integration, runtime and CDX API. source\model-runtime\include: public headers for the standalone source build. source\src\model_ipc: shared IPC and calibration implementation. source\src\cd\outputs: DBC packing implementation. source\model-runtime\release: CMake library build definition used for the prebuilt libraries. licenses\nxp and licenses\cmsis: required SDK sources, startup assembly, device/CMSIS headers and original third-party notices. Install Arm GNU GCC 10.3 or newer, CMake 3.21 or newer and Ninja per the Installing Tools. The compiler version in release-manifest.json identifies the bundled-library compiler, not an exact-match application requirement. Use the supplied ARM toolchain file for matching Cortex-M4, Thumb, FPv4-SP-D16 and hard-float ABI settings.</description>
    </item>
    <item>
      <title>Revision History</title>
      <link>/models/revision-history.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/models/revision-history.html</guid>
      <description>CDX Runtime Revision History&#xD;This file lists the changes in each CDX Runtime release, newest first.&#xA;One release version covers the runtime library, public API, cdx command-line tool, MATLAB helpers, CMake helpers and example projects. The ZIP filename, cdx --version and version in release-manifest.json show the installed release. Version numbers not listed here were not released.&#xA;Major relates to the core dash generation (e.g. CD5x / CD6x). Minor More general changes that may cause incompatibilities. Revision General fixes and small improvements. Patch Minor fixes and improvements. Omitted if zero. To upgrade, replace the complete cdx-runtime folder as described in Updating the Runtime.</description>
    </item>
  </channel>
</rss>