1. 1 New method of video transfer and control functions for training in computer classroom and for audiovisual applications WP4: User Interface SCREENS – Tallin, 15 june 2006 EU CRAFT PROJECT 016357

2. 2 SCREENS – Tallin, 15 june 2006 Decisions Solution A * as originally described: ARM9 + Linux * several serial ports available * USB host port available * internal LCD controller Solution B: * BlackFin + uClinux * low cost versions have one serial port only * LCD may be driven with little glue logic * lower BOM * smaller physical size As agreed at the 3rd meeting in Braunschweig, march 16th 2006 (cfr. 3 rd meeting minutes, 4.4 - WP4 progress)

3. 3 SCREENS – Tallin, 15 june 2006 BF533 CS x 4 User Interface block diagram FLASH 32 Mbit ABCDEFGHIJKLMNOP Abcdefghijklmnopq 01234567890 buzzer RS485 PLD SDRAM 64Mbit Memory bus LCD bias PLD matrix KBD TIMER Parallel Peripheral Interface External Memory Interface DISPLAY UART line 12 VDC in 5 VDC To LCD 3.3 VDC FET 3.3 VDC Vcore Expansion connector LEDs on keyboard

4. 4 SCREENS – Tallin, 15 june 2006 BF533 Architectural details, 1 PLD matrix KBD TIMER Parallel Peripheral Interface LEDs on keyboard MATRIX KEYBOARD CONTROLLER Whenever a keypress is detected, the PLD automatically generates a PPI access to the processor Separate pins from the memory bus Programmable speed directly from processor scanning is zero-overhead Clock source: internal timer/counter of the processor 8-bit data: 5-bit column (single-bit), 3-bit row (encoded) 32 keys are scanned, hw provisions for key debounce 4 LEDs are controlled via programmable flags (ALL, GRP A, GRP B, DATAPROJECTOR) 8 4 ROWS COLUMNS 1 bit active at time ROWS COLUMNS

5. 5 SCREENS – Tallin, 15 june 2006 Keyboard layout Updated keyboard layout and LED arrangement Cfr.: D1b: User Interface Specification, ver. 0.5 (05/05/2006)

6. 6 SCREENS – Tallin, 15 june 2006 BF533 CS x 4 Architectural details, 2 FLASH 32 Mbit ABCDEFGHIJKLMNOP Abcdefghijklmnopq 01234567890 PLD SDRAM 64Mbit Memory bus LCD bias External Memory Interface DISPLAY MEMORY MAPPING Due to limited address range of processor chip select lines, a simple PLD is required to allow access to all memory-mapped resources. NOR FLASH: it contains bootloader and executable code in binary form SDRAM: code is executed from here, at 133 MHz LCD: 8-bit memory-mapped peripheral (two locations: control and data) boot process: bootloader initializes SDRAM controller and copies data from FLASH into SDRAM

7. 7 SCREENS – Tallin, 15 june 2006 BF533 Architectural details, 3 buzzer RS485 UART line Expansion connector SERIAL PORT The processor has a single UART, dedicated to the RS-485 interface along with a direction pin. EXPANSION CONNECTOR It contains the SPI port, for future expansion.

8. 8 SCREENS – Tallin, 15 june 2006 SCREENS SW Emulator Windows-based software emulator of actions on User Interface, based on the D1b: User Interface Specification, ver. 0.3 (11/01/2006) D1b: User Interface Specification, ver. 0.5 (05/05/2006)

9. 9 SCREENS – Tallin, 15 june 2006 uClinux on Blackfin, 1 Recent trend: convergence of media processors and embedded operating systems Blackfin is a mixed architecture (DSP with RISC- and microcontroller-like extensions): MicroSignal Architecture (MSA) developed by Analog Devices and Intel uClinux is an operating system that is derived from the Linux kernel * intended for microcontrollers without Memory Management Units (MMU’s) * available on many processor architectures, including the Blackfin processor http://blackfin.uclinux.org Official repository, supported by Analog Devices

10. 10 SCREENS – Tallin, 15 june 2006 uClinux on Blackfin, 2 Differences between Linux and uClinux 1. No real memory protection (a faulty process can bring the complete system down) 2. No fork system call 3. Only simple memory allocation 4. Some other minor differences Which is the advantage for SCREENS in using uClinux on Blackfin? * Low processor cost * Native Unicode handling * Availability of a file system * Easy retargetting on other platforms

11. 11 SCREENS – Tallin, 15 june 2006 Software development, 1 STEP 1 two applications on PC GUI (TCP socket client) core application (TCP socket server) screens_emulator.exe TCP socket server TCP socket client keystrokes LCD bitmap Configuration files

12. 12 SCREENS – Tallin, 15 june 2006 Software development, 2 STEP 2 one applications on PC GUI (TCP socket client) One application running on STAMP (BF533 board) core application (TCP socket server) with configuration files Communication thru LAN screens_ctrl TCP socket server TCP socket client keystrokes LCD bitmap Configuration files GUI on host

13. 13 SCREENS – Tallin, 15 june 2006 Software development, 3 STEP 3 Applications running on target board core application with configuration files keyboard management RS-485 protocol LCD driver character generation  All look-and-feel issues are solved BEFORE implementation on target (consortium agreement on current version is required before proceeding with implementation on target)  the main application, based on configuration files, is already developed and debugged BEFORE implementation on target  The activites which must be scheduled on physical hardware are: Keyboard management, with debounce logicRequires User Interface board RS485 protocol - validation phase of development Requires Video Switch unit(s) LCD driverRequires User Interface board

14. 14 SCREENS – Tallin, 15 june 2006 HW development Status -HW specifications: completed -Components selection: completed -Schematics: completed. -PCB Layout: ready to start -PCB specs: -4 layers, FR4, Dielectric constant Er 4.3.. 4.5 -Gold or Silver finish -> RoHs and planarity -different solutions could be proposed by electro-Hill -6 mils minimum trace -6 mils clearance. -minimum via – DIA 0.5mm hole 0.3mm. -All vias filled with solder resist.

15. 15 SCREENS – Tallin, 15 june 2006 HW development Next step -Agreement on schematics -Agreement on Bill of material -Start PCB Layout. -Prototypes (PCB, components procurement and assembly) fabrication: -by electro hill -to reduce final project cost -Production tuning now and not at the end of the PRJ -Only one step for production. -NRE only one time -CRR receive 2 assembled prototypes. -Start of debug and test

16. 16 SCREENS – Tallin, 15 june 2006 Status SW Emulator: completed (except bugfixes), waiting for consortium agreeement Schematics: completed Layout: starts now (once approved) Software: in progress Bet version of firmware will be available 1 man-month after receiving a prototype

17. 17 SCREENS – Tallin, 15 june 2006 THANK YOU