Hi,
This is a short FAQ about DVP Evaluation Software (former XRC software) that comes together with boards such as:
EVAL-ADV7611EB1Z,
EVAL-ADV7612EB1Z,
EVAL-ADV7611EB2Z,
EVAL-ADV7612EB2Z;
EVAL-ADV7844EB1Z
1. What is DVP Evaluation Software?
It is a software that allows for evaluation of ADI video parts.
In configuration where evaluation board is connected to PC/Laptop using USB connector.
Evaluation boards have an USB chip that works effectively as a I2C to USB converter,
so I2C registers from all devices can be read using software on a PC. See screenshot below.
2. What DVP Evaluation Software is capable of?
It allows for accessing registers, downloading scripts, reading back data etc.
Additionally DVP Evaluation Software shows values of registers
associated with their names (see screenshot). Additional feature that is worth
mentioning is a fact that it allows for Python scripting. User can write any piece
of software that reads/writes registers in any algorithmic order (loops,
condition statements, etc) ; outputting/inputtnig data from files; building GUI
blocks (with wx python) showing any data and interpretation of user is interested in;
3. What operating systems are supported:
Windows XP
Windows 7
4. Notes regarding Windows 7.
In older version of DVP Evaluation Software - script files and boards files
are installed in Program Files folder. Windows 7 by default doesn't allow
application itself to modify own files in those folders, therefore it is
recommended to run DVP Evaluation Software as an Administrator.
5. How to upload/add new boards into DVP Evaluation Software?
To add new boards into DVP Evaluation Software you will need:
a) board specific files
b) DVP Evaluation Software installed on your PC.
"Board files" (or board specific files) is a directory structure that contains
set of specific .xml , script files, and board_info files files.
.xml file - contains XML description of register maps and registers of device (let say ADV7611)
script files - is usually a single .txt script file that contains number of scripts to set part
into particular working mode (e.g. signle script that configures ADV7611 and ADV7511
on a one board to receive HDMI on ADV7611's side and output it from ADV7511).
Script files must have following name: [NAME_OF_DEVICE]-VER.X.A.txt
(Where Name_of_device - e.g. ADV7611, X - major version number; A - minor
version number that can be ended with letter; there must be no more dots or hyphens
in name; example correct one is: ADV7611-VER.2.9c.txt)
board_info.txt file - additional installation file telling DVP Evaluation Software how
board should be installed (e.g. receiver board).
Example board files ADV7611:
>>ADV7611 (folder that contains following):
ADV7611.xml (file)
board_info.txt (file)
>> Script (subfolder, which contains):
ADV7611-VER.2.9c.txt (script folder).
To upload new board:
Place whole board files structure (including top folder e.g. ADV7611) into:
Where_DVP_Evaluation_Software_is_installed\xml\New Boards\[HERE],
Example:
Where_DVP_Evaluation_Software_is_installed\xml\New Boards\ADV7611
Run your DVP Evaluation Software and click "Upload boards".
Note: that in case of Windows 7 you may need administrator priviliges to allow program
for modification of board files.
You may also find useful this post: http://ez.analog.com/message/31501#31501
6. After powering up board - DVP Evaluation Software shows an I2C error.
There might be few possible problems:
a. I2C map addresses are not set in your video part:
Video components by Analog Devices contain number of I2C map
(such as CP Map, IO Map, HDMI Map and other). Only main maps (such as
IO Maps are programmed at start). Therefore when powering up board
and opening CP Map - you may get error. Go first to Main Map (or IO Map)
and configure CP Map address to desried (registers to set slave addresses
are on very bottom of IO Map/Main Map -> between 0xF0 ... 0xFF)
b. Repeater driver running and keeping I2C bus busy
Some of video boards come with microcontroller that is preloaded with software.
This software may keep I2C bus busy and not allow your PC to communicate
with board. Make sure software driver is disabled (SW Enable switch on your board)
More Q&A to come.
