List of Known Issues
Standard ASAM MCD-1 XCP Version 1.5.0
ID Title
3376 Specification of the Command Sequence for Slave Reprogramming
Description
Chapter 13.7 REPROGRAMMING THE SLAVE describes the commands for
ECU programming. The specification is very short and is missing a clear def-
inition of command sequences. Further relevant descriptions are scattered
across prior chapters. This shall be improved. The standard shall include:
• consolidated description of slave reprogramming, either by textual de-
scriptions in the chapter or by explicit references to other chapters
• clear specification of command sequences
• examples
ID Title
3640 Ambiguous Use of the Abbreviation "MSB"
Description
The abbreviation "MSB" is used multiple times in the standard. However, it is
not clearly defined. There are various inconsistent uses of "MSB" in the stand-
ard:
• In chapter 7.5.1 STANDARD COMMANDS, MSB for the parameter
BYTE_ORDER has the meaning of "Most Significant Byte".
• In chapter 7.5.1.13 BUILD CHECKSUM OVER MEMORY RANGE,
however, MSB is used to denote "Most Significant Bit". Same is true
for chapter 7.5.2.5 MODIFY BITS and 7.5.4.8 GET DAQ CLOCK
FROM SLAVE.
• Chapter 13 SYMBOLS AND ABBREVIATED TERMS defines MSB
as: "MSB - Most Significant Bit/Byte". This definition is ambiguous.
The same is true for LSB.
ID Title
3657 Error in PROGRAM command specification
In Table 175 "PROGRAM command structure", for table entry byte 1, the up-
per limit [1..(MAX_CTO_PGM-2)/AG] is specified incorrectly. The correct for-
mula is MAX_CTO_PGM/AG-2.
ID Title
3825 Error in the Initial UPLOAD Command of GET_ID
Description
Chapter 7.5.1.7 GET IDENTIFICATION FROM SLAVE describes:
"If TRANSFER_MODE is 0, the slave device sets the Memory Transfer Ad-
dress (MTA) to the location from which the master device may upload the
requested identification using one or more UPLOAD commands. For the ini-
tial UPLOAD command, the following rule applies:
Number of Data Elements UPLOAD [AG] = (Length GET_ID [BYTE]) / AG"
The above calculating formula does not covered multiple UPLOAD com-
mands. It is proposed to add the following clause to the standard:
"If '(Length GET_ID [BYTE]) / AG' exceeds the maximum number of data
elements UPLOAD [AG], multiple UPLOAD commands shall be sent from
XCP master."
LOKI_ASAM_MCD-1_XCP_1-5-0.pdf.docx 1
List of Known Issues
Standard ASAM MCD-1 XCP Version 1.5.0
ID Title
3826 Error in Non-volatile Memory Programming Commands Error Handling
Description
In Table 233 "Non-volatile memory programming commands error handling",
Timeout t5 error Pre-Action of PROGRAM and PROGRAM_MAX is "SYNCH
+ SET_MTA". This is only valid for "Absolute Access Mode". In case of "Func-
tional Access Mode", the Pre-Action is "SYNCH".
Comments:
In case of "Functional Access Mode", SET_MTA is never used for functional
programming sequence. This can be determined in "4.5.4 FUNCTIONAL AC-
CESS MODE - ACCESS BY FLASH AREA" and the descriptions of PRO-
GRAM_FORMAT (7.5.5.8). Chapter "7.5.5.8 SET DATA FORMAT BEFORE
PROGRAMMING" describes:
"The sequence will be terminated by other commands e.g. SET_MTA."
Therefore, different Pre-Actions should be described in case of functional
access mode and absolute access mode.
ID Title
Description
LOKI_ASAM_MCD-1_XCP_1-5-0.pdf.docx 2
List of Known Issues
Standard ASAM MCD-1 XCP Version 1.5.0
About This Document
This document lists known issues for the standard and version as identified in the document
header. Issues in the context of ASAM standards have one of the following characteristics:
• Error: unintended or wrong content.
• Contradiction: inconsistent or contradictory content.
• Specification gap: missing content required for a functional system and for complete
understanding.
• Lack of clarity: Unclear, vague or ambiguous description, which leads to misunder-
standings and misinterpretations.
The issue may exist in the base standard, in associate standards, schema files, interface
definition files, model files, examples or any other supplements of the standard.
For each issue, the table contains an ID, title and description.
ID: Unique identification number assigned by the ASAM change request system.
Title: Summary of the issue description in headline style.
Description: Identifies the parts of the standard that are affected by the issue, provides a
reason why this is considered as an issue and allows the reader to understand
the technical implications of the issue. Optionally, the description includes a
resolution proposal and a proposed workaround for the issue.
Issues are resolved in the release of a new version of a standard. Please regularly check
ASAM's web page and news publications to stay informed about new versions. If an issue
has been resolved in a new version, then it is not listed in the List of Known Issues document
for this version any longer.
The List of Known Issues document for former versions of the same standard will be frozen
and will not be further maintained. ASAM advises all users of its standards to always use
the latest version of its standards.
LOKI_ASAM_MCD-1_XCP_1-5-0.pdf.docx 3
