1. Handheld User Interface Unit for Saliva Analysis Device
University of Washington
EE400/590
Brigette Huang

2. Agenda Function Specifications User Interface logic flow diagram
Hardware Specifications
Software Development Environment
I2C bus
To be determined…
To do list
EE590 - Winter 2004

3. What does UI stand in the project?
EE590 - Winter 2004

4. Function Specifications
The UI unit is intended to accept any necessary information and command to operate the saliva sample analysis. To complete the whole system, the UI unit is required to have 4 essential elements:
An application to interact with users.
A communication protocol established to transmit control signal and data between the UI unit and the analysis module.
A LCD display panel with touch pad capability that meets the hardware requirement to output results and allow user to select commands.
Data storage to store the analysis results and image data.
The system will designed so as not to preclude the incorporation of an option of direct data synchronization with main server in future.
EE590 - Winter 2004

5. User Interface diagram

6. SMDK Development Board
EE590 - Winter 2004

7. Microporcessor Overview
S3C2410X01 microprocessor
Designed for handheld and general applications
Cost-effective (mass production)
Low power (power mode)
Relative high performance (max 200Mhz)
Easy to adapt (shorten time to market)
Complete set of common system peripherals (SOC)
External memory controller
LCD controller, Touch screen interface
DMAs, UARTs, SPIs, USBs, I2C, I2S controller
PWM timers, Watch dog timers, on chip clock generator with PLL, RTC with calendar function
ADC, 117b I/O pins
1.8v internal, 3.3V external I/O
SD/MMC interface
1.8V internal, 1.8V/2.5V/3.3V memory, 3.3V external I/O microprocessor with 16KB I-Cache, 16KB D-Cache, and MMU. External memory controller. (SDRAM Control, Chip Select logic)
LCD controller (up to 4K color STN and 64K color TFT) with 1-ch LCD-dedicated DMA. 4-ch DMAs with external request pins
3-ch UART with handshake(IrDA1.0, 16-byte FIFO) / 1-ch SPI 1-ch multi-master IIC-BUS/1-ch IIS-BUS controller
SD Host interface version 1.0 & Multi-Media Card Protocol version 2.11 compatible 2-port USB Host /1- port USB Device(ver 1.1)
4-ch PWM timers & 1-ch internal timer Watch Dog Timer 117-bit general purpose I/O ports / 24-ch external interrupt source Power control: Normal, Slow, Idle, Stop and Power-off mode 8-ch 10-bit ADC and Touch screen interface. RTC with calendar function. On-chip clock generator with PLL
EE590 - Winter 2004

8. LCD display overview Mode Transflective Application PDA, Game
Number of Pixels 240 x 320
Active Area(mm) x 71.52
Pixel Pitch(mm) x
Number of Colors 262K
Contrast Ratio (typ.) 8 (BL off), 60 (BL on)
Brightness(cd/m2) 50
Response Time (ms at 25°C) 40
Interface 6 bit RGB
Supply Voltage(V) 3.3
Outline Dimension x 85.6 x 4.8 TSP included
Reflectance(%) 8
Power(mW) Panel 30 / BL 300
Light Source LED BACK LIGHT
Weight(g) 52
Production Mass Production
262K because 6bit RGB
EE590 - Winter 2004

9. Software WindowsCE.net 4.2 32-bit, real-time multitasking OS
Highly componentized
Scalable
Wide variety of CPU support
X86, ARM, MIPS, SHX
Real time – Hard real time kernel With 256 priority levels and nested interrupt support, Windows CE .NET 4.2 meets demanding, deterministic performance requirements for a variety of device types and uses hard real-time response requirements as well as ultra-low bounded Interrupt Service Routine (ISR) and Interrupt Service Thread (IST) latency (average ISR latency of 2.8 microseconds and average IST latency of 17.9 microseconds on a Pentium 166 MHz processor).
Componentized - Continuing the effort to minimize the operating system footprint for embedded devices, Windows CE .NET provides granular kernel componentization. Windows CE .NET supports a minimum configuration platform that is as small as 200 kilobytes (KB) with minimum kernel functions only.
Scalable - Windows CE .NET allows developers the freedom to connect smart devices flexibly and more securely by choosing from a broad range of advanced technologies that offer richly differentiated experiences.
Scalable wireless technologies
Rich multimedia Rich multimedia
Latest Web-browsing technologies
Extensive multi-language support
Applications and services
EE590 - Winter 2004

10. Why people choose WinCE
Productivity
Great development tools: Platform Builder
Faster design start with pre-configured device designs
Shorter build-debug-deploy cycle with
Common IDE – PB is based on Visual Studio 6.0
Dedugging tools – emulator, kernel tracker, kernel profiler…
Rich documentation and well established support channels.
Quality & Value
Testing Suite and Logo Test – quality assurance
3 dollars per run-time license on certain volume.
Pre-configured device design - digital media receiver, enterprise terminal, web pad, gatway, industrial controller, internet appliance, IP phone, mobile handheld, mobile phone, set-top box, tiny kernel, thin client.
Common IDE – Platform builder IDE is based on Visual Studio 6.0 you will find the most smooth transition experience.
EE590 - Winter 2004

11. Why Windows CE.NET?
A proven, robust, and extensible operating system that can be utilized across multiple projects and device versions.
Powerful development tools and integrated, fully tested technology, which enable the OEM to capitalize on existing expertise and focus on product differentiation and adding value to its design.
A fast and predictable time to market.
Consistency, availability, and supportability of the embedded operating system over the device life cycle.
At the end of the day – oem wants an operating system that delivers
a great solution and value
at a fair price
from a reputable vendor
who will be there to support them throughout the device life cycle.
(print the page out on why windows CE.NET)
EE590 - Winter 2004

12. I2C bus
Philips developed a simple bi-directional 2-wire, serial data (SDA) and serial clock (SCL) bus for inter-IC control
Each device is recognized by a unique address and can operate as either a receiver-only device (e.g. an LCD driver) or to both receive and send information (such as memory). Transmitters and/or receivers can operate in either master or slave mode, depending on whether the chip has to initiate a data transfer or is only addressed. I²C is a multi-master bus, i.e. it can be controlled by more than one IC connected to it.
EE590 - Winter 2004

13. I2C Bus
EE590 - Winter 2004

14. To be determined How many modules UI will be talking with??
Is the module UI send command to start the test the same module that will later transmit the data back
Protocols for communications between UI and the units mention above.
EE590 - Winter 2004

15. To Do List Clarify the items in to-be determined list.
Modeling the UI application using Esterel.
Build a platform for the development board.
Driver planning and implementation – LCD, SD, I2C, Touch pad.
User Interface application planning and implementation.
EE590 - Winter 2004