Windows CE .NET Development Environmentmesl.khu.ac.kr/lecture/doc/esl2/closed.pxa255/esl2-08... · 2016-09-10 · Embedded Visual C++ 4.0 MS 에서제공하는Windows CE .NET 용소프트웨어를개발하는프로그램

Embedded System Lab. II

Windows CE .NET Windows CE .NET

Development EnvironmentDevelopment Environment

경희대학교 컴퓨터공학과

조진성

Embedded System Lab. II 2

목차

� Overview of Windows CE .NET

� Serial Number 받기

� Platform builder .NET 4.2 설치

� Microsoft Embedded C++ 4.0설치

� JFlashMM설치

� EBOOT download

� Handheld device만들기

� Application 개발


Overview of Windows CE .NETOverview of Windows CE .NET


Overview of Windows CE .NET

� Windows CE .NET: Design Goals

� What is New in Windows CE .NET?

� Basic Configurations

� Target Hardware Support


Windows CE .NET: Design Goals

� Modular and compact operating system

� Highly modular

� Customized to meet to the specific product requirements of a range of

devices

� Only the required modules can be included in the operating system image

� Wireless and wired connectivity

� Allows you to build scalable wireless platform

� Flexibly connect mobile devices into existing infrastructures

� Provide broad wireless support for PAN(Personal Area Network)s, LANs, and

WANs

� Including Bluetooth, Wireless LAN – Zero Configuration(802.11) Support

� PAN : Bluetooh나 IrDA(적외선)이용한근거리개인네트웍


Windows CE .NET: Design Goals

� Robust real-time capabilities

� Hard RTOS kernel support

� Efficiently enabling the most demanding real-time embedded designs

� Rich multimedia and multilingual support

� Provide the latest multimedia experiences

� Allow you to efficiently build localized embedded devices

� Strong development tool support


What Is New in Windows CE .NET?

� Internet Explorer 5.5 for CE

� Wireless support

� Multimedia

� Customizable UI

� Security Services

� Real-time collaboration and communication

� Better multi-language support

� ClearType


Basic Configurations 이란?

� There are 13 different starting points to develop your platform

� Each one targets a particular class of device

� To reduce product development

� Once a basic configuration has been chosen, you may modify it to suit

your specific needs


Basic Configurations

� PDA or mobile handheld device

� Variants with or without applications, such as WordPad

� Cell phone/smart phone

� 160x220 nominal display resolution

� Web Pad

� Touch-screen user interface and 640x480 or larger display

� Internet appliance

� Non-mobile, Browser-based device with a fixed (CRT or LCD) display and a

keyboard.

� Internet Appliance with Browser

� Consumer Internet Appliance with mouse-based UI and 640x480 or larger display

� Internet Appliance with Browser and Applications


Basic Configurations (continued)

� Media appliance

� Playback or store music, video, and other electronic media

� Digital Audio Receiver/Jukebox

� Networked device that stores, decodes, and plays Windows Media Audio and MP3

music files

� Digital Audio Receiver

� Without local storage

� Portable Audio Player with Wireless Networking

� Portable DVD Player

� Electronic Picture Frame

� Retrieve and display picture from the internet or a home network

� Digital imaging device

� Camera, projector, and printer



� Set-top box

� Connects to a TV for display of Internet / media content

� Residential gateway

� Connects to the Internet and shares that connection with a wired or wireless

home network

� Industrial automation device

� Human Machine Interface (HMI) or Programmable Logic Controller (PLC)

variants

� Retail Point-of-Sale device

� Self-service kiosks, electronic payment terminals, POS terminals

� Windows thin client

� Minimal remote access terminal with constrained shell and RDP



� Tiny Kernel

� Smallest functional Windows CE image

� Starting point for the most compact, headless devices

� Custom Device

� The most fully customizable configuration

� Allows you to choose from all operating system features

� Also a variant for devices without displays


Target Hardware Support

GEODE

CEPC

KEYWEST

ASPEN

DDB5476

EAGLE

TBD

ARMINTEGRATOR

SA11X0BD

BSP Name

National Geode Reference

Platform

NS Geode

CEPCP5/P4/PIII/PII/

CelK6x/Athlon

x86

Hitachi SH3

Keywest SDB

SH3-7729

Hitachi SH4

Aspen SDB

SH4-7750SHx

NEC DDB-Vrc5476

Boston SDB

NEC Vr5432

NEC DDB-Vr4122

Eagle SDB

NEC Vr4122MIPS

Intel Lubbock SDBIntel Xscale

ARM1020

ARM Integrator

AP SDB

ARM920

Intel SA111x

Assabet SDB

Intel SA1110ARM

SDBCPUProcessor Family


Core Operating System Architecture

Hardware

OAL

Device Drivers

GWES

Kernel

Filesys

Applications

Programming Interfaces(Win32, COM, MFC, ATL)

Communications interfaces (Winsock, RAS, TAPI)

Networkingand

CommunicationsSystem

DeviceManager


The OEM Adaptation Layer

� Layer between the Kernel and the hardware

� Set of functions related to system startup, interrupt handling, power mana

gement, profiling, timer, and clock

� Included in BSPs for supported SDBs

� Coded by OEMs to adapt windows CE to their own custom platforms

� Linked with code provided by Microsoft to build the Kernel


The Kernel Module

� Portable across supported processors

� Kernel is portable as most of the operating system is written in C

� NK.EXE, COREDLL.DLL

� NK.EXE contains Kernel code and Coredll.dll is the operating system core DLL module

� Saving system resources

� CE loader is designed to save system resources by loading application pages as and w

hen needed and by keeping only one physical copy of a DLL

� Demand paging

� Loads virtual memory pages into physical memory when needed

� Multiple execute in place regions

� Allows applications to execute code directly from read-only memory


Device Driver System

� Device driver

� Links an operating system and a device

� Built-in Drivers vs. Installable Drivers

� Built-in drivers are installed by the platform manufacturer

� Installable drivers are third-party peripheral devices that end users can connect to a Windows CE-based platform

� Native Drivers vs. Stream Drivers

� All of the device drivers managed by GWES are native device drivers

� Device manager loads stream interface drivers when the system boots, if those drivers are listed in the registry

� Monolithic Drivers vs. Layered Drivers

� Monolithic drivers implement interface directly in terms of actions on the device they control

� Layered drivers separate the implementation into two layers


The GWES Module

� Graphics, Windowing, and Event Subsystem

� Graphic output: display and printer

� User input: keyboard, stylus, and mouse

� Window management: message routing

� Graphic Device Interface (GDI)

� Is the drawing subsystem of GWES

� Controls how text and graphics are displayed

� Uses a device context to store drawing attributes for a specified device


The Filesys Module

� The Filesys Module

� Implements the object store

� File systems

� Registry

� Property Database

� Substitutes for a hard drive on an embedded drive

� Resides in ROM, RAM, or both

� Can have a maximum size of 256 MB


The Filesys Module (continued)

� Storage manager

� Is responsible for all external storage items, including all the file systems and block drivers

� Installable file systems

� Can provide access to a floppy diskette, a hard drive, a flash file system on a PC Card, or to other external storage devices

� File-shadowing mechanism

� Allows a file to be stored both in RAM and ROM.

� Differences from other Windows file systems

� No letters assigned to file systems

� No concept of current directory

� No support for overlapped I/O

� All files stored in RAM are automatically compressed


The Filesys Module (continued)

� Registry

� Provides a common repository for system settings, application data, and user preferences

� Resides in RAM, if not present in RAM, the registry can be reloaded from persistent storage or rebuilt from ROM

� Registry functions specific to Windows CE

� Property Database

� Provides a lightweight database management system

� Accessible using a new set of Win32 API functions specific to Windows CE

� Data stored in a flat model

� Accessible to ActiveX Data Objects for Windows CE (ADOCE)

� Supports multiple volumes on installable file systems


Real Time Operating System

� Bounded interrupt response latency

� Timer precision configurable (1 millisecond default)

� System timer tick independent of thread quantum

� Nested interrupt support

� Priority inheritance

� Protected virtual memory

� Synchronization objects


Power Management Features

� Power management features respond to system calls for turning the

system off or for idling

� Device level power states, DO-D4

� D0 – Full on: Full power with full functionality

� D1 – Low On: Slightly reduced functionality, lower power and/or performance

� D2 – Standby: Partial power with automatic wake

� D3 – Sleep: Partial power with device initiated wake

� D4 – Off: Power off

� The only device power state that all devices must support is D0, full on


Advanced Features of Windows

CE .NET

� Networking and Communications

� Real-Time Communication

� Multimedia

� Security

� Internationalization


Get the Serial NumberGet the Serial Number


Serial Number 받기

� [https://www.interactservices.com/WinEmRegistration/ProdRegister.asp]

� Product : Windows CE .NET 4.2

� Platform builder와 embedded C++에서사용할 Serial Number를구한다.

� Platform builder는 120일의 evaluation version.

� Embedded C++은 freeware.

� E-mail을통해 serial number가발송된다.


[Windows CE .NET 4.2]

을선택한다.


Platform builder .NET 4.2 Platform builder .NET 4.2 설치설치


Platform builder .NET 4.2

� MS Windows CE .Net 플랫폼을개발하는프로그램이다.

� Visual studio같은통합개발환경을제공한다.

� Windows CE .NET플랫폼을디자인, 작성, 빌드, 테스트및디버깅하는데필요한모든개발도구가포함되어있다.

� 상용프로그램이고 120일 Evaluation version은 MS사에서무료로받을수있다.


� 임베디드시스템의 custom Windows CE의 OS개발툴

� 개발과정

� Basic platform building

� Customize Platform

� Download to target device

Platform Builder

Customize Platform

Configure PlatformConfigure Platform

Develop device

drivers

Create or add

custom components

Modify source code

configuration files

Debug

Platform

Debug

PlatformBuild

OS image

Build

OS image

Configure PlatformConfigure Platform

Export SDKExport SDK

Develop OAL

board support package

and bootloader

Develop OAL

board support package

and bootloader

Platform complete?

Custom target device?

No

Yes

No

Yes


Platform builder 설치

� CD를넣으면위와같은창이뜬다.

� Install을선택한다.


� [I accept the terms in the license agreement]를선택.

� [Next]를선택.


� Product key를입력하고 [Next]를선택한다.

� Product key는 evaluation version이고, MS 홈페이지에서얻을수있다.


� Custom을선택후, [Next]를클릭한다.


� 원하는폴더를지정후 [Next]선택


� [ARMV4], [ARMV4I], [XSCALE]은반드시설치하여야한다.

� [Shared Source for windows CE .NET 4.2]는커널소스이다.

� 굳이포함시킬필요는없다.


� 설치가진행되는과정이다.


� 설치가완료되었다.

� [Finish]버튼을선택하여설치를종료한다.


� Platform builder가실행된모습이다.


PXA255PXA255--Pro3 Pro3 용용 BSP BSP 설치설치


BSP

� Board support package의약자이다.

� 제공된 CD를통해설치한다.

� [BSP설치방법.txt] 파일을참조해서설치할수있다.

� 1. CD의 BSP디렉토리의 PXA255PRO3디렉토리를 COPY하여,

C:\WINCE420\PLATFORM 디렉토리에 PASTE한다.

� 이때, CD의내용대신, 강의홈페이지의 PXA255PRO3_BSP.zip의내용을/Platform/PXA255Pro3 folder로복사한다.

� 2. 제공된 .msi파일을더블클릭하여실행한다.

� 3. (주)휴인스에서제공한 BSP설치된것을확인한다. (Catalog window의 Third

party의 BSPs에서확인)


BSP설치

� BSP설치모습이다.

� [Next]를선택한다.


� 별다른설정없이 BSP설치가완료되었다.

� [Finish]를선택하여 BSP설치를종료한다.


MS Embedded C++ 4.0MS Embedded C++ 4.0설치설치


Embedded Visual C++ 4.0

� MS에서제공하는Windows CE .NET용소프트웨어를개발하는프로그램이다.

� Visual studio와같은통합개발환경을제공한다.

� 이프로그램자체가개발프로그램이므로 Visual studio없이개발할수있다.

� 무료개발프로그램이다.


Embedded C++ 설치

� Embedded C++ 설치시작모습이다.

� [Next]를선택하여다음으로진행한다.


� License 동의에관한화면이다.

� [I accept the agreement]를선택하고 [Next]를클릭한다.


� 이전에구한 serial number를입력하고 [Next]를선택한다.


� 설치할항목을선택하는화면이다.

� 이미모두선택되어있으므로, [Next]를선택한다.


� 설치할폴더를묻는화면이다.

� 적절한폴더를선택후, [Next]를클릭한다.


� 설치가시작되는화면이다.

� [Continue]를눌러계속진행한다.


� 설치할항목을다시묻고있다.

� [Continue]를선택한다.


� 설치가완료되었음을알려주는화면이다.

� [OK]를선택해설치를종료한다.


JFlashMMJFlashMM 설치설치


JFlashMM

� Intel에서제공하는 Rom Writer이다.

� JTAG 케이블을이용해보드에장착되어있는 Flash에Writing할수있는프로그램이다.

� Intel Website에서최신버전을 download받을수있다.


JFlashMM설치

� 제공된 CD

� 또는

� [http://developer.intel.com/design/pca/applicationsprocessors/swsup/jflas

hmm.htm]

� 를통해설치한다.


� License동의를묻는화면이다.

� [Yes]를선택한다.


� 설치할폴더를선택하는화면이다.

� 적절한폴더를지정후, [Next]를선택한다.


� 설치가완료되었음을나타내는화면이다.

� [Finish]를선택하여설치를종료한다.


GIVEIO driverGIVEIO driver설치설치


GIVEIO driver설치

� GIVEIO driver

� GIVEIO driver는 JFlashMM을사용하기위해설치해야한다.

� Parallel port와 IO를수행하기위해필요한 device driver이다.

� [C:\Program Files\Intel Corporation\JFlash_MM\GIVEIO.SYS]

� 파일을

� [C:\windows\system32\drivers]에복사한다.


� 제어판에서 [새하드웨어추가]를실행한다.

� 하드웨어추가마법사창에서 [다음]을클릭한다.


� [예, 하드웨어를이미연결했습니다]를선택한다.

� [다음]을선택한다.


� 제일하단에있는 [새하드웨어장치추가]를선택한다.



� [목록에서직접선택한하드웨어설치]를선택한다.



� [포트(COM및LPT)]를선택하고, [다음]을선택한다.


� [디스크있음]을선택한다.


� [giveio.inf]가있는파일경로를지정하고, [확인]을선택한다.

적절한폴더선택


� [giveio]가위와같이잡히는지확인한다.





� 하드웨어의호환성을묻고있다.

� [계속]을선택한다.


� [giveio] driver가정상적으로설치되었다.

� [마침]을선택한다.


� 잘설치되었는지장치관리자에서확인한다.


EbootEboot downloaddownload


EBOOT

� Ethernet Bootloader.

� MS Windows CE에서기본적으로제공하는 Bootloader이다.

� Eboot는보드에전원이들어가면

� CPU의 GPIO, 메모리컨트롤러, Interrupt controller, 클럭등을초기화한다.

� 그후, Ethernet controller를초기화하고

� TFTP를통해Windows CE OS이미지를받아온다.


JFlashMM console 선택


EBOOT download

� Program을선택하면 DOS창이뜬다.

� 여기서 [Jflashmm]을실행시킬수있다.


� 제공된 CD에있는

� [\Utilties\JFlash_MM\acumen.dat]파일과

� [\Image\EBOOT.nb0]파일을

� [C:\Program Files\Intel Corporation\JFlash_MM]에복사해넣는다.


� [Jflashmm]을실행시킨다.


� [Enter platform data file name :] 에 [acumen]을입력한다.

� 뒤의 [.dat]는입력하지않는다.


� [Enter Binary file name :]에 [EBOOT.nb0]를입력한다.


� Writing과 Verifying을거쳐 download가성공적으로완료되었다.


하이퍼터미널

� Eboot가정상적으로 download되었는지확인하기위해사용한다.

� [보조프로그램]->[통신]->[하이퍼터미널]


� 적당한이름을입력하고 [확인]을선택한다.


� 알맞은 COM port를선택하고 [확인]을선택한다.


� 위와같이설정을하고 [확인]을선택한다.

� board를 reset하면 boot loader가동작하는것을볼수있다.


� [enter]키를누르면 ethernet을통해새로운부트로더이미지를다운로드한다.

� [space]키를누르면 boot loader option을변경할수있다.

� Eboot가잘동작하는것을확인하였다.


Handheld DeviceHandheld Device만들기만들기


� [New Platform]을선택한다.


� New platform wizard 가나타나는데, [Next]를선택한다.


� BSP를설치했으므로 PXA255PRO3를선택한다.



� [Mobile Handheld] 선택후, Platform name을설정한다.



� 설정을그대로유지한채, [NEXT]버튼을클릭한다.


� 설정을그대로유지한채, [NEXT]버튼을클릭한다.


� 모든 [Notification acknowledged]에체크를한후, [NEXT]버튼을클릭한다.


� 모든설정이완료되었다.

� [Finish]버튼을클릭한다.


Active configuration변경

� Platform 에도 debug Mode와 Release Mode가있다.

� Debug Mode

� Kernel을 SDRAM에올린다.

� 이때, ethernet cable은항상연결되어있어야한다.

� Host에서 debugging message를볼수있다.

� Release Mode

� Kernel을 FLASH에올린다.

� Debugging정보를포함하지않으며, 속도가 debug모드보다는빠르다.

� Test중에는 Debug Mode로사용하기로한다.


Resolve Features

� 현재 platform에맞는 features를선택해야빌드가가능하다.

� [Device Driver]에서오른쪽버튼을누른다.

� [Resolve Features]를선택한다.

� 여기서 board에해당하는 device를선택해준다.

� Debug/Release Mode를각각설정해주어야한다.


� Audio : UCB1400 Waveform Audio device


� Display : XSC1BD LCD


� PCMCIA : SA11x1 PCMCIA


� Serial : XSC1BD Serial


� USB Function : XSC1BD USB Function( Serial interface )

� 모든설정을완료하고 [OK] 버튼은누른다.


Exclude power button

� Board에는 power button이존재하지않으므로 exclude시킨다.

� Board에달린 power button과위 power button은다르다.

� 이과정을수행하지않으면커널이제대로동작하지않는다.

� Debug/Release Mode 모두설정해야한다.


PXA255PRO3.bat 파일수정

� \platform\PXA255PRO3\PXA255PRO3.bat

� Kernel이정상적으로동작하기위해서는위파일을수정해야한다.

� 수정할부분은다음과같다.

� SET BSP_LAN91C111, BSP_NOUSBSER, BSP_NOUSB

� SET BSP_LAN91C111=

� SET BSP_NOUSBSER=1

� SET BSP_NOUSB=1

� 강의홈페이지의 PXA255PRO3_BSP.zip으로 BSP를설치한경우, 이미수정이되어있다.


Platform.reg

� \platform\pxa255pro3\files\platform.reg

� Scotg.dll부분을 IF문으로감싸준다.

� IF BSP_SCOTG

� [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TD242]

� …

� ENDIF

� 강의홈페이지의 PXA255PRO3_BSP.zip으로 BSP를설치한경우, 이미수정이되어있다.


Build kernel

� [Build]->[Build Platform]을선택한다.

� 시간이꽤걸리므로설정을정확히하고컴파일하는것이좋다. (약 10분소요)


� 컴파일이에러없이완료되었는지확인한다.


Configure remote connection

� [Target]->[Configure Remote Connection]을선택한다.

� Board에 download하는방식을설정한다.

� 이과정을수행해야만 board에 download할수있다.


� Download/Kernel을모두 Ethernet으로설정.

� [Configure]버튼을선택한다.


� Platform builder는그대로둔채,

� 하이퍼터미널을연결하고보드의전원을킨다.

� [space]키를통해 IP등을설정한다.


� IP/Subnet을설정후, [D]를통해 kernel을 download한다.


� BOOTME message가보내지는것을확인한다.


� BOOTME message가전송되는것을확인한다.

� Platform builder를보면, available device가추가된것을볼수있다.

� 이것을선택하고 [OK]를누른다.

� Board와 platform builder와의연결이완료되었다.


� [Target] -> [Download/Initialize]를통해 kernel을 download한다.


� [YES]를누르고계속진행한다.


� Download가진행되는것을볼수있다.


� Download가완료되고나면,

� Platform builder는 debuging모드가되고,

� Board의 TFTLCD에는WINCE가동작하는것을볼수있다.


Application Application 제작제작


Application 개발

� Application을개발하기위해서는 Embedded C++이필요하다.

� Platform builder를통해 SDK를생성한후,

� Embedded C++을이용해 application을제작한다.

� Application은 “Hello World”라는글자를화면에표시한다.


SDK SDK 제작제작


SDK제작

� Platform builder에서 [Platform]->[Configure SDK]를선택한다.




� 적절한이름을입력한후, [다음]을클릭한다.


� MFC로 application을제작할것이므로, 위그림대로선택한다.

� visual studio .NET으로개발할것이라면 .NET Compact framework도선택한다.


� 설정이완료되었다.

� [Finish]를눌러완료한다.


Build SDK

� [Platform]->[Build SDK]를선택한다.


� Build가완료되었다.

� SDK가만들어진위치를확인한다.

� Error가없는것을확인하고, [Done]버튼을누른다.


SDK 설치

� SDK가생성된위치로가서 msi파일을실행한다.


� License에동의를하고 [Next]를선택한다.


� 적당한내용을입력한후, [Next]를선택한다.


� [Custom]을선택한다.


� 모두선택되어있으므로, [Next]를선택한다.


� [Install]을선택한다.


� 설치가진행되고있다.


� 설치가완료되었다.

� Embedded C++을실행한다.


Embedded C++Embedded C++을을 이용한이용한application application 개발개발


� Embedded C++에서

� [File]->[New]를선택한다.


� 위와같이설정후, [OK]를선택한다.


� [Finish]를선택한다.


� [OK]를선택하면 app_test라는 project가생성된다


� 왼쪽화면과같이코드가생성된것을볼수있다.

� Platform builder와board가연결되어있는상태에서다음을진행한다.


실행전설정사항

� [tools]->[Configure platform

manager]를선택하면위와같은화면이나타난다.

� PXA255PRO3_MH device를선택하고 [Properties]를선택한다.


� Transport와 startup Server를왼쪽과같이설정한다.

� Transport의 configure버튼을누른다.


� Named connection을제작한 SDK에맞는이름을선택한다.

� [OK]를통해선택을마치고embedded C++에서프로그램을실행하면보드에서윈도우가뜨는것을확인할수있다.

Documents

Windows CE .NET Development Environmentmesl.khu.ac.kr/lecture/doc/esl2/closed.pxa255/esl2-08... · 2016-09-10 · Embedded Visual C++ 4.0 MS 에서제공하는Windows CE .NET 용소프트웨어를개발하는프로그램