<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Simulink® Enabled :: Ginmake Manual</title>
    <link>https://gems.co.uk/simulink/index.html</link>
    <description>Ginmake version 1.74+&#xA;This section details the use of Ginmake for Simulink® Enabled GEMS electronic controllers. It includes information on the build process, command line options, and how to use the Simulink® related features.&#xA;Simulink Build Process&#xD;Command Line&#xD;Input Files&#xD;Generated Files&#xD;Simulink Options File&#xD;User Workspace</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://gems.co.uk/simulink/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Simulink Build Process</title>
      <link>https://gems.co.uk/simulink/simulink-build-process.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/simulink/simulink-build-process.html</guid>
      <description></description>
    </item>
    <item>
      <title>Command Line</title>
      <link>https://gems.co.uk/simulink/command-line.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/simulink/command-line.html</guid>
      <description>ginmake –simulink-options=options-file –simulink-base-gin=some.gin –simulink-output=dir&#xA;The options file can specify both the output directory (dir) and/or the base gin. The command line options will override the options file.</description>
    </item>
    <item>
      <title>Input Files</title>
      <link>https://gems.co.uk/simulink/input-files.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/simulink/input-files.html</guid>
      <description>The base GIN file describes the base-level un-extended functionality, protocols etc for the ECU and is strictly required.&#xA;The generated model source code and the user workspace file should be provided in the model_sources section of the options file. These are necessary for code/data generation.&#xA;Ginmake will generate an externs file in such a way to allow the firmware to convert virtual gemscom addresses to real addresses. The externs file is also processed to add the items to the base gin file and generate a merged gin.</description>
    </item>
    <item>
      <title>Generated Files</title>
      <link>https://gems.co.uk/simulink/generated-files.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/simulink/generated-files.html</guid>
      <description>Simulink export will generate a number of files:&#xA;{prefix}get_set.h {prefix}externs.h {prefix}workspace.m {prefix}in_signals.h {prefix}gin.h {prefix}gin.c {prefix}merged.gin</description>
    </item>
    <item>
      <title>Simulink Options File</title>
      <link>https://gems.co.uk/simulink/simulink-options-file.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/simulink/simulink-options-file.html</guid>
      <description>The Simulink options file controls what files are input and output.&#xA;The file is in a permissive JSON format that supports c-style comments and allows key names to be specified without quotation marks. The entire file must be a JSON object.&#xA;CDX API Use target: &#34;CDX&#34; to select CDX export. Like target: &#34;XCU8&#34;, this defaults to A2L output, does not require a base GIN, and enables direct calibration access. Alternatively, set uses_cdx_api: true to select the CDX API independently of the target’s other defaults. This takes precedence over uses_xcu_api.</description>
    </item>
    <item>
      <title>User Workspace</title>
      <link>https://gems.co.uk/simulink/user-workspace.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/simulink/user-workspace.html</guid>
      <description>The Simulink code generation can be supplied with a user workspace file that identifies objects used by the Simulink model and should be available to the calibration software.&#xA;Enumerations and other ginmake directives can appear in this file. These should be specified in comments that begin with %+.&#xA;e.g.&#xA;1%+ [OPTLIST=Baud,13,38400,26,19200,52,9600,104,4800,208,2400] 2%+ [CATEGORY,fuel,Fuel]&#xD;Items may have ginmake style comments preceding them. These will be added to the generated externs file (possibly with some translations).</description>
    </item>
  </channel>
</rss>