<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SEGMENT_ADDRESS :: Ginmake Manual</title>
    <link>https://gems.co.uk/data-definitions/segment-address.html</link>
    <description>Supported by Ginmake 2.19+&#xA;[SEGMENT_ADDRESS,&lt;segment_name&gt;,&lt;gemscom_address&gt;,&lt;size&gt;[,&lt;physical_address&gt;[,gcc_section]]] Defines address / size of a segment previously defined by a SEGMENT definition. This removes the need for PAGETBL / PAGETBLv2 – memory segments can be defined purely with SEGMENT and SEGMENT_ADDRESS since ginmake 2.19. This is preferable for code that does not use a page table for gemscom address translation.&#xA;Parameter Description&#xA;&lt;segment_name&gt; Name of the segment to match that in its SEGMENT definition &lt;gemscom_address&gt; Address of the segment used over the gemscom protocol. This is a virtual address and is remapped by the ECU to a physical address. Size of the segment, in bytes. At time of writing, GWv4 will read/write entire calibration (NVM) segments. &lt;physical_address&gt; Optional physical address of the segment from the perspective of the target computer (the ECU). This may be useful for diagnostic purposes in future. &lt;gcc_section&gt; Section name used by linker for this segment that will appear in the GNU linker map file. Example</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://gems.co.uk/data-definitions/segment-address/index.xml" rel="self" type="application/rss+xml" />
  </channel>
</rss>