1 / 18

Embedded software within Upmarket TV

Embedded software within Upmarket TV. Guy Van Hooveld Based on a presentation by Rob Van Ommering. Contact persons. Guy Van Hooveld - Software development manager Brugge Aad Van Zanten - Technology manager Brugge Erwin Raeds - ASD manager Brugge Hans Aerts - Overall project manager E’ven.

shelby
Download Presentation

Embedded software within Upmarket TV

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Embedded software within Upmarket TV Guy Van Hooveld Based on a presentation by Rob Van Ommering

  2. Contact persons • Guy Van Hooveld - Software development manager Brugge • Aad Van Zanten - Technology manager Brugge • Erwin Raeds - ASD manager Brugge • Hans Aerts - Overall project manager E’ven

  3. Build a Variety of CE Video Products TV/VCR UTV DTV Basic TV MG-R Products Flat TV VCR ‘Potential’ MG-R Products Projection TV LCD Projection Dimensions of variation Price Region Broadcasting Standard DVD Video Output Device Storage Device Chip Technology Sound Features

  4. Upmarket TV • High-end TV application • large number of products (types) • growing regional diversity • dependency on local (regional) situation (signals, providers…) • several ranges to be covered by reuse • Technology • 16 bits microprocessor architecture (today) • RTOS • embedded software • C programming language - coding rules - QA-C • many key components to implement the functionality (today) • reuse necessary • component based technology introduced • ROM size 128K -> 4MB (doubling every 18 months) • debugging host vs target / simulator vs ICE • cost driven

  5. Organization • Multisite development • 70 people in Brugge • specification • technology management • TV-platform • integration projects • end responsibility • 15 people in E’ven • subsystem development • architectures • 80 people in Bangalore • subsystem development • Several types of projects • small - 5 manyears • medium - 15 manyears • large - 100 manyears • Profiles Majority Ing. + Ir. + Grad.

  6. Process and methodology • CMM standard used (level 2 KPAs - see hereunder) • Requirements management • Internal tool used (formal description language) • evolution to use cases and UML investigated • Configuration management • Continuus package is being used • New challenges related to subsystem oriented development and distributed multisite development • Subcontract management • Planning and tracking • Quality assurance • Other levels KPAs partially addressed if applicable

  7. Solution: Use Components Rom Rom Rom Rom Parts List Direct 100 Hz Flat Tuner Wide Video Source Select Teletext Projection EPG Tuner Dolby Audio Components

  8. CE Distributes Software Development Eindhoven Brugge Hamburg Briarcliff Southampton Wien Sunnyvale Knoxville Bangalore Singapore Involved now To be involved

  9. Solution: Use Subsystems Products (configurations) Subsystems or Standard designs (deployment) Basic components (assembly) Advantages: • Hide low-level assembly complexity from product creators • Concentrate domain knowledge (TV, Txt, UI) in capability centres Is a subsystem a component? Yes and no (see later)!

  10. Overall View MG Re-engineering CE Common Platform Architecture Architecture Projects Subsystem Projects Projects Products Product Execution Projects Subsystems Architecture & Design Implementation & Test Evolution & Integration Common software architecture, coding conventions, tools, ... Reusable standard designs, to be used in various products Commercial products, created from subsystems

  11. ‘Layered’ Architecture • Application software • need UI peope •  added value here! • OS Software • need OS people •  buy in P abstraction P API Applications A/V abstraction Computing platform (OS) A/V API A/V & data platform • Signal processing software • HW/SW guys and girls •  Semiconductors (general purpose) computing hardware uP hardware A/V hardware Signal processing hardware

  12. Comparing Layered Architectures GFL G+4 Control Applications System Services Resources General Mechanisms A/V Comp. Log. Dev. drivers Phys. Dev. ‘Development’ hierarchy Calling hierarchy Applications Applications A/V drivers OS OS A/V drivers Applications Computing platform (OS) A/V & data platform

  13. Actual Subsystems The following subsystems are currently defined within MG-R : Computing Platform API Computing Platform &Development Environment Applications & Services UI98Applications apps VBArtist vbart AnalogEPG epg TvServices tvsvc Factory fact DealerService deal SDE sde A/V Platform API UIMS uims TeletextLvl25 txplf TvPlatform tvplf ATSC atsc InfraStructure infra A/V and Data Platform

  14. Subsystem and Product Projects MG-R Products (1) PL: X Status: X MG-R Products (2) PL: X Status: X XXX PL: X XXX PL: X XXX PL: X XXX PL: X Cluster8 Arch: X Cluster9 Arch: X Cluster 2b/6 Arch: X EMG Arch: X Cluster 1/2a Arch: X Cluster 4 Arch: X Cluster 5 Arch: X Product projects create one (or more) product Subsystem projects create one or more subsystem: MG-R Subsystems PL: X Status: Running Arch: X X XXX PL: X XXX PL: X XXX PL: X XXX PL: X InfraStructure Arch: X TV Services Arch: X UIMS Arch: X ATSC Arch: X TV Platform Arch: X Dealer/Service Arch: X UI98 Applications Arch: X SDE Arch: X XXX PL: X Status: X XXX PL: X Status: X XXX PL: X Status: X Teletext Lvl2.5 Arch: X Analog EPG Arch: X Factory Arch: X

  15. Subsystem and Product Roadmap 22 26 32 36 46 52 2 4 6 8 22 14 16 18 20 24 28 30 34 38 40 42 44 48 50 10 12 14 16 18 20 arch R0.1 IROM R1.0 IROM TR R2.0 R2.1 IROM CR AV-Link Flash infra R1.0 R2.0 ‘Chinese’ characters uims R0.1 R0.2 R0.3 R0.4 R1.0 R2.0 R2.1 R2.2 EDRIC FDW HC50.x MCS Eur & Eco HW AP HW tvplf R0.1 atsc R0.1 R0.2 R1.0 R2.0 R2.1 FDW Eur, HC 50.3 AP tvsvc R1.0 R2.0 R2.1 Eur AP deal R0.1 R0.2 R1.0 R2.0 R2.1 Eur AP fact R0.1 R0.2 R1.0 R2.0 R2.1 FDW Eur, HC 50.3 AP apps R1.0 R2.0 Now/Next EPG Full EPG epg R0.1 R1.0 R2.0 infra uims tvplf (A) tvplf(A+D) tvsvc apps Txt Lvl 2.5 Chinese TXT txplf Gemstar/CC Fact/Deal/Svc FDW Functional Tests Alpha Tests cl8 tvplf, milo tvsvc, apps, CC, GS Fact/Deal/Svc Functional Tests Alpha Tests cl9 Functional Tests Alpha Tests EMG Functional Tests Alpha Tests cl4 Functional Tests Alpha Tests cl1/2a Functional Tests Alpha Tests cl2b/6 Functional Tests cl5 Product and subsystem releases are carefully planned:

  16. Solutions Our Solution: • mirror the hardware composition • communicate through software signals Advantage: • creating a new chassis is nothing more than wiring the components power src tuner video ssl dec video featuring video output dest sound Traditional Solution: • managers that control certain aspects Disadvantage: • most of the code resides in managers • these managers are very chassis specific! system control tuning program selection power video audio tun hip msp picnic topic hop

  17. Koala - Example

  18. Conclusions - challenges • CMM and process improvement • continuous process to change the culture and the way of working • multi-site development • new subsystem/integration approach • consequences at configuration management level • consequences at requirements management level • managing technology change in a fast changing environment • new models/component development have to be proven (reuse…) • defects prevention to improve product quality

More Related