WinCE for LPC3250. BUMMS China Nov PDF created with pdffactory Pro trial version

Size: px

Start display at page:

Download "WinCE for LPC3250. BUMMS China Nov PDF created with pdffactory Pro trial version"

Elvin Allen Johnston
6 years ago
Views:

1 WinCE for LPC3250 BUMMS China Nov 2008

2 Contents 1. Getting started WinCE with LPC WinCE6.0 basic knowledge 3. WinCE6.0 BSP development 4. Reference 2

3 Getting started WinCE with LPC3250 3

4 Setup WinCE6.0 development environment The following must be installed in order to create a supported Windows Embedded CE 6.0 development environment: 1. Visual Studio Visual Studio 2005 SP1 3. Visual Studio 2005 SP1 Update for Vista (if applicable) 4. Windows Embedded CE 6.0 Platform Builder 5. Windows Embedded CE 6.0 SP1 (required if PB 6.0 Tools have been installed) 6. Windows Embedded CE 6.0 R2 7. Windows Embedded CE 6.0 Cumulative Product Update Rollup 12/31/ Windows Embedded CE 6.0 Monthly Update (from Jan to Sep, 2008) All of the above components can be downloaded from Microsoft MSDN website 4

5 Snapshot of VS PB6.0 environment 5

$Install the BSP unzip the BSP file lpc32xx.bsp.wince.zip into the.\wince600\platform directory. The following path should be available:.$

6 Install the BSP unzip the BSP file lpc32xx.bsp.wince.zip into the.\wince600\platform directory. The following path should be available:.\wince600\platform\lpc3250 Run the ins_lwce.bat script in the.\lpc3250 directory This is to copy common files used in other BSPs to the LPC3250 BSP. The step is necessary and once is enough. What s in the.\lpc3250 6

7 Run-time image development process Create a WinCE project based on LPC3250 BSP and PDA device design template Configure the system by selecting variant catalog items Build a run-time image Download the run-time image to target device through Ethernet Burn WinCE run-time image and bootloader to SD card or NAND flash and boot the system 7

8 Create a WinCE project Create an OS design Follow the steps in setion 4.1 of <nxp_lpc3250_wince60.pdf> Configure Catalog Items for an OS design Follow the steps in section 4.2 of <nxp_lpc3250_wince60.pdf> [DEMO] 8

9 Build the project Select Build Solution from the Visual Studio Build menu. After build complete, a number of files will be generated here:.\wince600\osdesigns\my3250\my3250\reldir\lpc32xx_armv4i_debug Including EBoot.nb0 and NK.bin Depending on the speed of your machine, build times may vary. If errors happen during the build process, correct them before next build. [Remark] You may meet two error in using current BSP package, modify them as: 1. Add the line 74 of.\wince600\platform\lpc32xx\files\platform.bib ENDIF CE_MODULES_KEYBD CE_MODULES_POINTER 2. Resave the.\wince600\platform\lpc32xx\src\inc\chip\lpc32xx_mac.h You can do something to the file and undo, then save it. There are coding confusion about the file. [DEMO] 9

10 Download WinCE image through Eboot Configure S1L To auto boot the WinCE Ethernet bootloader Eboot Follow the steps in section of <nxp_lpc3250_wince60.pdf> Configure Eboot To set boot device and debug device as Ethernet, as well as network settings. Follow the steps in section of <nxp_lpc3250_wince60.pdf> Connect PB and target board for Ethernet download Follow the steps in section of <nxp_lpc3250_wince60.pdf> You need a DHCP server to assign IP address to the Phy3250 board After the download completed, execution of WinCE will start on the board. The WinCE image NK.bin is downloaded to SDRAM 0x [DEMO] 10

11 Boot Eboot and WinCE from SD card or NAND flash To set Eboot boot device, need to use S1L command to adjust its boot settings To set WinCE image boot device, need to set Eboot boot options SD card boot is slow. The Eboot and WinCE can boot from same device OR different devices Refer to Chapter 5 of <nxp_lpc3250_wince60.pdf> for details. 11

12 WinCE Basics 12

13 WinCE 6.0 Architecture 13

Overview of OS directories Directory CRC Others OSDesigns Platform Private Public SDK Contents A file named Crc.ini, which provides information about files in the Platform Builder installation.

14 Overview of OS directories Directory CRC Others OSDesigns Platform Private Public SDK Contents A file named Crc.ini, which provides information about files in the Platform Builder installation. Run-time files, binary files for building run-time image files, registry files, and batch files used to add files to an run-time image. User-created OS designs. Device-specific files and directories. Source code for the Windows Embedded CE OS. Source code for the Windows Embedded CE OS. Tools and libraries in the Windows Embedded CE SDKs that support Platform Builder. For information about the Windows Embedded CE SDKs, see the documentation included with those products. 14

15 Terminology in WinCE Catalog A container of individually selectable units of Windows Embedded CE functionality. Catalog item is Any item that you can select from the Catalog. design template A pre-defined selection of operating system (OS) components that Microsoft provides for a category of target devices. A design template is a starting point. When saved or modified, the design template becomes an OS design. OS design A selection of Catalog items that defines the characteristics of an OS. You can begin an OS design with or without a design template. An OS design corresponds to a set of Sysgen variables. run-time image Software to deploy on a target device, or the same software running on a target device. A run-time image contains the OS and associated software. board support package (BSP) Software that is specific to a hardware board. This software typically includes the boot loader, OEM adaptation layer (OAL), and board-specific device drivers. configuration A selection of Catalog items and a selection of build options. component The smallest unit of functionality that you can add to an OS design. module An EXE or a DLL that is a part of a Windows Embedded CE OS. project A container for all files related to an OS design. 15

16 WinCE 6.0 vs. WinCE 5.0: Highlights CE 6.0 provides hundreds of OS features, source code access, and compatibility with a variety of processor architectures. The kernel for CE 6.0 has been redesigned. CE 6.0 can run as many as 32,000 simultaneous processes, each with 2 GB of virtual memory space. CE 6.0 provides a new file system that supports larger storage media, larger file sizes, removable media encryption, and more. Platform Builder for Windows Embedded CE 6.0 plugs into the development environment for Microsoft Visual Studio

17 WinCE BSP development 17

18 Overview of Windows CE Development Device Bring-up Platform Development Application Development Hardware Design Debug Hardware Create Boot loader Develop Custom Drivers Boot Minimum Kernel Custom WinCE OS features Test & Integration OAL Development BSP Development Develop & Integrate OS features Application & Middleware 18

19 Major tasks of WinCE OS design Create a board support package (BSP) for your specific target device. Create an OS design, based on a standard or custom BSP, that you can use to create a run-time image that you can download to a standard development board (SDB), which is also called a hardware platform. Create and customize device drivers for your target BSP. Customize the OS design with additional subprojects and Catalog items. Build the run-time image, download it to your SDB, and then debug the run-time image by using the debugging tools found in the CE 6.0 integrated development environment (IDE). When the run-time image is complete, export a software development kit (SDK) for your application developers. 19

20 Developing Board Support Package Developing a Boot-loader Developing an OEM Adaptation Layer (OAL) Creating Device drivers Creating OS design configuration files Board bring-up using ICE, ROM Monitors Clone Reference BSP Develop Boot loader Develop OAL (Tiny Kernel) Package BSP or Design custom OS Power management Add Device drivers 20

21 About Boot-loader A boot loader manages the boot process of the target device by initializing the target device, downloading the run-time image, and booting the run-time image on the target device. Using the boot loader during the board support package (BSP) development process saves time. Final products may not have the boot loader hardware platforms that need to perform pre-boot tasks, such as run-time image updates, might include the boot loader in the final product 21

22 Developing a Boot-loader Implement StartUp function Set SVC mode, clear caches & TLBs, disable interrupts, Initialize memory controller & PLLs Implement OEM functions called by the BLCOMMON library ( Control flow, debug, ethernet, flash, initialization, timer Create a sources file and makefile file Create the.bib file, which will be used by Romimage.exe to convert the boot loader.exe file into.bin and.nb0 files Check Platform builder help for complete list of steps to implement ( 22

23 About OAL (OEM Adaptation Layer) An OEM adaptation layer (OAL) is a layer of code between the Windows CE kernel and the hardware of your target device. Contains code to handle interrupts, timers, power management, bus abstraction, generic I/O control codes (IOCTLs) Creating the OAL is one of the more complex tasks in the process of getting a Windows CE based OS to run on a new hardware platform. In general, the easiest way to create an OAL is to copy the OAL implementation from a working OS design, and then modify it to suit the specific requirements of your hardware platform. 23

24 Developing an OEM Adaptation Layer (OAL) Implement the Startup function for the OAL Create a sources file and a makefile Implement required OAL function. Check ( Implement required kernel independent transport layer (KITL) functions ( Implement ILTiming and profiling function Create config.bib, platform.bib, platform.reg, platform.db, platform.dat files. Check Platform builder help for complete list of steps to implement ( 24

25 About Device Drivers A device driver is software that abstracts the functionality of a physical (eg. UART, network, audio) or virtual device (eg. File system) Many Windows CE device drivers implement the stream interface XXX_Open (Device Manager), XXX_Close (Device Manager), XXX_Read (Device Manager), and XXX_Write (Device Manager). Determine the driver type FileSys.exe loads file system drivers Device.exe loads audio drivers, battery drivers, keyboard drivers, mouse drivers, NDIS drivers, notification LED drivers, serial drivers, PC Card drivers, USB drivers, and any other driver that exposes the stream interface. GWES.exe loads a device driver if GWES is the only client of a driver. Device drivers loaded by GWES present a standard set of functionality for all similar devices. Drivers that GWES loads might expose the stream interface or they might expose other interfaces. Having alternatives make accessing the drivers much faster. GWES loads display drivers, printer drivers, and touch screen drivers. 25

Device Drivers Concepts Monolithic vs Layered Most Windows CE device drivers consist of a platform dependent driver (PDD) and a model device driver (MDD).

26 Device Drivers Concepts Monolithic vs Layered Most Windows CE device drivers consist of a platform dependent driver (PDD) and a model device driver (MDD). A monolithic driver combines all PDDs and MDDs into one driver. MDDs Code common to all drivers Call PDD functions Expose device driver interface (DDI) functions to the operating system (OS) Contain any interrupt service threads (ISTs) PDDs Hardware platform specific code Work with specific MDD implementations Device driver service-provider interface (DDSI) functions that the MDD calls Check ( 26

27 OS Design Configuration Files Run-time Image Configuration Files Run-time image configuration files are used by a number of tools that are called by the Make Binary Image Tool to create the run-time image. Binary Image Builder File (.bib) Defines the modules and files to be included in the run-time image. Registry File (.reg) Defines the registry keys and values for a run-time image created during a cold boot. File System File (.dat) Defines the RAM file system directories, files, and links for a run-time image created during a cold boot. Database File (.db) Defines the databases to be included in the object store of a run-time image created during a cold boot. String File (.str) Defines locale-specific string replacements for text that is visible to a user in.reg,.dat, and.db files. Each line in the.str file must end with a <CR> to enable correct processing. 27

28 OS Design Configuration Files Source Code Configuration Files Source code configuration files are used by the Build tool (Build.exe) to build modules and features and to build the source code for your run-time image. Dirs File (dirs) A text file that specifies the subdirectories that contain source code to be built. Makefile File (makefile) Each subdirectory in a source code tree should have this file. In platform builder always refers to common makefile file, Makefile.def. Module-definition File (.def) Contains the statements defining an executable or dynamic-link library. Used by the linker tool to create.exe files and DLL files Sources File (sources) Contains the macro variables and source files list needed to build source code. 28

29 Catalog Item Files After you create BSP or project, you can use a Catalog item (.cec) file to associate it with a Catalog item that you can display in the Platform Builder Catalog. For more information ( 29

30 WinCE 6.0 build system 30

31 Reference <nxp_lpc3250_wince60.pdf> MSDN MSDN is a set of online and offline services designed to help developers use Microsoft products and technologies. On MSDN, the Windows Embedded Developer Center provides information about devices, applications, services, support, and communities for a Windows Embedded CE developer. WinCE6.0 on-line documentation 31

32 NXP Semiconductors founded by Philips 32

Porting WinCE 5.0 to your NXP BlueStreak MCU Board

Porting WinCE 5.0 to your NXP BlueStreak MCU Board Durgesh Pattamatta Staff Systems Engineer, Product Line Microcontrollers, NXP Semiconductors. http://www.standardics.nxp.com/support/microcontrollers/