Страница 1 мировой engineering стандарты общая спецификация

RequestOutOfRange 
Note 1
•
Any memory address within the interval [$MA, ($MA + $MS -$1)] is invalid.
•
Any memory address within the interval [$MA, ($MA + $MS -$1)] is
restricted.
•
Any memory address within the interval [$MA, ($MA + $MS -$1)] is secure
and the ECU is locked.
•
The memorySize parameter in the request message is greater than the
maximum value supported by the ECU.
M
ROOR
78
RequestCorrectlyReceived-ResponsePending
See 7.2 Return Code Definition.
C
RCR-RP
Note 1: 
A restricted memory address is one that the ECU will not allow a tester to read under any circumstances (e.g., the addresses that
contain the security seed and key values. Secure memory addresses are those which the ECU shall not allow the tester to read unless the
ECU is unlocked (see service $27 SecurityAccess).
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
Page 121
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
8.7.5 Message Flow Example ReadMemoryByAddress.
8.7.5.1 ReadMemoryByAddress Example with 4 Byte memoryAddress. 
In this example (Table 96):
The ECU uses 4 byte addressing and the tester requests memory data in addresses $00011102 to $00011103
(two bytes memory data so memorySize is $00 $02).
The tester responds with the memory data $34 and $56.
The node has a physical request CANId of $241.
The node has a physical USDT response CANId of $641.
Table 96: ReadMemoryByAddress(memoryAddress, memorySize < 4 bytes)
T = Frame Sent By Tester, N = Frame Sent By Node; shaded region indicates PCI
Frame Type CAN Id
#1
#2
#3
#4
#5
#6
#7
#8
T(USDT-SF)
$241
$07
$23
$00
$01
$11
$02
$00
$02
N(USDT-SF)
$641
$07
$63
$00
$01
$11
$02
$34
$56