dynabook Portege X30L-K Series, Руководство по обслуживанию

Страница: 60 / 136

Maintenance Manual (960-948) 3-8
Tests and Diagnostics
Enter C ……Restarts the test execution
Enter E …….Ends the test. The program returns to the screen to select
Error Stop and Test Loop item selection.
Select No: though any error occurs during the test, the test is continued.
The setting of Yes/No can be changed by pressing
ENTER .
■
Go to Test
The subtest is started in the conditions selected above by entering ENTER .
For more information about the tests in the Main Test Menu and other tests,
refer to Section 3.6 or later.
3.6 Memory Test
To execute the Memory Test, select 1 from the DIAGNOSTIC TEST Menu
(Main Test Menu), press Enter and follow the directions on the screen.
(Move the highlight bar to the subtest you want to execute and press
Enter .)
Subtest 1 [Main memory Test]
This test writes/reads the test data to/from the main memory,
and compares them.
The test procedure is as follows:
(1) This test gets the memory map table.
(2) It seeks empty area more than 1MB.
(3) To the whole empty area, it writes the test data and reads
out them to compare the test data and read data.
(4) Up to the maximum address of the mounted memory, it
repeats to seek the empty area, to write the test data, to
read out the data and to compare the test data and read
data.
(5) It repeats the process from (1) to (4) above with the 4
test data.
The test patterns are 4-byte data: 00000000h, 55555555h,
AAAAAAAAh and FFFFFFFFh. If empty area less than 3-
byte length is found, the test data is not written.
If the empty memory is 64MB or less, this test is not
executed. In the case that this test is never executed
because of the memory size shortage, this test displays the
message “Data Not Found “and writes the information to the
text file
(errorlog.txt) as an error log.
If the test data and read data is not the same at comparing,
this test displays the message “Data Compare error “and
writes the information to the text file (errorlog.txt) as an error
log.
As for the details of the error log, refer to 3.12 Log utility.