Grundig GDV 100 D Servicehandbuch Seite 74

Service Test Programme
– "NVRAM checksum could not be updated."
Error code: DD_ERR_ANYNVRAMLOC_WRITECHECKSUM_FAIL
This Service Test Level can be used to read and modify any location
of the NVRAM. To do this the user is prompted for an address and a
value which must be written.
The Service Test Level prompts the user for input in two stages. During
these two input stages, the user can always terminate the Service Test
Level by entering a return. If the Service Test Level is terminated in this
way the contents of the NVRAM will not be modified. The following will
describe the steps that must be taken to modify the contents of the
NVRAM.
When the Service Test Level is activated the following prompt appears
on the command handler:
NVRAM address >
Here a hexadecimal address in the range of 000 - FFF can be entered.
Note that an address always consists of 3 characters. When an invalid
address is entered, a message "NVRAM address must be 3 charac-
ters." is displayed and the Service Test Level terminates. If a correct
address is entered followed by a return, the following prompt appears:
NVRAM data (0xXX) >
The XX in 0xXX is replaced by a hexadecimal value. This value is the
value that is currently stored on the address that was selected with the
previous prompt. Now the user can enter a 2-digit hexadecimal value.
If an invalid value is entered, a message "NVRAM data must be 2
characters" is displayed and the Service Test Level terminates without
modifying the contents of the NVRAM. If a correct value is entered
followed by a return, the value will be stored on the given address in
NVRAM. The Service Test Level checks if the address to be modified
is within the configuration area, i.e. within the range of 000 - 00d. If the
address is within this area, a new checksum for the area is calculated
and stored. In this way a modified configuration area will still be valid.
Note that if the checksum was not valid before this Service Test Level
was executed it will be made valid if an address within the configuration
area is modified. If an address not contained in the configuration area
is modified, the checksum of the configuration area will be left un-
changed.
Example 1:
Read the contents of address 0x00A of the NVRAM. It is assumed for
this example that the contents of address 0x00A are 0x12.
↵
NVRAM address > 00A
↵
NVRAM data (0x12) >
Example 2:
Modify the contents of address 0x00A of the NVRAM. This address is
within the configuration area. It is assumed in this example that the
contents of address 0x00A are 0x12 and must be modified to 0xFF.
↵
NVRAM address > 00A
↵
NVRAM data (0x12) > FF
NVRAM contents and configuration checksum updated.
75 (PapChksEpr05)
Calculate and verify checksum of the EPROM05.
This Service Test Level will check if the checksum of the EPROM05 is
correct. This Service Test Level does not check if the EPROM05 is of
the right version and in the right place.
Message:
– "Calculated checksum is 0xX and is correct"
Error code: DD_ERR_OK
– "Calculated checksum of EPROM05 is 0xX and is not correct (must
be 0xY)"
Error code: DD_ERR_CHECKSUM_EPR05_FAILED
The X will be replaced with the calculated checksum and Y will be
replaced with checksum value stored in EPROM05. Both values will be
shown as a hexadecimal value of eight digits (32 bit unsigned long) with
a fixed length (leading zero's).
This Service Test Level will check the checksum of the EPROM05
which is located in the address range of 0 to 512KB. This Service Test
Level will return a TRUE and the calculated checksum, if the access is
good and the contents is correct. If the contents are not correct this
Service Test Level will return a FALSE, the calculated checksum and
the expected checksum.
3 - 32
BASIC ENGINE ERRORS [BE]
No. Error Meaning
01 illegal-command Command not allowed in this state or unknown
02 illegal_parameter parameter not valid for command
03 sledge_error sledge could not be moved to home position
04 focus_error focus failure
05 motor_error motor not on speed within time-out
06 radial_error servo didn't get on track after several retries
07 pll_lock_error PLL could not lock in Accessing or Tracking
state
08 subcode_header_ subcode or sector information could not be
time_out read
09 subcode_not_ requested subcode item could not be found
found
10 tray_error tray could not be closed or opened completely
11 toc_read_error TOC read could not be read in time
12 jump_error Set when a seek couldn't be performed
13 non_existing_ datapath tries to access a non existing lead
session in area
14 non_existing _bca datapath tries to access a non existing bca area
0xF0 over-run error too many bytes received over S2B
0xF1 communication too less bytes are received over S2B time out
0xF2 parity error byte received with a parity error
0xF3 illegal bus phase CMD_IDC is not valid: out of sync
0xF4 illegal number more bytes are transmitted than possible
of bytes
ERROR LOG AND BITS DESCRIPTION
bit log description
1-8 – –
2
16 000C0001 No I C communication with DENC
24 00110000 No indentification
2
32 000D0001 No I C communication with DSP
33-40 – –
48 00130004 No identification
47 00130003 Internal bus (DSM-DVP)
56 00100002 No acces to NVRAM
64 00070001 No acknowledge from I
2
63 00070002 I C bus busy
72 00090001 S2B interface error
71 00090002 S2B interface communication error
80 00150000 No communication with Display processor
GDV 100 D
component
IC7303
IC7406
IC7201
IC7407
BE
IC7201
IC7201
IC7108
2 C controller IC7101
IC7101
IC7111
IC7111
IC7111
GRUNDIG Service