handheld1 - University of Washington

Download Report

Transcript handheld1 - University of Washington

Handheld User Interface
Unit for
Saliva Analysis Device
University of Washington
EE400/590
Brigette Huang
Agenda







Function Specifications
User Interface logic flow diagram
Hardware Specifications
Software Development Environment
I2C bus
To be determined…
To do list
EE590 - Winter 2004
2
What does UI stand in the project?
Sample
DSP
ref lection
Light
0
1
2
Light
source
LED
3
4
Imager
a1
Vcc1
a2
b2
a3
a4
b1
b3
GND
0
b4
5
UI
Display
6
7
8
Storage
FPGA
Controlmodule
EE590 - Winter 2004
3
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
4
Program Idle
Analy sis result
comeback
User Interface diagram
Analy ze
Display
Failure
message
No
If process
complete?
Y es
Is Saliv a in
place?
No
Error: No Saliv a
Success
message,
display
analy sis
result
Y es
Does user
want to
pursue?
No
Error:
Resume process
Imagedestroy ed
No
Do y ou want to
sav eimage?
Y es
Y es
Def ault ID:
Name:
DOB:
Others:
User data input
f orm:
Sav eimage
Does required
data f illed in?
Error:
Datav alidationf ail
No
OpenImage
Y es
Processed
CloseImage
No
If the process
reach time out
y et?
Y es
Error:
Datav alidationf ail
SMDK Development Board
EE590 - Winter 2004
6
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
EE590 - Winter 2004
7
LCD display overview

















Mode
Application
Number of Pixels
Active Area(mm)
Pixel Pitch(mm)
Number of Colors
Contrast Ratio (typ.)
Brightness(cd/m2)
Response Time (ms at 25°C)
Interface
Supply Voltage(V)
Outline Dimension
Reflectance(%)
Power(mW)
Light Source
Weight(g)
Production
Transflective
PDA, Game
240 x 320
53.64 x 71.52
0.2235 x 0.2235
262K
8 (BL off), 60 (BL on)
50
40
6 bit RGB
3.3
63.3 x 85.6 x 4.8 TSP included
8
Panel 30 / BL 300
LED BACK LIGHT
52
Mass Production
EE590 - Winter 2004
8
Software

WindowsCE.net 4.2
32-bit, real-time multitasking OS
 Highly componentized
 Scalable
 Wide variety of CPU support


X86, ARM, MIPS, SHX
EE590 - Winter 2004
9
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.
EE590 - Winter 2004
10
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.
EE590 - Winter 2004
11
2
IC


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
12
2
IC
Bus
EE590 - Winter 2004
13
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
14
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
15