{
  "node": {
    "id": "term:hex-file",
    "type": "Term",
    "label": "HEX and S-record files",
    "properties": {
      "id": "hex-file",
      "name": "HEX and S-record files",
      "abbr": ".hex, .s19",
      "aka": [
        "Intel HEX",
        "Motorola S-record",
        "SREC"
      ],
      "section": "topic-data",
      "definition": "Text formats that carry a firmware or calibration image with its memory addresses and checksums, used to flash controllers: Intel HEX and Motorola S-record (.s19, .srec, .mot). Their content must match the A2L that describes it.",
      "related": [
        "flashing",
        "firmware",
        "a2l"
      ],
      "url": "https://lemonergy.com/learn/glossary/hex-file/",
      "mentions": []
    }
  },
  "edges": [
    {
      "id": "edge:4196",
      "source": "term:hex-file",
      "target": "topic:topic-data",
      "type": "belongsTo",
      "properties": {
        "sourceFile": "terms.json"
      }
    },
    {
      "id": "edge:4197",
      "source": "term:hex-file",
      "target": "term:flashing",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4198",
      "source": "term:hex-file",
      "target": "term:firmware",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4199",
      "source": "term:hex-file",
      "target": "term:a2l",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    }
  ],
  "neighbors": [
    {
      "id": "topic:topic-data",
      "type": "Topic",
      "label": "Data, communication and electronics",
      "properties": {
        "id": "topic-data",
        "name": "Data, communication and electronics",
        "lede": "The control units, chips, protocols and file formats through which a battery is measured, controlled and logged.",
        "context": "Separate quantities from encoding and transport.",
        "example": "2500 in a log might mean 25.00 °C, 2.5 V or raw counts. Units and scale must accompany the value.",
        "lesson_url": "https://lemonergy.com/learn/fundamentals/battery-basics/",
        "lesson_label": "Open battery basics"
      }
    },
    {
      "id": "term:flashing",
      "type": "Term",
      "label": "Flashing",
      "properties": {
        "id": "flashing",
        "name": "Flashing",
        "aka": [
          "reprogramming",
          "ECU flashing",
          "bootloader"
        ],
        "section": "topic-data",
        "definition": "Writing new firmware into a controller’s flash memory, normally through a bootloader that receives the image over CAN with UDS services. Image files come as Intel HEX, Motorola S-record or binary, often signed so the controller refuses unauthorised code.",
        "related": [
          "firmware",
          "uds",
          "hex-file",
          "can-bus"
        ],
        "url": "https://lemonergy.com/learn/glossary/flashing/",
        "mentions": []
      }
    },
    {
      "id": "term:firmware",
      "type": "Term",
      "label": "Firmware",
      "properties": {
        "id": "firmware",
        "name": "Firmware",
        "aka": [
          "embedded software",
          "BMS software"
        ],
        "section": "topic-data",
        "definition": "The software that runs on a BMS or charger controller. Its version decides how SOC, limits and faults behave, so it is tracked like a part number, updated by flashing over CAN or over the air, and recorded in the battery passport.",
        "related": [
          "mcu",
          "flashing",
          "bmu",
          "battery-passport",
          "functional-safety"
        ],
        "url": "https://lemonergy.com/learn/glossary/firmware/",
        "mentions": [
          "charger",
          "state-of-charge",
          "bms",
          "over-the-air-update"
        ]
      }
    },
    {
      "id": "term:a2l",
      "type": "Term",
      "label": "A2L file",
      "properties": {
        "id": "a2l",
        "name": "A2L file",
        "abbr": ".a2l",
        "aka": [
          "ASAM MCD-2 MC"
        ],
        "section": "topic-data",
        "definition": "The ASAM description of a controller’s internal measurement and calibration variables — names, memory addresses, data types and conversions — that tools need to read or tune them over XCP. It is generated with each firmware build and must match it exactly.",
        "related": [
          "xcp",
          "hex-file",
          "mdf4",
          "firmware"
        ],
        "url": "https://lemonergy.com/learn/glossary/a2l/",
        "mentions": []
      }
    }
  ]
}