Cts.ini - Studer OnAir 3000 Service Instructions Manual

STUDER Professional Audio GmbH

5.3.1 cts.ini

In the file Cts.ini an html-like syntax is used. There exist different areas in this file that configure different parts
of the program. Each area is started by <AreaName> and ended by </AreaName>. At time of writing there exist
three different areas.
Caution: Don't change the syntax or capitalizations; also take care to keep the whitespaces after opening
brackets and before closing brackets. To comment out the rest of a line write "#". To comment out the
rest of the file, write a single "*" into one line.
The first area, namely <ConfigFiles>, specifies where cts will find the binary files for each processor on a DSP
Card. The syntax is as follows:
( slot processorID filepath\filename )
With: slot: specifies to which card this binary goes (valid values: 0 ... 5)
processorID: which processor it goes to:
16 – DSP1
17 – DSP2
18 – DSP3
19 – DSP4
20 – DSP5
21 – DSP6
22 – SH4
23 – SLotector
25 – VDCA
A valid example would be:
( 5 21 \firmware\test_0_5.ldr )
In case there is an illegal entry in one of those lines, the user will be alerted via the Log Window. The download
will stop at that point.
The second area starts with the tag <TestTypes> and ends with </TestTypes> respectively. Here is being
specified which test IDs cts will recognize as a valid test ID; and, more importantly, which type of test this test
belongs to. Thus firmware developers may define new tests without changing cts. The new test just has to be
one of the existing kinds of tests. At time of writing there are three kinds of tests.
•
Simple test: The test is executed on one or multiple processors (independent from each other) at the
same time on one board, no other processors interfere or interact with this test
•
Multi test: The test is executed on one processor, while all other processors on the same board execute
the same test, but just in response to the processor under test.
•
Mirror test: The test is executed on one or multiple processors on one board, while DSP1 on another
board (specified as the mirror card) executes a specific test to loop back test data
The syntax is as follows:
( testID TestType )
With: testID: either 500 or 1000 + the test number given by the firmware developer
where 500 is used for a DSP test and 1000 is used for a SH4 test
TestType: one of the following:
Simple
Multi
Mirror
A valid example would be:
( 502 Simple )
13.Feb.06
Compact SCore Technical Info
17/22