OM5721 Ver la hoja de datos (PDF) - Philips Electronics

Número de pieza

componentes Descripción

Fabricante

OM5721

STB5660 (Set-Top Box) STB concept

Philips Electronics 

Philips Semiconductors

STB5660 (Set-Top Box) STB concept

Product specification

OM5721

6 DEVELOPMENT ENVIRONMENT

This chapter describes how you can develop your own

STB5660 application, what environment you need. What

hardware and software interface the system provides.

It answers the question what you need to start developing

your application. In addition it will tell you what you will

receive with the system that gets you on your way and

shorten development time and reduce the costs involved.

6.1 Summary of the STB5660 kit

When you receive the STB5660 development system it will

offer you a complete Set-Top Box system with all needed

documentation for development. This will give you a ‘plug

and play’ solution to test and develop a system based on

this platform.

6.1.1 THE HARDWARE

This consists off a satellite front-end board, a front panel

with the display and IR-receiver, a main board, smart card

unit, the remote control and all cables needed to make the

necessary connections. On the main board you will find a

programmed EPROM and Flash memory.

6.1.2 THE SOFTWARE

You will receive not only the binary executable, but also all

source codes in C, header files and documentation files.

The software will include the complete Application

Programmers Interface (API) for all components on the

board, except for IEEE 1394, which will be a subset of the

standard. This API will offer a developers logical services

like audio, video, graphics, descrambling, etc. Together

with this you will get the Feature Demonstration

Application (FDS). This is an application that will show you

the key features of the system.

6.1.3 DOCUMENTATION

Here you will find the user manual and programmers

reference for all major parts of the system like the

SAA7215 (AVGD chip), the SAA7214 (MPEG2

descrambler demultiplexer chip), and the satellite

front-end module (OM5718).

6.1.4 TEST REPORTS

These are included to prove the system maturity. You will

see the reports of the API tests and the reports concerning

the extensive In-System-Test. The latter is done to prove

the chip-set in a complete system environment, a

customer like set-up, customer use based on our

experience with previous end-customers.

6.2 How to get started

The first day you receive the system you can hook up a

satellite dish or transport stream (DiSEqC or not), a TV,

connect power to the system and it will start with the FDS

program. This demo gives you a menu driven interface to

the system. You can test and experiment with all main

features of the system. See how fast the On-Screen

Display functions, try out the IEEE 1394 interface to a

similar board, look at window tests, try out teletext, etc.

This will give you an understanding of the system and its

possibilities.

6.3 Hardware interface with the STB5660

Besides the dish and the TV (SCART, SVHS, CCIR 656

YUV) there is an interface to IEEE 1394, SPDIF

(multi-channel audio decoder, to a PC via RS232 and

IEEE 1284 (Centronics), a debug socket (ROM emulator,

I/O), JTAG connector (boundary scan testing), smart-card

unit and a remote control.

To use a ROM emulator there is an I/O connector on the

main PCB where an extension board fits on the debug

connector. This extension gives you access to two

footprints for 1-Mbyte ROMs.

6.4 Software interface with the STB5660

In the following way you can interface to the system to

develop and debug your own application. Connect a PC

(or other development system) with a ROM emulator to

extension board on the debug connector, compile the

supplied source code and load the executable in the ROM

emulator. Connect the RS232 debug port to the PC and

run a terminal program, this will give you a debug screen.

If you don’t have a ROM emulator you can use the parallel

port (IEEE 1284) of the Set-Top Box. There is a loader

program embedded in the EPROM of the system which

allows development without ROM emulator.

The maximum possible memory configuration consists of

a boot ROM (256 kbytes) with the loader program,

2 Mbytes fast DRAM as scratch memory, 32 kbytes NVM

for channel data storage, 4 Mbytes Flash memory to store

the program and 4 Mbytes SDRAM video memory.

The boot Chip Select can be switched between boot ROM

and Flash memory. Of course a smaller configuration is

possible, just leave the memory footprints open.

1999 May 05

16

Share Link: