2. Safety Information, General Notes & Lead Free Requirements
2.1 Safety
Instructions
2.1.1 General Safety
Safety regulations require that during a repair:
• Connect the unit to the mains via an isolation transformer.
• Replace safety components, indicated by the symbol
,
only by components identical to the original ones. Any
other component substitution (other than original type)
may increase risk of fi re or electrical shock hazard.
Safety regulations require that after a repair, you must return
the unit in its original condition. Pay, in particular, attention to
the following points:
• Route the wires/cables correctly, and fi x them with themounted cable clamps.
• Check the insulation of the mains lead for external
damage.
• Check the electrical DC resistance between the mains
plug and the secondary side:
1. Unplug the mains cord, and connect a wire between
the two pins of the mains plug.
2. Set the mains switch to the ‘on’ position (keep the
mains cord unplugged!).
3. Measure the resistance value between the mains
plug and the front panel, controls, and chassis
bottom.
4. Repair or correct unit when the resistance
measurement is less than 1 MΩ.
5. Verify this, before you return the unit to the customer/
user (ref. UL-standard no. 1492).
6. Switch the unit ‘off’, and remove the wire between the
two pins of the mains plug.
2.1.2 Laser Safety
This unit employs a laser. Only qualifi ed service personnel may remove the cover, or attempt to service this device (due
to possible eye injury).
2.2 Warnings
2.2.1 General
• All ICs and many other semiconductors are susceptible to
electrostatic discharges (ESD, ). Careless handling
during repair can reduce life drastically. Make sure that,
during repair, you are at the same potential as the mass
of the set by a wristband with resistance. Keep
components and tools at this same potential.
Available ESD protection equipment:
– Complete kit ESD3 (small tablemat, wristband,
connection box, extension cable and earth cable)
4822 310 10671.
– Wristband tester 4822 344 13999.
• Be careful during measurements in the live voltage
section. The primary side of the power supply, including
the heatsink, carries live mains voltage when you
connect the player to the mains (even when the
player is ‘off’!). It is possible to touch copper tracks and/
or components in this unshielded primary area, when
you service the player. Service personnel must take
precautions to prevent touching this area or components
in this area. A ‘lightning stroke’ and a stripe-marked
printing on the printed wiring board, indicate the primary
side of the power supply.
• Never replace modules, or components, while the unit is
‘on’.
2.2.2 Laser
• The use of optical instruments with this product, will
increase eye hazard.
• Only qualifi ed service personnel may remove the cover or attempt to service this device, due to possible eye injury.
• Repair handling should take place as much as possible
with a disc loaded inside the player.
• Text below is placed inside the unit, on the laser cover
shield:
Note: Use of controls or adjustments or performance of
procedure other than those specifi ed herein, may result in hazardous radiation exposure. Avoid direct exposure to beam.
CAUTION VISIBLE AND INVISIBLE LASER RADIATION WHEN OPEN AVOID EXPOSURE TO BEAM
ADVARSEL SYNLIG OG USYNLIG LASERSTRÅLING VED ÅBNING UNDGÅ UDSÆTTELSE FOR STRÅLING
ADVARSEL SYNLIG OG USYNLIG LASERSTRÅLING NÅR DEKSEL ÅPNES UNNGÅ EKSPONERING FOR STRÅLEN
VARNING SYNLIG OCH OSYNLIG LASERSTRÅLNING NÄR DENNA DEL ÄR ÖPPNAD BETRAKTA EJ STRÅLEN
VARO! AVATTAESSA OLET ALTTIINA NÄKYVÄLLE JA NÄKYMÄTTÖMÄLLE LASER SÄTEILYLLE. ÄLÄ KATSO SÄTEESEEN
VORSICHT SICHTBARE UND UNSICHTBARE LASERSTRAHLUNG WENN ABDECKUNG GEÖFFNET NICHT DEM STRAHL AUSSETSEN
DANGER VISIBLE AND INVISIBLE LASER RADIATION WHEN OPEN AVOID DIRECT EXPOSURE TO BEAM
ATTENTION RAYONNEMENT LASER VISIBLE ET INVISIBLE EN CAS D’OUVERTURE EXPOSITION DANGEREUSE AU FAISCEAU
Figure 2-2
Page 2
Safety Information, General Notes & Lead Free Requirements
2.3 Lead Free Requirement
Information about Lead-free produced sets
Philips CE is starting production of lead-free sets from
1.1.2005 onwards.
INDENTIFICATION:
Regardless of special logo (not always indicated)
One must treat all sets from 1 Jan 2005 onwards, according
next rules.
Example S/N:
Bottom line of typeplate gives a 14-digit S/N. Digit 5&6 is the year, digit 7&8 is
the week number, so in this case 1991 wk 18
So from 0501 onwards = from 1 Jan 2005 onwards
• Special information for BGA-ICs:
- always use the 12nc-recognizable soldering temperature
profi le of the specifi c BGA (for de-soldering always use the
lead-free temperature profi le, in case of doubt)
- lead free BGA-ICs will be delivered in so-called ‘drypackaging’ (sealed pack including a silica gel pack) to
protect the IC against moisture. After opening, dependent
of MSL-level seen on indicator-label in the bag, the
BGA-IC possibly still has to be baked dry. (MSL=Moisture
Sensitivity Level). This will be communicated via AYSwebsite.
Do not re-use BGAs at all.
• For sets produced before 1.1.2005 (except products of
2004), containing leaded solder-alloy and components,
all needed spare-parts will be available till the end of the
service-period. For repair of such sets nothing changes.
• On our website www.atyourservice.ce.Philips.com you fi nd more information to:
BGA-de-/soldering (+ baking instructions)
Heating-profi les of BGAs and other ICs used in Philips-sets
You will fi nd this and more technical information within the
“magazine”, chapter “workshop news”.
For additional questions please contact your local repair-helpdesk.
Important note: In fact also products of year 2004 must be treated in this way as long as you
avoid mixing solder-alloys (leaded/ lead-free). So best to always use SAC305 and the higher
temperatures belong to this.
Due to lead-free technology some rules have to be respected by the
workshop during a repair:
• Use only lead-free solder alloy Philips SAC305 with order
code 0622 149 00106. If lead-free solder-pate is required,
please contact the manufacturer of your solder-equipment.
In general use of solder-paste within workshops should be
avoided because paste is not easy to store and to handle.
• Use only adequate solder tools applicable for lead-free
solder alloy. The solder tool must be able
o To reach at least a solder-temperature of 400°C,
o To stabilize the adjusted temperature at the solder-tip
o To exchange solder-tips for different applications.
• Adjust your solder tool so that a temperature around 360°C
– 380°C is reached and stabilized at the solder joint.
Heating-time of the solder-joint should not exceed ~ 4 sec.
Avoid temperatures above 400°C otherwise wear-out of
tips will rise drastically and fl ux-fl uid will be destroyed. To
avoid wear-out of tips switch off un-used equipment, or
reduce heat.
• Mix of lead-free solder alloy / parts with leaded solder alloy
/ parts is possible but PHILIPS recommends strongly to
avoid mixed solder alloy types (leaded and lead-free).
If one cannot avoid or does not know whether product is
lead-free, clean carefully the solder-joint from old solder
alloy and re-solder with new solder alloy (SAC305).
• Use only original spare-parts listed in the Service-Manuals.
Not listed standard-material (commodities) has to be
purchased at external companies.
Page 3
1. Alignments & Test Procedures
1.1. Reprogramming Procedure of NVM on the Digital Board
The NVM, item 7809 on the Digital board contains the following:
• Slash information (or slash version)
• IEEE Unique number
The slash version and IEEE Unique number are stored at the end of the production line of the set.
In case of failure the Digital board is replaced by a new board (the NVM is an empty device). After replacement
of the NVM the set can only startup in Diagnostic software mode because the Slash version is not in placed.
By way of commands via the Diagnostic Software (DS) and hyperterminal connection to the PC, these factory
settings must be restored into the NVM.
1.1.1. Slash Version
The slash version is stored with DS command 1217 followed by the slash version as parameter.
The slash versions used in DVDR7310H are as follows:
• DVDR7310H/05 11208
• DVDR7310H/31 11207
• DVDR7310H/51 11222
• DVDR7310H/58 11207
Example:
DS:> 1217 11221
With DS command 1218 the slash version can be displayed
1.1.2. IEEE Unique Number
1. Note the serial number of the set example:
VN050136130156
- VN = production center (VN….Szekesfehervar).
According to UAW-500: V=22 and N=14
- 05 = change code (this is not used for this calculation)
- 01 = YEAR
- 36 = Production WEEK
- 130156 = Lot and SERIAL number
2. Calculate the unique number: this number always exists out of 10 hexadecimal numbers
3. First 5 numbers: First we calculate a decimal number according to formula below:
- 35828*YEAR + 676*WEEK + 26*A + H + 8788
- The figures are fixed, YEAR + WEEK + production center code (A + H) are variables
- Then we translate this decimal number to a hexadecimal number.
- Example: 68986 = 10D7A (hex)
4. Last 5 numbers: The last 5 numbers exist out of the Lot and SERIAL number.
We have to translate the decimal number to the next 5 hexadecimal numbers:
Example: 130156 (decimal) = 1FC6C (hex)
5. This IEEE Unique number (10-digit hexadecimal number) is stored with DS command 1207.
Example:
DS:>1207 10D7A1FC6C
120700: Test OK@
The set has now its original IEEE unique number.
With DS command 1208 the slash version can be displayed
1.2. Reprogramming Procedure of NVM on the Digital Board
The Boot Eeprom, item 7810 on the Digital board contains the “Diversity String” that tells the software during
DVDR7310H_Alignment.doc
Page 4
startup which hardware version is present. This setting is stored during the production of the Digital board.
In case of failure and the Digital board has been replaced it is adviseable to ensure that the Eeprom containing
the correct boot script.
With DS command 1228 the settings can be displayed.
Note: An error in the Diversity string will render the s e t not able to boot-up and the Digital board
Via the Dignostic Software the “Diversity String” is stored with the command 1226, followed by the “Diversity
String” as parameter.
The Diversity strings used in BHDR2/02 is as follows:
444248499BFB40014630355F330000005504030000010102000101004008080044564452323030312E303031
0102020808000000010002010000000000000000
Example:
DS:> 1226
444248499BFB40014630355F330000005504030000010102000101004008080044564452323030312E303031
0102020808000000010002010000000000000000
Test OK @
becomes defective
1.3. Laser Control Adjustment
No Laser control adjustment is necessary because the Basic Engine (Drive) delivered by the factory is already
pre-aligned to optimum matching between the Frontend (Servo) Board & the OPU unit in the Basic Engine.
1.3.1. Adjustment procedure
This adjustment is done with the DSW software nucleus 931. The adjustments takes about 30 seconds and the
data is stored in the OPU Eeprom.
Example:
DS:> 931
93100
Test OK @
1.4. Procedure for Formatting a new HDD drive
In case of failure the HDD is replaced by a new unformatted HDD.
To prepare the new HDD for use it must be formatted with a Master DVD via the Diagnostic software nucleus
2107.
Example:
DS:> 2107
Please insert the Master DVD <OK>
This information is furnished for guidance, and with no guarantee as to its accuracy or completeness; its publication conveys no
license under any patent or other right, nor does the publisher assume liability, for any consequence of its use; specifications and
availability of goods mentioned in it are subject to change without notice; it is not to be reproduced, in whole or in part, without
the written consent of the publisher.
Project Documentation.dot, version 1.0
Page 1 of 176
Page 55
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
DOCUMENT CHANGE HISTORY
Date Person Version Reason
2002-08-27 T.J. Scheffel 1.0 Approved version for DS step 3
(P1_4) ( Release 0.2.1.)
2002-09-16 T.J. Scheffel 1.1 Approved version for DS step 4
(P1_4) (Release 0.5)
2002-11-22 T.J. Scheffel 1.2 Approved version for DS step 4
(P1_5) (Release 0.5.2)
2002-12-12 T.J. Scheffel 1.3 Approved version for DS step 5
(P1_5) (Pre-release 0.9) (DS version
6)
2003-01-14 T.J. Scheffel 1.4 Approved version for DS step 5
(P1_5) (Release 0.9 Full
Functionality) (DS version 7)
2003-04-04 T.J. Scheffel 2.0 Approved version for Release 1.0
Full Functionality (DS version 8 )
2003-05-28 M. Quik 2.1 Added chapters User Interface and
Digital Board Diversity. I-Step
update.
2003-10-15 M. Quik 2.2 Modified some small descriptions.
Added DS_HDD nuclei.
2003-12-04 T.J. Scheffel 2.3 Merged all existing variants into 1
document.
2004-01-22 T.J. Scheffel 2.4 Approved version for all variants.
2004-03-30 T.J. Scheffel 2.5
2004-03-30 M. Quik 2.6 Added DS_DTTM nuclei,
DS_SYS_UartSetup, and
DS_AMIX_Mute.
2004-05-24 J. Lekkerkerker 2.7 DS_DTTM updated.
Added DS_HDMI nuclei.
M. van der Ham Added HDD nuclei
2004-07-06 M. Quik 2.8 Modified some small things.
2004-09-17 M. Quik 3.0 Approved version.
2005-01-18 M. Quik 3.1 Updated for VCRCOMBI.
2005-03-10 M. Quik 3.2 Updated for SXC(+/-) and small
changes.
2005-04-06 M. Quik 3.3 Added and changed HDMI nuclei,
BE nuclei, and some small things.
2005-09-02 M. van der Ham 3.4 sgp29atl#47: correct error codes
DS_HDD
2005-10-13 Yeo K.B 3.5 Added new pins for
DS_ASP_Extended and included
warning for ATAPI based drives for
BE nuclei.
2006-05-26 Teo T. T. 3.6 Added DS_AVL tests.
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
DV : Digital Video
DVIO : Digital Video Input Output
EPGB : Electronic Program Guide Board
FRE : Front End (Tuner)
HDD : Hard Disk Drive
HDMI : High Definition Multimedia Interface
IC : Integrated Circuit
IDE : Integrated Drive Electronics
IH : Interface Handler
IIC : Inter IC Communication
INT : Interrupt
LED : Light Emitting Diode
NVRAM : Non Volatile Random Access Memory
OPC : Optimal Power Control
PIO : Peripheral IO pin
PSCAN : Progressive Scan
RC : Remote Control
S2B : Serial to Basic Engine
SYS : System
TOC : Table Of Contents
UART : Universal Asynchronous Receiver Transmitter
UDF : Universal Disc Format
VIP : Video Input Processor
VMIX : Video Matrix (Video switching)
1.3 PURPOSE, SCOPE AND SHORT DESCRIPTION
This document is the user manual for the Diagnostic Software (DS).
Its goal is to facilitate the usage of the DS software.
The users of this document are typically the factory and service teams.
The Diagnostic Software consists of independent ‘atomic’ tests, called nuclei.
Each nucleus forms a test to indicate possible hardware failure.
Its purpose is to facilitate fault-finding in DVD+RW sets.
This document describes all tests that are currently available in the diagnostic software.
Different DVD+RW recorder sets containing different hardware become available all the time,
resulting in hardware diversity covered by chapter 4 :‘Digital Board Diversity’.
Apart from this there will be some different software-builds that define some hardware-specific
issues at compile-time.
As a result of this there will be parts in this document that will NOT be executable on your
specific DVD+RW recorder.
So if you execute a nucleus from one of these groups not currently in your software-build the
command-line will e.g. look like:
DS:> 1800
DS:>
This user manual is intended for an audience that is aware of the diversity in hardware and is
aware which hardware is encompassed in their DVD+RW recorder sets.
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Please note that the examples given in this user manual can differ from your actual hardware.
The error codes returned by the diagnostic software will ALWAYS be as indicated in the
nucleus-description. Should there be any discrepancy then please contact our team so we can
correct the issue.
1.4 NOTES
The OPC change is industrial/production change because it was reported to have high OPC
value (about 2 to 3%) in the production line. This change will help to improve the production fall
out due to high OPC value. So the drives that have went thru the production will have good
OPC value. As for the drives that are already in the market, they will not be affected. The
service centre must perform the drive calibration (nucleus 931; DS_BE_AdjustLaserControl) for
AV3.5 drive, which has firmware version 35 below. We do not think that the download SW
needs to change anything. Please issue the drive calibration in the service nucleus (931) after
the drive is upgrade with the newer firmware.
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
2 USER INTERFACE
The table below shows an overview of the user interfaces of the DS. The table is based on
logical interface, interfaces as seen from user perspective. A logical interface can use one or
more physical interface components.
The DVD Recorder has only a single RS232 port (service port) available for diagnostic or
debugging purposes, implying that all interfaces using this port are mutually exclusive.
Logical
Interface
Command line
interface
Scripts
interface
In the next chapters the logical user interfaces are described in more detail including the exact
use of the physical interface components. To switch between interfaces, the DVD Recorder
needs to be switched off and on again.
Description Physical interface components
Used to send commands from the
Control PC or Service PC to the
DVD Recorder DS.
• Control PC or service PC,
running a program (e.g. Asterix,
Compair, HyperTerminal),
connected to service port of the
DVD Recorder
• Test pin
Used to execute End-user/Dealer
Test Script.
• Local-Keyboard
• Local-Display
2.1 NUCLEI NUMERATION
Each nucleus has a unique number of four digits. This number is the input of the command line
interface.
Figure 1 Unique number of a diagnostic nucleus.
The following groups are defined:
Group number Group name
0 Scripts
1 Codec (e.g. Chrysalis, Leco)
2 Boot EEPROM
3 NVRAM
4 SDRAM
5 FLASH
6 Video Input Processor
7 DVIO
8 Progressive Scan
9 Basic Engine
10 Display and Control Board
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
11 Analogue Board
12 System
13 Electronic Program Guide Board
14 PCMCIA
15 HDMI
16 Analogue Slave Processor
17 Analogue Board EEPROM
18 Video Matrix
19 Audio Matrix
20 Front End
21 Hard Disk
22 Digital Terrestrial Tuner Module
23 USB
2.2 ERROR HANDLING
Results returned from a diagnostic nucleus to the control/service PC are terminated by a 'CR'
character (included in the string length).
The result has the following layout
<number> <string> [Test OK | Error] @<CR>
The use of the “@” enables the Asterix system on the control PC to parse the output string of
each nucleus into a database. This system is used in the factory and automates the test
sequences needed to test each product using the Diagnostic and Service Software.
<number> is a 6-digit decimal number padded with leading zeros if its value is less than 6
digits. The first four digits identify the generating nucleus (group and nucleus); the latter two
digits indicate the error number.
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
2.3 COMMAND LINE INTERFACE
Via the command line interface the execution of diagnostic nuclei can be controlled.
2.3.1 Set-up of physical interface components
Hardware required:
• Control PC
• One free COM port on the Control PC
• Special cable to connect the DVD Recorder to the Control PC
The control PC must use the following port settings for the used COM port:
- 19200 bps,
- 8 data bits,
- no parity,
- 1 stop bit and
- no flow control.
The control PC is connected with a special cable (see chapter 4A.2) to the RS232 port of the
DVD Recorder. Via the same connection the ‘test pin’ will be connected to ground. Using this
pin the software can determine whether Diagnostic mode needs to be entered.
2.3.2 Activation
After power on the next text will be sent to the control PC
Factory Diagnostics and Service Software
DVD Video Recorder (Dec 13 2003, 10:55:37)
The first lines indicate that the DS has been activated and contains the version and build info of
the DS. The next line is the command line prompt (“DS:>”). The DS is now ready to receive
commands. Please note that this text will be different on your specific variant of the DVD+RW
recorder product range.
2.3.3 Usage
The commands that can be given are the numbers of the nuclei. A command must be
terminated with an <ENTER> character from the control PC. When typing commands, the
backspace key can be used to make corrections. Apart from this one can use the Up and Down
arrows to browse to previous commands.
When one enters non-supported commands, the interface returns the command line prompt.
If the command (the nucleus number) is recognised, the nucleus is executed. Result and output
of an activated (and terminated) nucleus will be sent back to the control PC.
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
120000: Hardware ID = 0x27
Test OK @
Example in case the result is an error (DVD+RW 2.1 example):
DS:> 1100
110002: Communication with Analogue Board fails
Error @
DS:>
2.3.4 Termination
To turn off the command line interface switch off the DVD Recorder.
2.4 END-USER/DEALER SCRIPT INTERFACE
This interface is used during execution of the script to display output and error messages.
The local display will be used to display the output and the error messages.
2.4.1 Set-up physical interface components
Hardware required:
• DVD Recorder
The DVD Recorder is tested stand-alone: no other equipment than the DVD Recorder is
needed.
2.4.2 Activation
Pressing the play-key on the keyboard of the DVD Recorder during power-on activates the
dealer script.
2.4.3 Usage
The test requires no user interaction. A number of nuclei will be run before a message is
returned indicating if there is a failure in the DVD Recorder (‘’PASS” will be indicated when the
product functions OK and “FAIL” when there has been an error during one of the tests).
During the execution of this script, a progress indicator is displayed on the display of the DVD
Recorder.
Note
that from the command line interface this script can be started as well, by entering ‘script’
on it.
2.4.4 Termination
To turn off the dealer test, the DVD Recorder must be powered down.
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_CHR_TestImageOn
Nucleus Number 101
Description Generates a test-image of a selected video standard on selected video output
Technical - Validate the user input.
Execution Time 6 seconds.
User Input The user has to decide which test image, video standard and video output must
Error Number Description
10100 Generating the test image succeeded.
10101 Invalid input was provided.
10102 The Codec SYNC-module cannot be initialised.
10103 The Codec MIXER-module cannot be initialised.
10104 The Codec VPP-module cannot be initialised.
10105 The Codec DENC-module cannot be initialised.
10106 The digital board hardware information is corrupt
on the digital board. When no input is given, the default values will be used (see
user input description below). Make sure to use the proper nuclei to route the
video signal on the analogue board to get the video signal to the proper output.
Note: Although a DTT has a Chrysalis C3, the codec IC may never use the
YUV functionality of the internal DENC. This is specified by the hardware. The
digital boards for DTT do have a YUV-matrix. The signals from this YUV-matrix
are not routed to the regular video output connector but to the progressive scan
output connector.
- Initialise the SYNC module.
- Initialise the DISPLAY module.
- Initialise the MIXER module.
- Initialise the DENC module.
- Set the selected video standard.
- Generate the selected test image in memory.
- Start the DISPLAY module.
- Start the MIXER module.
- Start the DENC module according to the selected test image id.
be used: < Test image id > < Video standard > < Video output >
Test image id:
0 VERTICAL_COLOURBAR (default)
1 HORIZONTAL_COLOURBAR
2 WHITE
3 YELLOW
4 CYAN
5 GREEN
6 MAGENTA
7 RED
8 BLUE
9 BLACK
10 GRAY
11 TEST_IMAGE_FOR_PROGRESSIVE_SCAN
Video standard:
PAL Standard PAL 50 Hz (default)
NTSC Standard NTSC 60 Hz
Video output:
ALL CVBS and YC and RGB DACs are enabled (default)
CVBS CVBS DAC is enabled
YC Y and C DAC is enabled
RGB CVBS, R, G, and B DACs are enabled
YUV Y, U, and V DACs are enabled
PSCAN Progressive scan is enabled.
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Example
DS:> 101
010100:
Test OK @
DS:> 101 0 pal cvbs
010100:
Test OK @
DS:> 101 4 ntsc yc
010100:
Test OK @
Nucleus Name DS_CHR_TestImageOff
Nucleus Number 102
Description Switches the test-image off.
Technical - Stop the DENC module.
Execution Time Less than 1 second.
User Input None
Error Number Description
10200 Stopping the test image generation succeeded
10201 The Codec DENC-module failed.
Example
DS:> 102
010200:
Test OK @
Nucleus Name DS_CHR_SineOn
Nucleus Number 103
Description Generate an audio sine signal on the audio output of the digital board.
Note: Left channel 6kHz, right channel 12 kHz sine. Make sure to route the
signal first.
When ‘SPDIF’ is entered as a parameter, the SPDIF path will be activated
correctly to contain the sine wave.
Technical - De-mute the analogue board
- Set fifo parameters for audio
- Set the volume
- Set the I2S outputs and configuration paths
- Set the decoder mode
- Configure the audio decoder
- Put the AC3 audio in the fifo
- Send ‘prepare’ command to the audio decoder
- Send ‘play’ command to the audio decoder
Execution Time Less than 1 second
User Input None or ‘SPDIF’
Error Number Description
10300 The sine signal was successfully generated
10301 The analogue board could not be de-muted
10302 The audio decoder did not initialise
10303 The dsp2 (DUET) of the audio decoder did not configure
10304 The dsp1 (PALM) of the audio decoder did not configure
10305 There was a delay-error before starting
10306 Wrong input was given to the decoder function
10307 Wrong input was given to the decoder function @@@@@
10308 The audio decoder did not get into the ‘prepared’ state
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_CHR_SineOff
Nucleus Number 104
Description Stop generating the audio sine signal
Technical - Reset the audio block of the Codec
Execution Time Less than 1 second.
User Input None
Error Number Description
10400 Switching off the audio sine signal succeeded
10401 Failed to reset the audio decoder
Example
DS:> 104
010400:
Test OK @
Nucleus Name DS_CHR_SineBurst
Nucleus Number 105
Description Generate an audio sine signal on the audio output of the digital board for 4
seconds.
Note: Left channel 6kHz, right channel 12 kHz sine with some known hick-ups
Technical - Call the DS_CHR_SineOn nucleus
- Delay for 4 seconds
- Call the DS_CHR_SineOff nucleus
Execution Time 4 seconds
User Input None
Error Number Description
10500 The sine signal burst was successfully generated
10501 The delay did not succeed during the burst
10502 The audio sine could not be generated
Example
DS:> 105
010500:
Test OK @
Nucleus Name DS_CHR_MuteOn
Nucleus Number 106
Description Mute the audio outputs of the digital board
Technical - Send the ‘Mute’ command to the audio decoder
- Activate the ‘audio mute’ PIO pin
Execution Time Less than 1 second.
User Input “PIO” to just use the PIO pin mute. When muting using this, also de-mute using
this as this works ‘paired’.
Error Number Description
10600 Muting the audio succeeded
10601 Muting the audio through the PIO-pin failed
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_CHR_MuteOff
Nucleus Number 107
Description De-mute the audio outputs of the digital board
Technical - Send the ‘DeMute’ command to the audio decoder
- Deactivate the ‘audio mute’ PIO pin
Execution Time “PIO” to just use the PIO pin de-mute. Only de-mute using this when you muted
using the PIO parameter, as this works ‘’paired.
User Input None
Error Number Description
10700 De-muting the audio succeeded
10701 De-muting the audio through the PIO-pin failed
Example
DS:> 107
010700:
Test OK @
DS:> 107 PIO
010700:
Test OK @
Nucleus Name DS_CHR_DvLedOn
Nucleus Number 108
Description Check the connection to the DV-LED on the digital board by switching it on
Technical - Write to the PIO pin to light the DV LED
Execution Time Less than 1 second.
User Input None
Error Number Description
10800 Switching the DV-LED on succeeded
10801 Switching the DV-LED on failed
Example
DS:> 108
010800:
Test OK @
Nucleus Name DS_CHR_DvLedOff
Nucleus Number 109
Description Switch off the DV-LED on the digital board
Technical - Write to the PIO pin to switch off the DV LED
Execution Time Less than 1 second.
User Input None
Error Number Description
10900 Switching the DV-LED off succeeded
10901 Switching the DV-LED off failed
Example
DS:> 109
010900:
Test OK @
Nucleus Name DS_CHR_MacroVisionOn
Nucleus Number 110
Description Turn on MacroVision.
Technical - Set some registers of the DENC module in the Codec.
Execution Time Less than 1 second.
User Input None
Error Number Description
11000 Turning on MacroVision succeeded
11001 Turning on MacroVision failed
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_CHR_MacroVisionOff
Nucleus Number 111
Description Turn off MacroVision.
Technical - Set some registers of the DENC module in the Codec.
Execution Time Less than 1 second.
User Input None
Error Number Description
11100 Turning off MacroVision succeeded
11101 Turning off MacroVision failed
Example
DS:> 111
011100:
Test OK @
Nucleus Name DS_CHR_Peek
Nucleus Number 112
Description Peek a value on a specified address
Technical - Check the user input
Execution Time Less than 1 second.
User Input The address to peek on
Error Number Description
11200 Peeking on the specified address succeeded
11201 Peeking on the specified address failed, wrong user input
11202 Peeking on the specified address failed due to misalignment
Example
- Read out the address specified
- Check whether the address to be read is aligned on 4 bytes
DS:> 112 0xa0700000
011200: Value read = 0x000001BD
Test OK @
Nucleus Name DS_CHR_Poke
Nucleus Number 113
Description Poke a value on a specified address
Technical - Check the user input
Execution Time Less than 1 second.
User Input The address to poke and the value: <address><value>
Error Number Description
11300 Poking the specified address succeeded
11301 Poking the specified address failed, wrong user input
11302 Poking the specified address failed due to misalignment
Example
- Change the value on the address specified
- Check whether the address to be modified is aligned on 4 bytes
DS:> 113 0xa0700000 0xaabbccdd
011300:
Test OK @
Nucleus Name DS_CHR_INT_PICInterrupts
Nucleus Number 114
Description Test all interrupts of the priority interrupt controller
Technical - Install interrupt handlers
Execution Time Less than 1 second.
User Input Error Number Description
11400 Testing all the PIC interrupts succeeded
11401 Testing all the PIC interrupts failed
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_CHR_DMA_TestDMA
Nucleus Number 115
Description Test the memory to memory DMA transfer
Technical - Create a block with known data in memory
Execution Time Less than 2 seconds.
User Input Error Number Description
11500 The testing of the DMAs succeeded
11501 The initialisation of the DMAs failed for one or more DMA
11502 One or more DMAs failed the test
Example
- Copy this block to the consecutive area using 3 different DMAs
- Check whether all DMAs transferred the data properly
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
3.2 BOOT EEPROM (BROM)
Nucleus Name DS_BROM_Communication
Nucleus Number 200
Description Check the communication between the IIC controller of the Codec and the boot
Technical - Initialise IIC
Execution Time Less than 1 second.
User Input None
Error Number Description
20000 The data is properly read so the communication is OK
20001 The IIC bus was not accessible
20002 There was a timeout reading the device
20003 The IIC acknowledge was not received
20004 An IIC-bus error occurred
20005 The IIC bus initialisation failed
20006 An unexpected IIC error occurred
Example
Nucleus Name DS_BROM_WriteRead
Nucleus Number 201
Description Check whether the Boot EEPROM can be written to and read from
Technical - Initialise IIC
Execution Time Less than 1 second.
User Input None
Error Number Description
20100 The write-read test succeeded
20101 The write-read test failed
20102 An IIC-bus error occurred
20103 There was a timeout reading the device
20104 The IIC bus was not accessible
20105 The IIC acknowledge was not received
20106 Got unknown IIC bus error
20107 The IIC bus initialisation failed
Example
EEPROM
- Read something from the EEPROM
DS:> 200
020000:
Test OK @
- Write something to the EEPROM
- Read from the same location and check whether it is the same as written
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
3.3 NON VOLATILE RAM (NVRAM)
Nucleus Name DS_NVRAM_Communication
Nucleus Number 300
Description Check the communication between the IIC controller of the Codec and the
Technical - Initialise IIC
Important note: This nucleus only checks the physical connection between the Codec and IIC
Execution Time Less than 1 second.
User Input None
Error Number Description
30000 Something is properly read so the communication is OK
30001 The IIC bus was not accessible
30002 There was a timeout reading the device
30003 The IIC acknowledge was not received
30004 The communication with the device failed
30005 The IIC bus initialisation failed
Example
Nucleus Name DS_NVRAM_WriteRead
Nucleus Number 301
Description Check whether the EEPROM can be written to and read from
Technical - Initialise IIC
Execution Time Less than 1 second
User Input None
Error Number Description
30100 The write-read test succeeded
30101 The IIC bus could not be initialised
30102 There was an NVRAM IO error
30103 The value could not be read back from the NVRAM
Example
NVRAM EEPROM
- Read from a location in the NVRAM EEPROM device
EEPROM. If no EEPROM is mounted this test will fail. However other NVRAM
nuclei might still work because the software will store NVM data into flash
memory
DS:> 300
030000:
Test OK @
- If no IIC EEPROM was found then initialise flash memory to use NVM
pages
- Backup data from location to modify
- Write to location and read it back again
- Write back the backed up data to the location to leave the NVRAM as
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_NVRAM_Clear
Nucleus Number 302
Description Make the EEPROM empty, containing all zeroes.
Technical - Initialise IIC
Important note: The Hardware Diversity Information and unique identification number
Execution Time 16 seconds
User Input None
Error Number Description
30200 The clearing of the NVRAM succeeded
30201 There was an IIC error
30202 Clearing the NVRAM failed
Example
- If no IIC EEPROM was found then initialise flash memory to use NVM
pages
- Read the DVID and diversity string from NVM (either EEPROM or Flash)
- Create a memory block filled with zeroes
- Write this block to the NVRAM (either EEPROM or Flash)
- Write back the Read the DVID and diversity string to NVM (either
EEPROM or Flash)
(IEE1394-specific) of the Digital Video processing part is NOT cleared by this
nucleus!
DS:> 302
030200:
Test OK @
Nucleus Name DS_NVRAM_Modify
Nucleus Number 303
Description Modifies one or more locations in NVRAM and updates the checksum of the
Technical - Initialise IIC
Execution Time Less than 1 second
User Input 1. The location that must be modified
Error Number Description
30300 Modifying the NVRAM contents succeeded
30301 Unable to initialise NVM
30302 Modifying the NVRAM contents failed
30303 length out of range
30304 unable to decode length
30305 offset out of range
30306 unable to decode offset
30307 unknown location specified
30308 no location is specified
30309 number of values incorrect
30310 There was an IIC error
Example
section modified
- If no IIC EEPROM was found then initialise flash memory to use NVM
pages
- Decode user input
- Modify the NVRAM as indicated
- Validate the NVRAM by calculating the checksum and storing it
i.e. "ALL" "BOOT" "DIAGNOSTICS" "DOWNLOAD" "CONFIG"
"RECORDER" or no string if an offset from the base address of the
NVRAM is required
2. The offset and data which to put on the selected location
<offset> <length> <data>
DS:> 303 DIAGNOSTICS 5 1 0x5a
030300: Section is modified successfully
Test OK @
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_NVRAM_Read
Nucleus Number 304
Description Read out one or more locations in the NVRAM
Technical - Initialise IIC
Execution Time Less than 1 second
User Input 1. The location which must be read
Error Number Description
30400 Value read
30401 Unable to initialise NVM
30402 Reading the NVRAM contents failed
30403 Length out of range
30404 Unable to decode length
30405 Offset out of range
30406 Unable to decode offset
30407 Unknown location specified
30408 No location is specified
Example
- If no IIC EEPROM was found then initialise flash memory to use NVM
pages
- Decode user input
- Read from the NVRAM and return this info to the user
i.e. "ALL" "BOOT" "DIAGNOSTICS" "DOWNLOAD" "CONFIG"
"RECORDER" or no string if an offset from the base address of the
NVRAM is required
2. The offset and number of bytes to read
<offset> <length>
304 DIAGNOSTICS 0 6
030400: Value read = 0x00 0x00 0x00 0x00 0x00 0x5A
Test OK @
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
3.4 SDRAM (SDRAM)
Nucleus Name DS_SDRAM_WriteRead
Nucleus Number 400
Description Check all data lines, address lines and memory locations of the SDRAM
Technical - Test the data bus
Execution Time 11 seconds for 32 Mb
User Input None
Error Number Description
40000 The write-read test succeeded
40001 The data bus contains an error
40002 The address bus contains an error
40003 The SDRAM itself contains an error
Example
Nucleus Name DS_SDRAM_WriteReadFast
Nucleus Number 401
Description Check all data lines and address lines of the SDRAM
Technical - Test the data bus
Execution Time Less than 1 second
User Input None
Error Number Description
40100 The write-read test succeeded
40101 The data bus contains an error
40102 The address bus contains an error
Example
Nucleus Name DS_SDRAM_Write
Nucleus Number 402
Description Write to a specific un-cached memory address
Technical - Decode the user input and check its ranges and alignment on 4 bytes
Execution Time Less than 1 second
User Input 1. The location that must be modified
Error Number Description
40200 Writing to the SDRAM succeeded
40201 Writing to the SDRAM failed; Wrong user input
40202 Address is not dividable by 4
Example
- Test the address bus
- Test the integrity of the device itself (memory locations)
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_SDRAM_Read
Nucleus Number 403
Description Read from a specific un-cached memory address
Technical - Decode the user input and check the ranges
Execution Time Less than 1 second
User Input The location from which the data must be read
Error Number Description
40300 Reading from the SDRAM succeeded
40301 Reading from the SDRAM failed; Wrong user input
40302 Address is not dividable by 4
Example
- Read from the SDRAM and return this info to the user
(SDRAM starts at address 0xA0000000)
DS:> 403 0xa1000010
040300: Value read = 0xAD112222
Test OK @
Nucleus Name DS_SDRAM_DmaWriteRead
Nucleus Number 404
Description Write a pattern to the entire SDRAM using DMA and check the data
Technical - Check if the Stack pointer is not in the write range
Execution Time 24 seconds
User Input None.
Error Number Description
40400 Writing to the SDRAM succeeded
40401 Stack area definition ERROR!
40402 DMA controller could not be initialised.
40403 Not all data was transferred correctly
Example
- Clear a 64kb block and then fill it with a pattern
- Initialise the DMA controller and write the data to the SDRAM
- Then check if all the data was written correctly (except descriptor tables)
- Repeat the process 4 times with 4 different patterns
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
3.5 FLASH (FLASH)
Nucleus Name DS_FLASH_DevTypeGet
Nucleus Number 500
Description Get the device (revision) type information of the FLASH ICs. (type,
Technical - Set the timing for the flash writing
Execution Time Less than 1 second
User Input None
Error Number Description
50000 Getting the information from the FLASH succeeded
50001 Getting the information from the FLASH failed
Example
Nucleus Name DS_FLASH_WriteRead
Nucleus Number 501
Description Check whether the FLASH can be written to and read from
Technical - Find the test segment in flash
Execution Time Less than 1 second.
User Input None
Error Number Description
50100 The FLASH write-read test succeeded
50101 The test segment could not be found
50102 All bits in the TEST region are filled with 0 (region exhausted)
50103 The Write Read test failed
50104 The Write Failed
Example
Nucleus Name DS_FLASH_Read
Nucleus Number 502
Description Read from a specific memory address in FLASH
Technical - Decode the user input and check the ranges and whether the address is
Execution Time Less than 1 second.
User Input The location from which data must be read
Error Number Description
50200 Reading the FLASH succeeded
50201 Reading the FLASH failed; Wrong user input
50202 Address is not dividable by 4
Example
manufacturer, device ID and size)
- Write a command sequence to determine device type information
- Return the information to the user
DS:> 500
050000: Found FLASH memory:
NOR AMD 29DL640G 8MB,NOR AMD 29DL640G 8MB
Test OK @
- Read the data into SDRAM
- Modify the data
- Write this data from SDRAM to FLASH and verify it by reading back again
DS:> 501
050100:
Test OK @
aligned on 4 bytes
- Read the data and return this to the user
(FLASH starts at address 0xB8000000)
DS:> 502 0xb8000000
050200: Value read = 0x3C08A000
Test OK @
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_FLASH_ChecksumProgram
Nucleus Number 503
Description Check the checksum of the application partitions by recalculating and
comparing partition checksums
Technical - Determine the number of segments
- Find the application in each segment and determine its checksum
- Check whether the checksums stored match the newly calculated
Execution Time 6 seconds
User Input None
Error Number Description
50300 The checksum is valid, the test succeeded
50301 The checksum is invalid
Example
DS:> 503
050300:
BootCode checksum is: 0xBABE5B6F, which is correct
Diagnostics checksum is: 0xBABEBAFF, which is correct
Download checksum is: 0xBABEEDBF, which is correct
Application checksum is: 0xBABE8EEC, which is correct
Test OK @
Nucleus Name DS_FLASH_CalculateChecksum
Nucleus Number 504
Description Calculate the checksum over all memory addresses. Used to check entire
FLASH contents
Technical - Run the checksum calculation algorithm on all flash memory addresses
Execution Time 6 seconds
User Input None
Error Number Description
50400 Calculating the checksum over all addresses succeeded
Example
DS:> 504
050400: The Checksum = 0xBABE30A4
Test OK @
Nucleus Name DS_FLASH_CalculateChecksumFast
Nucleus Number 505
Description Calculate a checksum over a selected number of address locations
Technical - Run the checksum calculation algorithm on a selected number of flash
memory addresses
Execution Time 6 seconds
User Input None
Error Number Description
50500 Calculating the checksum over selected addresses succeeded
Example
DS:> 505
050500: The Checksum = 0xBABEB064
Test OK @
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
3.6 VIDEO INPUT PROCESSOR (VIP)
Nucleus Name DS_VIP_DevTypeGet
Nucleus Number 600
Description Get the device (revision) type information of the VIP IC
Technical - Initialise IIC
Execution Time Less than 1 second
User Input None
Error Number Description
60000 Getting the information from the VIP succeeded
60001 The IIC bus initialisation failed
60002 The was an error getting the information from the VIP
60003 Type not according to type stored in HW diversity string
Example
Nucleus Name DS_VIP_Communication
Nucleus Number 601
Description Check the communication between the IIC controller of the Codec and the VIP
Technical - Initialise IIC
Execution Time Less than 1 second
User Input None
Error Number Description
60100 Communicating with the VIP succeeded
60101 The IIC bus was not accessible
60102 There was a timeout reading the device
60103 The IIC acknowledge was not received
60104 The communication with the device failed
60105 The IIC bus initialisation failed
Example
Nucleus Name DS_VIP_ClockOutputOn
Nucleus Number 602
Description Switch the clock output on
Technical - Initialise IIC
Execution Time Less than 1 second
User Input None
Error Number Description
60200 Switching the clock output on succeeded
60201 Switching the clock output on failed
Example
- Read out the device (revision) type information of the VIP IC
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_VIP_ClockOutputOff
Nucleus Number 603
Description Switch the clock output off
Technical - Initialise IIC
Execution Time Less than 1 second
User Input None
Error Number Description
60300 Switching the clock output off succeeded
60301 Switching the clock output off failed
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
60400 Selecting the input of the VIP succeeded
60401 The user provided wrong input
60402 The VIP was not accessible
60403 An unsupported VIP was found
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
3.7 DIGITAL VIDEO INPUT OUTPUT CIRCUIT (DVIO)
Nucleus Name DS_DVIO_LinkDevTypeGet
Nucleus Number 700
Description Get the device (revision) type information of the 1394 Link layer IC
Technical - Initialise the PIO pins on the Codec
Execution Time Less than 1 second
User Input None
Error Number Description
70000 Getting the information from the link layer IC succeeded
70001 Getting the information from the link layer IC failed
70002 Type not according to type stored in HW diversity string
Example
Nucleus Name DS_DVIO_PhyDevTypeGet
Nucleus Number 701
Description Get the device (revision) type information of the 1394 Physical layer IC
Technical - Initialise the PIO pins of the Codec
Execution Time Less than 1 second
User Input None
Error Number Description
70100 Getting the information from the physical layer IC succeeded
70101 The physical layer IC was not accessible
70102 Getting the information from the physical layer IC failed
70103 Type not according to type stored in HW diversity
Example
Nucleus Name DS_DVIO_LinkCommunication
Nucleus Number 702
Description Check the accessibility of the 1394 Link layer IC by writing to and reading from
Technical - Initialise the PIO pins of the Codec
Execution Time Less than 1 second
User Input None
Error Number Description
70200 Communicating with the link layer IC succeeded
70201 Communicating with the link layer IC failed
70202 Result of nucleus not according to HW diversity string
Example
- Read out the ID register
DS:> 700
070000: Device type of the link layer IC: ffc00301
Test OK @
- Write the PHY-access register in the Link chip to indicate phy read access
- Wait until the link chip has obtained the value from the phy-chip
- Read this out and filter the data to be returned to the user
DS:> 701
070100: Physical layer IC: VendorID: 0x006037, ProductID: 0x412801
Test OK @
a specific address
- Write a pattern to the CYCTM register of the link chip
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_DVIO_PhyCommunication
Nucleus Number 703
Description Check the accessibility of the 1394 Physical layer IC by writing to and reading
Technical - Initialise the PIO pins of the Codec
Execution Time Less than 1 second
User Input None
Error Number Description
70300 Communicating with the physical layer IC succeeded
70301 The physical layer IC was not accessible
70302 Communicating with the physical layer IC failed
70303 Result of nucleus not according to HW diversity string
Example
from a specific address
- Initialise IIC
- Write the data to be written to the PHY-chip to the link chip first
- Wait until the link chip indicates that the data has been written to the PHY
- Write the PHY-access register in the Link chip to indicate PHY read access
- Wait until the link chip has obtained the value from the PHY-chip
- Test whether the value read back equals the one previously written
DS:> 703
070300:
Test OK @
Nucleus Name DS_DVIO_Routing
Nucleus Number 704
Description Route a DV stream containing an audio and video signal through the physical
Technical - Initialise the DMA to transfer 5 frames PAL/NTSC
Execution Time 6-10 seconds (6 when OK, 10 when no stream or error)
User Input None
Error Number Description
70400 Routing the signals succeeded
70401 The 1394 link chip could not be initialised properly
70402 There was a syntax error in the DV stream
70403 DMA could not copy DV stream to memory. Stream connected?
70404 DMA not working properly
Example
and link layer ICs to the Codec. This test works for both NTSC and PAL.
- Initialise the DV de-multiplexer
- Initialise the 1394 interface and start reception of the DV stream
- Check whether the stream was copied to memory properly by the byte
input interface (port to memory type DMA)
DS:> 704
070400:
Test OK @
Nucleus Name DS_DVIO_DetectNode
Nucleus Number 705
Description Check whether a DV node can be detected by the hardware. This test works for
Technical - Initialise the 1394 interface
Execution Time 3 or 5 seconds (3 when OK, 5 when no stream or error)
User Input None
Error Number Description
70500 The node was detected OK
70501 The 1394 link chip could not be initialised properly
70502 Unable to write to 1394 PHY chip
70503 Unable to read from 1394 PHY chip
70504 No node was detected
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_DVIO_DetectStream
Nucleus Number 706
Description Check whether a DV stream can be detected by the hardware. This test works
Technical - Initialise the 1394 interface
Execution Time 3 or 5 seconds (3 when OK, 5 when no stream or error)
User Input None
Error Number Description
70600 The stream was detected
70601 The 1394 link chip could not be initialised properly
70602 No stream detected
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
3.8 PROGRESSIVE SCAN CIRCUIT (PSCAN)
Nucleus Name DS_PSCAN_DevTypeGet
Nucleus Number 800
Description Get the device (revision) type information of the progressive scan ic.
Technical - Initialise the progressive scan ic.
Execution Time 1 second
User Input None
Error Number Description
80000 Everything went well.
80001 The communication with the device failed
80002 No chip was expected
Example
Nucleus Name DS_PSCAN_Communication
Nucleus Number 801
Description Check the communication between the IIC controller of the Codec and the
Technical - Initialise IIC
Execution Time Less than 1 second
User Input None
Error Number Description
80100 Communicating with the progressive scan ic succeeded
80101 The IIC bus was not accessible
80102 There was a timeout reading the device
80103 The IIC acknowledge was not received
80104 Communicating with the progressive scan ic failed
80105 The initialisation of the IIC bus failed
80106 The read data is not the same as the written data
80107 No chip was expected
Example
Nucleus Name DS_PSCAN_TestImageOn
Nucleus Number 802
Description Generate the test images that are present on the progressive scan IC.
Technical - Determine whether the user wanted a HATCH or a FRAME image pattern
Execution Time Less than 1 second
- Try to read the version register of the progressive scan ic.
DS:> 800
080000:
Chip name : 2300
Chip version : 1
Test OK @
DS:> 800
080000:
Chip name : ADV7196
Test OK @
DS:> 800
080000:
Chip name : ADV7302
Test OK @
progressive scan IC
- Write data to a register of the progressive scan ic through IIC
DS:> 801
080100:
Test OK @
- Initialise the PIO pins of the Codec
- Initialise IIC
- Reset the DENC
- Enable the 27Mhz clock
- Send all settings for the pattern to the DENC through IIC
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
User Input In case of ADV7196:
Error Number Description
80200 The generation of the test image succeeded
80201 Unable to initialise PSCAN IC
80202 Unable to reset DENC
80203 Unable to generate image
80204 No chip was expected
Example
When no input is given “HATCH” is the default
-“HATCH”
-“FRAME”
Remark:
“HATCH” is a crosshatch test pattern (horizontal and vertical white lines are
displayed against a black background)
“FRAME” is a uniform coloured frame/field test pattern (default white).
In case of FLI2300: Nothing.
DS:> 802 HATCH
080200:
Test OK @
Nucleus Name DS_PSCAN_TestImageOff
Nucleus Number 803
Description Switch off the generated test image
Technical - Initialise IIC
- Send the default DENC settings to the DENC through IIC
Execution Time Less than 1 second
User Input None
Error Number Description
80300 Turning off the test image succeeded
80301 Unable to initialise PSCAN IC
80302 IIC Error during writing PSCAN IC
80303 No chip was expected
Example
DS:> 803
080300:
Test OK @
Nucleus Name DS_PSCAN_TestImageColourSettingsSet
Nucleus Number 804
Description Set the colour of the hatch- or the frame- field to a different value than the
default white
Technical - Determine which colour must be set.
- Initialise IIC.
- Enable 27 MHz PSCAN Clock.
- Send all settings to the DENC through IIC.
Execution Time Less than 1 second.
User Input A colour string of one of the next non-case sensitive strings ( WHITE, BLACK,
RED, GREEN, BLUE, YELLOW, CYAN, MAGENTA ) or Y Cr Cb (hexa-)
decimal values.
Error Number Description
80400 Setting the new colour-settings succeeded
80401 The user provided wrong input
80402 Unable to initialise PSCAN IC
80403 Unable to set colour
80404 No chip was expected
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_PSCAN_TestImageColourSettingsGet
Nucleus Number 805
Description Get the colour settings of the hatch- or the frame- field.
Technical - Initialise IIC.
- Read the colour settings from the DENC through IIC.
Execution Time Less than 1 second.
User Input None
Error Number Description
80500 Getting the colour-settings succeeded
80501 The progressive scan DENC-IC was not accessible through IIC
80502 Unable to get colour
80503 No chip was expected
Example
DS:> 805
080500: Colour Y Cr Cb values: 0xD2 0x92 0x10
Test OK @
Nucleus Name DS_PSCAN_Routing
Nucleus Number 806
Description Route a video signal from the codec host processor through the progressive
scan ICs to the progressive scan output of the set.
Note: To route the progressive scan to the output of the set, first call the
nucleus to do the video routing on the analogue (part of the) board.
Technical - Initialise the PIO pins of the codec
- Initialise IIC
- Reset the DENC
- Enable the 27Mhz clock
- Send all settings to the DENC through IIC.
Execution Time Less than 1 second.
User Input None
Error Number Description
80600 Routing path is created successfully.
80601 Unable to initialise the Codec.
80602 Unable to access DENC
80603 Unable to access de-interlacer.
80604 Wrong chips were expected.
Example
DS:> 806
080600:
Test OK @
Nucleus Name DS_PSCAN_DevTypeGetDeinterlacer
Nucleus Number 807
Description See nucleus 800.
Example
DS:> 807
080700:
Chip name : 2300
Chip version : 1
Test OK @
Nucleus Name DS_PSCAN_CommunicationDeinterlacer
Nucleus Number 808
Description See nucleus 801.
Example
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
3.9 BASIC ENGINE (BE)
Nucleus Name DS_BE_CommunicationEcho
Nucleus Number 900
Description Check the communication between the digital board and the basic engine by
Technical - Check if an AV2 or AV3 is connected
Execution Time Less than 1 second
User Input None
Error Number Description
90000 Communicating with the BE over the S2B interface succeeded
90001 There was a time-out while communicating
90002 The Basic Engine returned an unexpected result
90003 The Basic Engine returned an error code
90004 No acknowledge received from BE
90005 Communicating with the Basic Engine failed
90006 Echo check failed, no echo received
90007 Echo check failed, received wrong pattern
Example
Nucleus Name DS_BE_Reset
Nucleus Number 901
Description Reset the basic engine
Technical - Check if an AV2 or AV3 is connected
Execution Time 2 seconds on AV2
User Input None
Error Number Description
90100 Resetting the Basic Engine succeeded
90101 Resetting the Basic Engine failed
Example
issuing an echo command
- In case of an AV2 Check the communication between the digital board and
the basic engine by issuing an echo command over the S2B interface
- Check if the BE returned the string 0x00 0xAA 0x55
- In case of an AV3 send an ATAPI TEST_UNIT_READY command
DS:> 900
090000:
Test OK @
- In case of an AV2 Toggle the reset pin of the I2S interface
- In case of an AV3 Toggle the reset pin of the IDE interface
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_BE_GetSelftestResult
Nucleus Number 902
Description Return the self-test results through the service port
Technical - Check if an AV2 or AV3 is connected
- In case of an AV2 Send the S2B GET_SELF_TEST_RESULT command
- In case of an AV3 Send the ATAPI REPORT_DRIVE_DIAGNOSTICS
command
- On error display the specific error codes received from the BE
Execution Time Less than 1 second
User Input None
Error Number Description
90200 Self test succeeded, no errors
90201 There was a time-out while communicating
90202 The Basic Engine returned an unexpected result
90203 The BE returned an error code
90204 No acknowledge received from BE
90205 Communicating with the Basic Engine failed
90206 Basic Engine returned no info
90207 Self test failed, errors are echoed
Example
DS:> 902
090200:
Self-test result byte : 00000000
Self-test result byte : 00000000
Self-test result byte : 00000000
Test OK @
Nucleus Name DS_BE_VersionGet
Nucleus Number 903
Description Get the version of the basic engine and that of the optical unit
Technical - Check if an AV2 or AV3 is connected
- In case of an AV2 send the S2B GET_VERSION_NUMBER command
- In case of an AV3 send the ATAPI INQUIRY command
- Send the GET_OPU_VERSION command
- Display the returned version information
Execution Time Less than 1 second
User Input None
Error Number Description
90300 BE version OK
90301 There was a time-out while communicating
90302 The Basic Engine returned an unexpected result
90303 The BE returned an error code
90304 No acknowledge received from BE
90305 Communicating with the Basic Engine failed
90306 The BE returned no info
Example (AV2)
Example (AV3)
DS:> 903
090300: BE version = 20.09.18 Optical unit version = 3C.00.09.41.08
Test OK @
DS:> 903
090300:
BE version = 31.30.24. PHILIPS ,VAD8031
,31302400,REL_8031_313024 2073,
Optical unit version = 00.06.82.19.00
Test OK @
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_BE_TrayOut
Nucleus Number 904
Description Open the tray of the basic engine
Technical - Check if an AV2 or AV3 is connected
Execution Time Approximately 2 seconds
User Input None
Error Number Description
90400 The command executed successfully
90401 There was a time-out while communicating
90402 The Basic Engine returned an unexpected result
90403 The BE returned an error code
90404 No acknowledge received from BE
90405 Unable to enter normal mode
90406 Communicating with the Basic Engine failed
Example
- In case of an AV2 Send the S2B TRAY_OUT command
- In case of an AV3 send an ATAPI START_STOP_UNIT command
DS:> 904
090400:
Test OK @
Nucleus Name DS_BE_TrayIn
Nucleus Number 905
Description Close the tray of the basic engine
Technical - Check if an AV2 or AV3 is connected
Execution Time Approximately 1 - 2 seconds
User Input None
Error Number Description
90500 The command executed successfully
90501 There was a time-out while communicating
90502 The Basic Engine returned an unexpected result
90503 The BE returned an error code
90504 No acknowledge received from BE
90505 Unable to enter normal mode
90506 Communicating with the Basic Engine failed
Example
- Send the S2B TRAY_IN command
- In case of an AV3 send an ATAPI START_STOP_UNIT command
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_BE_WriteReadDvdRw
Nucleus Number 906
Description Write data to and read data from a DVD+RW or DVD-RW disc through the
Technical - Check if an AV2 or AV3 is connected
Execution Time Approximately 20 seconds
User Input None
Error Number Description
90600 The command executed successfully
90601 This nucleus cannot be executed because the Self-Test failed
90602 The BE cannot enter normal operating mode
90603 Unable to send the tray in
90604 Unable to read TOC from disc
90606 Writing the test pattern to DVD+RW or DVD-RW failed
90607 Reading back the test pattern from DVD+RW of DVD-RW failed
90608 Compare check failed
90609 Calibrating DVD+RW or DVD-RW failed
Example
basic engine for verification of the writing
- Execute DS_BE_GetSelftestResults
- Send the TRAY_IN command
- Send the READ_TOC command
- Generate a random disc location
- Generate test data to write to the DVD+RW
- In case of an AV2 Transfer the test data to the disc location using DMA
- In case of an AV3 Transfer the test data to the disc location using PIO
mode ATAPI WRITE_10
- In case of an AV2 Read back the data from disc using DMA
- In case of an AV3 Transfer the test data to the disc location using PIO
mode ATAPI READ_10
- Compare the two data areas and check whether the areas are equal
90605
DS:> 906
090600: DVD+RW test on sector 0x5dbe0: OK
Test OK @
DS:> 906
090600: DVD-RW test on sector 0x304e0: OK
Test OK @
Invalid disc is loaded, please insert a DVD+RW or DVD-RW
disc
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_BE_WriteReadDvdR
Nucleus Number 907
Description Write data to and read data from a DVD+R or DVD-R disc through the basic
Technical - Check if an AV2 or AV3 is connected
Execution Time Approximately 20 seconds
User Input None
Error Number Description
90700 The command executed successfully
90701 This nucleus cannot be executed because the Self-Test failed
90702 The BE cannot enter normal operating mode
90703 Unable to send the tray in
90704 Unable to read TOC from disc
90705 Invalid disc is loaded, please insert a DVD+RW disc
90706 Unable to write, the DVD+R or DVD-R disc is full
90707 No writable DVD+R or DVD-R sector found
90708 Writing the test pattern to DVD failed
90709 Reading back the test pattern from DVD failed
90710 Compare check failed
Example
engine for verification of the writing
- Execute DS_BE_GetSelftestResults
- Send the TRAY_IN command
- Send the READ_TOC command
- Use the OPC area to test if the DVD+R or DVD-R is (still) writable
- Generate test data to write to the DVD+R or DVD-R
- In case of an AV2 Transfer the test data to the disc location using DMA
- In case of an AV3 Transfer the test data to the disc location using PIO
mode ATAPI WRITE_10
- In case of an AV2 Read back the data from disc using DMA
- In case of an AV3 Transfer the test data to the disc location using PIO
mode ATAPI READ_10
- Compare the two data areas and check whether the areas are equal
DS:> 907
090700: DVD+R test on sector 0x36210: OK
Test OK @
DS:> 907
090700: DVD-R test on sector 0x30000: OK
Test OK @
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Total time the power power on (HR:MIN)
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Note: Not for ATAPI based drives!
Nucleus Name DS_BE_StatisticalInformationGet
Nucleus Number 908
Description Retrieve the statistical information from the basic engine
Technical - Check if an AV2 or AV3 is connected
Execution Time Less than 1 second on AV2
User Input None
Error Number Description
90800 The command executed successfully
90801 There was a time-out while communicating
90802 The Basic Engine returned an unexpected result
90803 The BE returned an error code
90804 No acknowledge received from BE
90805 Communicating with the Basic Engine failed
90806 The BE returned no info
Example (AV2)
Example (AV3)
Command may not work for ATAPI based drives!
- In case of an AV2 Send the S2B GET_STATISTICAL_INFO command
- In case of an AV3 Send the transparent BIT engine
GET_STATISTICAL_INFO command
- Display the info returned from the BE
2 seconds on AV3
DS:> 908
Number of times Tray went Open/Closed : 4
Total minutes the CD laser was on : 0
Total minutes the DVD laser was on : 0
Total minutes the write laser was on : 0
090800:
Test OK @
DS:> 908
Number of times Tray went Open/Closed
4
0:0h
Total time of reading CDROM discs (HR:MIN)
0:0h
Total time of reading high speed CD-R discs (HR:MIN) 0:0h
Total time of reading other CD-R discs (HR:MIN) 0:0h
Total time of reading high speed CD-RW discs (HR:MIN) 0:0h
Total time of reading other CD-RW discs (HR:MIN) 0:0h
Total time of reading high speed DVD SL discs (HR:MIN) 0:0h
Total time of reading other DVD SL discs (HR:MIN) 0:0h
Total time of reading high speed DVD DL discs (HR:MIN) 0:0h
Total time of reading other DVD DL discs (HR:MIN) 0:0h
Total time of reading high speed DVD+R discs (HR:MIN) 0:0h
Total time of reading other DVD+R discs (HR:MIN) 0:2h
Total time of reading high speed DVD+RW discs (HR:MIN) 0:0h
Total time of reading other DVD+RW discs (HR:MIN) 0:35h
Total time of writing DVD+R discs at 2.4 x (HR:MIN) 0:0h
Total time of writing DVD+R discs at 4 x (HR:MIN) 0:0h
Total time of writing DVD+RW discs at 2.4 x (HR:MIN) 0:0h
Total time of writing DVD+RW discs at 4 x (HR:MIN) 0:0h
090800:
Test OK @
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Note: Not for ATAPI based drives!
Nucleus Name DS_BE_StatisticalInformationReSet
Nucleus Number 909
Description Reset the statistical information in the basic engine
Technical - Check if an AV2 or AV3 is connected
Execution Time 2 seconds
User Input None
Error Number Description
90900 The command executed successfully
90901 There was a time-out while communicating
90902 The Basic Engine returned an unexpected result
90903 The BE returned an error code
90904 No acknowledge received from BE
90905 Communicating with the Basic Engine failed
Example
Command may not work for ATAPI based drives!
- In case of an AV2
- Send the S2B RESET_STATISTICAL_INFO command
- Send the S2B POWER_DOWN command
- Toggle the reset pin of the I2S interface
- In case of an AV3 Send the transparent BIT engine
RESET_STATISTICAL_INFO command
DS:> 909
090900:
Test OK @
Note: Not for ATAPI based drives!
Nucleus Name DS_BE_ErrorLogGet
Nucleus Number 910
Description Get the error log from the basic engine
Technical - Check if an AV2 or AV3 is connected
Execution Time Less than 1 second
User Input None
Error Number Description
91000 The command executed successfully
91001 There was a time-out while communicating
91002 The Basic Engine returned an unexpected result
91003 The BE returned an error code
91004 No acknowledge received from BE
91005 Communicating with the Basic Engine failed
91006 The BE returned no info
Example (AV2)
Example (AV3)
Command may not work for ATAPI based drives!
- In case of an AV2 Send the S2B GET_ERROR command
- In case of an AV3 Send the transparent BIT engine GET_ERROR and
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Note: Not for ATAPI based drives!
Nucleus Name DS_BE_ErrorLogReset
Nucleus Number 911
Description Reset the error log in the basic engine
Technical - Check if an AV2 or AV3 is connected
Execution Time 2 seconds
User Input None
Error Number Description
91100 The command executed successfully
91101 There was a time-out while communicating
91102 The Basic Engine returned an unexpected result
91103 The BE returned an error code
91104 No acknowledge received from BE
91105 Communicating with the Basic Engine failed
Example
Command may not work for ATAPI based drives!
- In case of an AV2
- Send theS2B RESET_STATISTICAL_INFO command
- Send the S2B POWER_DOWN command
- Toggle the reset pin of the I2S interface
- In case of an AV3 Send the transparent BIT engine
RESET_STATISTICAL_INFO command
DS:> 911
091100:
Test OK @
Nucleus Name DS_BE_JitterOptimise
Nucleus Number 912
Description Perform jitter optimisation:
A formatted DVD must be loaded into the engine before executing this nucleus
Technical - Check if an AV2 or AV3 is connected
- Send the TRAY_IN command
- Send the READ_TOC command
- In case of an AV2
- Send the JITTER_COMMAND command with parameter 0x00 0x00
- Send the JITTER_COMMAND command with parameter 0x00 0x01
- Send the JITTER_COMMAND command with parameter 0x00 0x02
until offset 0x80 is received
- In case of an AV3 Send the MEASURE_JITTER_BLER_PPN command
and display the average jitter and bler values
Execution Time Approximately 20 seconds
User Input None
Error Number Description
91200 Optimising jitter succeeded
91201 There was a time-out while communicating
91202 The Basic Engine returned an unexpected result
91203 The Basic Engine returned an error code
91204 No acknowledge received from BE
91205 Unable to send tray in
91206 Unable to read the disc
91207 No disc is loaded
91208 Unknown disc is loaded
91209 Unable to enter service mode
Example (AV2)
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Note: Not for ATAPI based drives!
Nucleus Name DS_BE_FocusOn
Nucleus Number 913
Description Put the laser of the BE into focus
Technical - Check if an AV2 or AV3 is connected
Execution Time 3 seconds
User Input None
Error Number Description
91300 Focus on succeeded
91301 There was a time-out while communicating
91302 The Basic Engine returned an unexpected result
91303 The BE returned an error code
91304 No acknowledge received from BE
91305 Communicating with the Basic Engine failed
91306 Unable to enter service mode
Example
Command may not work for ATAPI based drives!
- In case of an AV2 Send the FOCUS command with parameter 0x01
- In case of an AV3 Send the transparent BIT engine FOCUS command
DS:> 913
091300:
Test OK @
Note: Not for ATAPI based drives!
Nucleus Name DS_BE_FocusOff
Nucleus Number 914
Description Turn off putting the laser of the BE into focus
Technical - Check if an AV2 or AV3 is connected
Execution Time Less than 1 second on AV2
User Input None
Error Number Description
91400 Focus off succeeded
91401 There was a time-out while communicating
91402 The Basic Engine returned an unexpected result
91403 The BE returned an error code
91404 No acknowledge received from BE
91405 Communicating with the Basic Engine failed
91406 Unable to enter service mode
Example
Command may not work for ATAPI based drives!
- In case of an AV2 Send the FOCUS command with parameter 0x00
- In case of an AV3 Send the transparent BIT engine FOCUS command
2 seconds on AV3
DS:> 914
091400:
Test OK @
Nucleus Name DS_BE_MotorOn
Nucleus Number 915
Description Turn on the turntable motor
Technical - Check if an AV2 or AV3 is connected
Execution Time Less than 1 second on AV2
User Input None
Error Number Description
91500 Turn table motor is on
91501 There was a time-out while communicating
91502 The Basic Engine returned an unexpected result
91503 The BE returned an error code
91504 No acknowledge received from BE
91505 Communicating with the Basic Engine failed
91506 Unable to enter service mode
Example
- In case of an AV2 Send the TURN_TABLE_MOTOR_ON command
- In case of an AV3 Send the transparent BIT engine TTM command
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_BE_MotorOff
Nucleus Number 916
Description Turn off the turntable motor
Technical - Check if an AV2 or AV3 is connected
- In case of an AV2 Send the TURN_TABLE_MOTOR_OFF command
- In case of an AV3 Send the transparent BIT engine TTM command
Execution Time Less than 1 second on AV2
4 seconds on AV3
User Input None
Error Number Description
91600 Turn table motor is off
91601 There was a time-out while communicating
91602 The Basic Engine returned an unexpected result
91603 The BE returned an error code
91604 No acknowledge received from BE
91605 Communicating with the Basic Engine failed
91606 Unable to enter service mode
Example
DS:> 916
091600:
Test OK @
Nucleus Name DS_BE_Tilt
Nucleus Number 920
Description Test the tilt mechanism control loop, or allow its proper functioning to be
measured.
Before executing this nucleus a non-empty disc must be loaded in the recorder
Technical - Check if an AV2 or AV3 is connected
- In case of an AV2
- Send the TRAY_IN command
- Send the READ_TOC command
- Send the TILT_COMMAND command with parameter 0x00 0x00
- Send the TILT_COMMAND command with parameter 0x00 0x01
- Send the TILT_COMMAND command with parameter 0x00 0x02
- In case of an AV3 display a “not supported” message
Execution Time Approximately 15 seconds
User Input None
Error Number Description
92000 The command executed successfully
92001 There was a time-out while communicating
92002 The Basic Engine returned an unexpected result
92003 The Basic Engine returned an error code
92004 No acknowledge received from BE
92005 Unable to send tray in
92006 Unable to read the disc
92007 No disc is loaded
92008 Unknown disc is loaded
92009 Unable to enter service mode
92010 This nucleus is not supported by the engine
Example (AV2)
Reference : SGP_AVS_SW_ATLAS-05-04 Classification : COMPANY RESTRICTED
Version : 3.6 Project : ATLAS_DSW
Status : Draft Chapter : User Manual
Date : 2006-05-25 Section : Diagnostic Software
Nucleus Name DS_BE_CheckDisc
Nucleus Number 921
Description Check whether there is a disc inside the BE
Technical - Send the TRAY_IN command
- Send the READ_TOC command
- Display the Disc type info
- If Disc type is a DVD+R(W), then read ADIP info.
- Display manufacturer and media type.
Execution Time Approximately 10 seconds
User Input None
Error Number Description
92100 There was a disc inside the set
92101 Unable to load the tray
92102 Error received from BE
Example
DS:> 921
092100:
Disc type: DVD+RW disc
Disc manufacturer id: PHILIPS
Media type id: 010
Test OK @
DS:> 921
090500:
Disc type: None
Test OK @
DS:> 921
092100:
Disc type: DVD+R disc
Disc manufacturer id: RICOHJPN
Media type id: R00
Test OK @
Nucleus Name DS_BE_SledgeMotor
Nucleus Number 922
Description Send the sledge to its home position, then to the middle of the disc, and then to
the end.
Technical - Send the PCS_COMMAND command with parameter 0x03 0x00
- Send the PCS_COMMAND command with parameter 0x02 0x00
- Send the PCS_COMMAND command with parameter 0x00 0x01
- Send the PCS_JUMP_SLEGE_STEPS command for 3 times
- Send the PCS_COMMAND command with parameter 0x00 0x00
Execution Time 4 seconds on AV2
11 seconds on AV3
User Input None
Error Number Description
92200 The command executed successfully
92201 There was a time-out while communicating
92202 The Basic Engine returned an unexpected result
92203 The BE returned an error code
92204 No acknowledge received from BE
92205 Communicating with the Basic Engine failed
92206 Unable to enter service mode
Example