General Specification Electrical Function gmw3110 General Motors Local Area Network Enhanced Diagnostic Test Mode Specification

9.3.2.1.1 Requirements for SPS ECUs Where Operational Software Is Not Programmable. 
SPS_TYPE_C 
ECUs executing operational software (only valid if operational software is not programmable via SPS) shall be 
able to receive diagnostic messages using the AllNodes request CANId with AllNodes extended address. SPS 
Programmable ECUs with preprogrammed permanent diagnostic CAN Identifiers (SPS_TYPE_A or 
SPS_TYPE_B) shall also be able to receive messages addressed with its PTP request CANId. SPS_TYPE_C 
ECUs (which do not have preprogrammed permanent diagnostic CAN Identifiers) shall respond to requests 
sent with the SPS_PrimeReq ($0xx) CANId once diagnostic responses have been enabled. 
An ECU shall be capable of using the same diagnostic CAN Identifiers for the duration of a programming 
event. This means that an ECU which stores the permanent diagnostic CAN Identifiers in calibration and is 
fully programmed at the beginning of a programming event (SPS_TYPE_A ECU) shall use the permanent 
diagnostic CAN Identifiers even after the calibrations have been erased. The operational software is not 
required to retain the permanent diagnostic CAN Identifiers if the programming event is interrupted prior to its 
completion and the ECU has performed a software reset. 
An ECU that is only capable of calibration programming (e.g., the operational software is part of ROM and 
calibrations stored in EEPROM) shall have in the operational software the equivalent functionality specified for 
the boot software in the subsequent sections of this chapter. 
9.3.2.2 Calibrations. 
Calibrations shall be capable of being programmed separately from the operational 
software. This allows for assembly plant programming of only calibrations. Deviations from this requirement 
must be agreed upon by appropriate release responsible engineer, service operations and manufacturing 
representatives and shall be documented in the CTS. 
Each calibration module shall have its own unique identifier retrievable via the ReadDataByIdentifier ($1A) 
service. 
The ECU shall support either one or both of the following methods of programming calibrations. 

Programming an individual calibration module. 

Programming multiple (or all) of the calibration modules during a single programming event.