DOCSLIB.ORG

Programming the Pocket PC OS for Embedded IR Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

AN926 Programming the Pocket PC OS for Embedded IR Applications Appendix A: “Example Irda Standard System Author: Joseph Snyder, Microchip Technology Inc. Description” describes the system and documents the Frank Ableson, Unwired Tools, LLC tool used to create this Pocket PC application program, while Appendix B: “PPC Source Code - IrDA INTRODUCTION DEMO.CPP” through Appendix C: “PPC Source Code - IrDA DemoDlg.cpp” is the PPC Application This application note details the tools, supporting Program source code. technologies and procedures for the development of infrared applications on Windows Mobile™ based Figure 1 shows an IrDA standard system, where a devices. Pocket PC PDA device is communicating with an embedded system. In this system, the Pocket PC A Pocket PC (PPC) application that interfaces with an (PPC) PDA operates as the Primary Device (Client) embedded system via IrCOMM is included in the and the embedded system operates as the Secondary Appendices of this application note. This source code Device (Server). The terms Client and Server are used ® demonstrates the use of the Windows Application in reference to Windows (PC and PPC) programming, ® Programming Interface (API) required for IrDA while Primary Device and Secondary Device are terms standard IR communication on Windows Mobile based used by the IrDA Standard. platforms. FIGURE 1: POCKET PC PDA - EMBEDDED SYSTEM BLOCK DIAGRAM Embedded System with IrDA® Port (Secondary Device/Server) Host Controller MCP215X Optical and Embedded or Transceiver Circuitry MCP2140 Circuitry Pocket PC Handheld Device with IrDA® Standard Port (Primary Device/Client) © 2007 Microchip Technology Inc. DS00926A-page 1 AN926 Terminology • Primary Device: The IrDA standard device that queries for other devices. Below is a list of useful terms and their definitions: • Secondary Device: The IrDA standard device • Pocket PC: A Windows Mobile based handheld that waits to detect IR communication before device. performing any IR communication. • Windows CE™: Microsoft® operating system for • Host Controller: The controller in the embedded handheld devices. system that communicates to the MCP215X or • Microsoft ActiveSync®: Application enabling the MCP2140. creation of a partnership between a desktop • MCP215X: An IrCOMM protocol handler IC that computer and a mobile device. This application supports IR communication from 9600 baud to allows desktop debugging of Windows Mobile 115,200 baud. based applications. • MCP2140: A low-cost IrCOMM protocol handler • Host System: The computer with which a PPC IC that supports IR communication at 9600 baud. OS device performs an ActiveSync. The host • Protocol Stack: A set of network protocol layers system is also where development takes place. that work together. Figure 2 shows the IrDA Host systems are typically based on Windows, standard protocol stack. Macintosh® or Linux® operating systems. • IrCOMM (9-wire “cooked” service class): IrDA • Microsoft Foundation Class (MFC): Class standard specification for the protocol to replace library and framework for application development the serial cable (using flow control). on Windows based platforms. ® • Microsoft eMbedded Visual C++ : FIGURE 2: IrDA® STANDARD DATA - Development environment for the development of PROTOCOL STACKS Windows Mobile based applications using C++. Available for free download from Microsoft’s web IrTran-P IrObex IrLan IrComm (1) IrMC site at www.microsoft.com. • Microsoft eMbedded Visual Basic®: LM-IAS Tiny Transport Protocol (Tiny TP) Development environment for the development of Windows Mobile based applications using Visual IR Link Management - Mux (IrLMP) Basic. Available for free download from Microsoft’s web site at www.microsoft.com. IR Link Access Protocol (IrLAP) • Microsoft Visual Studio® .NET: Development environment for the development of Windows Asynchronous Synchronous Synchronous desktop and Mobile based applications using Serial IR (2, 3) Serial IR 4 PPM C++, Visual Basic, Visual C#® and the .NET (9600 -115200 b/s) (1.152 Mb/s) (4 Mb/s) framework. Available for purchase from Microsoft’s web site at www.microsoft.com. • Microsoft Software Development Kit (SDK): Documentation, samples, header files, libraries Supported by Optional IrDA® standard and tools needed to develop applications that run the MCP215X data protocols not on the Windows operating system. All Microsoft and MCP2140. supported by the MCP215X tools require the correct platform SDK to target and MCP2140. Windows Mobile based devices. • Microsoft eMbedded Visual Tools 3.0: Note 1: The MCP215X and MCP2140 Development environment for the development of implement the 9-wire “cooked” service Windows Mobile based applications, includes class serial replicator. Microsoft eMbedded Visual C++ 3.0, eMbedded 2: An optical transceiver is required. Visual Basic 3.0 and the required SDK for Pocket PC 2002. 3: The MCP2140 support 9600 baud IR communication only. INFRARED COMMUNICATIONS The application built and discussed in this application note uses a high-level, infrared protocol called IrCOMM. This protocol is designed to be a wire- DS00926A-page 2 © 2007 Microchip Technology Inc. AN926 replacement technology. Infrared technology is an Note 1: The project files have been converted to excellent choice for data collection for many reasons, embedded Visual C version 4.0. including: 2: The sample application created in this • Availability: Virtually every late-model PDA and Application Note is a Microsoft laptop contains an IrDA standard port. Foundation Class (MFC) C++ application • Cost: IrDA standard communications may be which relies heavily on the characteristics added to a custom design very economically, as of object oriented programming. demonstrated in this application note. Therefore, to get the most out of this • Convenience and Compatibility: Working without application note’s examples requires an wires means no cables, gender-changers or any understanding of C++ programming. other gadgets to allow two devices to communi- However, it is possible to employ “C#” to cate. This is vital to the frequent traveler or perform IrDA programming under the technician in the field. Windows environment. An example of C# For more information regarding the IrComm protocol, IrDA programming under Pocket PC visit the IrDA organization’s web site at: www.irda.org. 2003 is available on the web site within this application note’s zipped source code files. WINDOWS POCKET PC DEVELOPMENT POCKET PC 2002 The Windows Mobile based Pocket PC is a handheld The eMbedded Visual Tools 3.0 package, available for device utilizing the Windows Pocket PC 2000/2002/ free from Microsoft (www.microsoft.com), includes 2003 platforms. The Pocket PC software platforms are eMbedded Visual C++ 3.0, eMbedded Visual Basic 3.0 built on the Windows CE 3.0/4.0 operating systems (see and the required software development kit (SDK). This Table 1). Pocket PC allows development of applications version supports the Pocket PC 2002 platform. using the familiar Windows development tools and POCKET PC 2003 APIs. These APIs include support for the development of applications that can communicate with other devices Development of Pocket PC 2003 applications requires utilizing wireless transmission, such as Wi-Fi®, eMbedded Visual C++ 4.0 or .NET tools. eMbedded Bluetooth™ and infrared. Visual C++ 4.0 is also available as a free download from Microsoft’s web site at www.microsoft.com. Pocket PC Tools TABLE 1: PLATFORM OPERATING Microsoft offers a wide range of development choices, SYSTEMS including the eMbedded Visual C++, eMbedded Visual Basic and Visual C# programming languages. There Pocket PC Platform Window CE Version are currently three development environments avail- 2000 2.0, 2.1, 2.11, 3.0 able for Pocket PC development: eMbedded Visual 2002 3.0 and later C++, eMbedded Visual Basic and Visual Studio .NET. The platform and chosen API (Win32®, MFC, ATL, 2003 4.0 and later .NET Compact Framework) determines the application tools and languages available for development (see Table 2). Both platforms, Pocket PC 2002 and Pocket PC 2003, can be targeted with one code base using eMbedded Visual C++ 3.0 if the application being developed uses the documented Microsoft APIs. This application note focuses on development of Pocket PC 2002 and 2003 applications using Microsoft’s eMbedded Visual C++ and the Microsoft Foundation Library (MFC). © 2007 Microchip Technology Inc. DS00926A-page 3 AN926 TABLE 2: PLATFORM DEVELOPMENT TOOLS Development Tools eMbedded Visual Tools 3.0 eMbedded Visual eMbedded Visual eMbedded Visual Visual Studio .NET C++ 3.0 Basic 3.0 C++ 4.0 (C#, Visual Basic) Pocket PC 2002 X X — — Pocket PC 2003 — — X X API • MFC • eMbedded Visual •MFC • .NET Compact •ATL Basic •ATL Framework •Win32® •Win32® TOOL INSTALLATION WINDOWS PROGRAMMING To insure inter operability between the development The Windows programming model is based on an tools and the ability to target multiple platforms, the event-driven architecture. Events can be generated development tools and SDKs should be installed on the through user interaction or some other event. Each development system in the recommended order. time the user interacts with the interface, an event is 1. Uninstall all existing tools and SDKs. generated and a message is placed in the operating 2. Install Microsoft ActiveSync 3.7. system's message queue to be dispatched to the 3. Install the eMbedded Visual Tools - 2002 application. A message handler in the application Edition, Pocket PC 2002 SDK and Smartphone handles
Recommended publications
  • Mypal A600A600A600A600

    Mypal A600A600A600A600

    MyPal MyPalMyPalMyPal A600A600A600A600 ® MyPal A600 User’s Manual MyPal A600 Microsoft MS ActiveSync Windows Microsoft Intel Intel ©2002 Mypal A600 1.00 T1054 2002 7 2 MyPal A600 Pocket PC MyPal A600 ASUSTeK COMPUTER INC.( ) 150 886-2-2894-3447 [email protected] 0800-093-456 ... / / / / 886-2-2890-7113 ... 886-2-2890-7114 ... 886-2-2890-7698 [email protected] cscnews.asus.com.tw www.asus.com ASUS COMPUTER INTERNATIONAL ( ) 6737 Mowry Avenue, Mowry Business Center, Building 2 Newark, CA 94560, USA +1-510-608-4555 [email protected] ASUS Technology Service Inc. +1-502-995-0883 +1-502-933-8713 [email protected] 7100 Intermodal Dr.Suite - A Louisville Ky,40258 USA ASUS Holland BV. ( ) +31-(0)591-668190 ... +31-(0)591-666852 [email protected] [email protected] [email protected] [email protected] www.asus.com.tw FTP ftp.asus.com.tw/pub/ASUS MyPal A600 Pocket PC 3 MyPal A600 1. ( http:// www.asus.com.tw) 2. - 1. http://www.asusmall.com.tw/accounts/member/ Chinese (TWN) Registration ( ) Join Membership ( ) 2. http://www.asus.com.tw/ ASUS Membership Asus Member's Area Chinese(TWN) Join Membership ( ) "*" ( ) Agree and continue( ) 1. " " ( ) 2. 0800-093-456 Flash ROM A600T---------- IIIIIIIIIIIIIIIIIIIIIIIII xxAPxxxxxx---------------- 4 MyPal A600 Pocket PC MyPal A600 1. 2. 3. (1) (2) (3) LCD LCD 1. 2. 3. 4. 5. 6. 7. 8. 9. 1. 0800-093-456 2. 48 48 3. 0800-093- 456 4. 5. !!! MyPal A600 Pocket PC 5 MyPal A600 MyPal A600 6 MyPal A600 Pocket PC MyPal A600 0 30 50 122 20~30 - - - MyPal A600 Pocket PC 7 MyPal A600 .....................................................................
  • Programming-8Bit-PIC

    Programming-8Bit-PIC

    Foreword Embedded microcontrollers are everywhere today. In the average household you will find them far beyond the obvious places like cell phones, calculators, and MP3 players. Hardly any new appliance arrives in the home without at least one controller and, most likely, there will be several—one microcontroller for the user interface (buttons and display), another to control the motor, and perhaps even an overall system manager. This applies whether the appliance in question is a washing machine, garage door opener, curling iron, or toothbrush. If the product uses a rechargeable battery, modern high density battery chemistries require intelligent chargers. A decade ago, there were significant barriers to learning how to use microcontrollers. The cheapest programmer was about a hundred dollars and application development required both erasable windowed parts—which cost about ten times the price of the one time programmable (OTP) version—and a UV Eraser to erase the windowed part. Debugging tools were the realm of professionals alone. Now most microcontrollers use Flash-based program memory that is electrically erasable. This means the device can be reprogrammed in the circuit—no UV eraser required and no special packages needed for development. The total cost to get started today is about twenty-five dollars which buys a PICkit™ 2 Starter Kit, providing programming and debugging for many Microchip Technology Inc. MCUs. Microchip Technology has always offered a free Integrated Development Environment (IDE) including an assembler and a simulator. It has never been less expensive to get started with embedded microcontrollers than it is today. While MPLAB® includes the assembler for free, assembly code is more cumbersome to write, in the first place, and also more difficult to maintain.
  • Windows Mobile

    Windows Mobile

    Universidad Católica “Nuestra Señora de la Asunción” Teoría y Aplicación de la Informática 2 Windows Mobile Carlos Trabuco [email protected] Asunción – Paraguay 2009 Introducción Windows Mobile es un sistema operativo compacto combinado con un conjunto de aplicaciones básicas para dispositivos móviles basados en la API Win32 de Microsoft. Los dispositivos que llevan Windows Mobile son Pocket PC, Smartphones, Media Center portátil y computadoras en tableros de ciertos automóviles. Ha sido diseñado para ser similar a las versiones de escritorio de Windows, inteligente y estético. Adicionalmente Windows Mobile cuenta con la opción de obtener software de terceros que puede ser utilizado para el desarrollo de aplicaciones. Windows mobile hace su aparición como el sistema operativo “Pocket PC 2000” y fue evolucionando a través de los años hasta llegar hoy día a su versión Windows Mobile 6.1. Microsoft concedió la licencia del Windows Mobile a cuatro de los cinco mayores fabricantes de telefonía móvil del mundo, siendo Nokia la excepción. Se estima que el 80% de los 50 millones de dispositivos equipados con WM (Windows Mobile) fueron producidos, bajo contrato, por la corporación HTC (High Tech Computer), que produce dispositivos para varias grandes compañías bajo sus marcas y últimamente ha sacado también su propia marca HTC. En febrero del 2009 Microsoft firma un acuerdo con la tercera mayor compañía productora de teléfonos móviles, LG Electronics, y concede la licencia de WM para 50 nuevos modelos de Smartphone que lanzara LG. Características Comunes del WM Windows Mobile para Pocket PC lleva estas características estándar en la mayoría de sus versiones: La pantalla principal muestra la fecha actual, la información del propietario, las próximas citas, los mensajes de correo electrónico, y tareas.
  • Pocket PC Backup/Restore Made Easy

    Pocket PC Backup/Restore Made Easy

    Pocket PC backup/restore made easy Last year in the September 2005 issue of the First Responder we had an article on backing up the PEAC-WMD software application to either a PC or to the flash memory on the PDA. This is still a problem customers are encountering and I thought that revisiting the problem and the solutions would be of assistance to our customers and others that encounter this problem with Pocket PCs. Background Before getting into the mechanics of the backup and restore processes a short discussion about the problem may help Pocket PC users understand the problem. The Pocket PC processor draws power regardless of whether the unit is turned ON or OFF. The ON/OFF button simply turns the display ON/OFF, and since the display is one of the primary power consumers on the PDA, shutting off the display will extend the useful life of the battery on a single charge. Most of the batteries on the Pocket PCs are Lithium-Hydride (LiH) units and typically have a pretty reasonable performance. But like any battery, over time they will degrade and may have to be replaced. The primary thing to remember – periodically charge the PDA! Well that’s easy for me to say, but in the real world that’s not always easy to do. Many fire departments like to mount the PDA in the cab of a vehicle so it’s ready when rolling out to a Hazmat incident. Great plan and the right idea, but sometimes the charger isn’t connected to power and before long the unit is dead.
  • Extreme Low Power (XLP) PIC® Microcontrollers

    Extreme Low Power (XLP) PIC® Microcontrollers

    XLP PIC® MCUs eXtreme Low Power (XLP) PIC® Microcontrollers www.microchip.com/xlp Looking Beyond Low-Power MCUs Microchip’s XLP PIC® MCUs As more wearables, wireless sensor networks, and other Internet of Things (IoT) enabled smart devices are getting powered from battery, energy conservation becomes paramount. Today’s connected appli- cations must consume little power and, in extreme cases, last for up to 20+ years while running from a single battery. To enable applica- tions like these, products with Microchip’s eXtreme Low Power (XLP) technology offer the industry’s lowest Run and Sleep currents. Benefits of XLP PIC MCUs Low Sleep Currents Battery-Friendly VBAT Battery Back-Up Large Portfolio of XLP with Flexible Wake-Up Features • Automatic switch-over MCUs Sources • Enable battery lifetime upon loss of VDD • 8–121 pins, • Sleep current down greater than 20 years • Maintains Real-Time 4 KB–1 MB Flash to 9 nA • Low-power supervisors Clock/Calendar (RTCC) • Wide selection of • Brown-Out Reset (BOR) for safer operation and user registers packages down to 45 nA (BOR, WDT) • Powered seperately • Active mode currents as • Real-time clock down to • Core Independent Pe- from 1.8–3.6V source low as 30 µA/MHz with 300 nA ripherals (CIPs) take the (coin cell) efficient instruction set • Watch-Dog Timer (WDT) load off the CPU and per- with over 90% single- down to 200 nA form extremely complex cycle instructions tasks in self-sustaining mode at lowest possible energy requirement XLP PIC MCU Application Examples Internet of Things Smart Energy
  • MPLAB XC8 PIC Assembler User's Guide

    MPLAB XC8 PIC Assembler User's Guide

    MPLAB® XC8 PIC® Assembler User's Guide Notice to Customers All documentation becomes dated and this manual is no exception. Microchip tools and documentation are constantly evolving to meet customer needs, so some actual dialogs and/or tool descriptions can differ from those in this document. Please refer to our web site (https://www.microchip.com) to obtain the latest documentation available. Documents are identified with a “DS” number. This number is located on the bottom of each page, in front of the page number. The numbering convention for the DS number is “DSXXXXXA,” where “XXXXX” is the document number and “A” is the revision level of the document. For the most up-to-date information on development tools, see the MPLAB® IDE online help. Select the Help menu, and then Topics to open a list of available online help files. © 2020 Microchip Technology Inc. User Guide DS50002974A-page 1 Table of Contents Notice to Customers.......................................................................................................................................1 1. Preface....................................................................................................................................................4 1.1. Conventions Used in This Guide..................................................................................................4 1.2. Recommended Reading...............................................................................................................5 1.3. Document Revision History..........................................................................................................5
  • MPLAB XC8 PIC Assembler User's Guide for Embedded Engineers

    MPLAB XC8 PIC Assembler User's Guide for Embedded Engineers

    MPLAB® XC8 PIC Assembler User's Guide for Embedded Engineers Notice to Customers All documentation becomes dated and this manual is no exception. Microchip tools and documentation are constantly evolving to meet customer needs, so some actual dialogs and/or tool descriptions can differ from those in this document. Please refer to our web site (https://www.microchip.com) to obtain the latest documentation available. Documents are identified with a “DS” number. This number is located on the bottom of each page, in front of the page number. The numbering convention for the DS number is “DSXXXXXA,” where “XXXXX” is the document number and “A” is the revision level of the document. For the most up-to-date information on development tools, see the MPLAB® IDE online help. Select the Help menu, and then Topics to open a list of available online help files. © 2020 Microchip Technology Inc. User Guide 50002994A-page 1 Table of Contents 1. Preface....................................................................................................................................................4 Notice to Customers................................................................................................................................1 1.1. Conventions Used in This Guide..................................................................................................4 1.2. Recommended Reading...............................................................................................................5 1.3. Document Revision History..........................................................................................................5
  • Remote Wireless Control of Building Management Systems Automation

    Remote Wireless Control of Building Management Systems Automation

    Master Thesis Computer Science Thesis no: MCS-2004:23 Remote wireless control of building management systems automation Marcus Gylling Blekinge Institute of Technology Department of Software Engineering and Computer Science Examinator: Rune Gustavsson, Blekinge Institute of Technology Blekinge Institute of Technology Department of Software Engineering and Computer Science Preface This thesis is submitted to the Department of Software Engineering and Computer Science at Blekinge Institute of Technology in partial fulfilment of the requirements for the degree of Master of Science in Computer Science. The thesis is equivalent to 20 weeks of full time studies. The thesis is done in cooperation with Styrprojektering AB. Initiator to the project is Jan-Åke Gylling at Styrprojektering AB. The target group for this thesis is companies that creates installations in the building systems automation business, the users that controls those installations and also the house-owners of the buildings where the installations are made. Contact information Author: Marcus Gylling Email: [email protected] External advisor: Jan-Åke Gylling Styrprojektering AB University advisor: Rune Gustravsson II Remote wireless control of building management systems automation Blekinge Institute of Technology Department of Software Engineering and Computer Science Abstract The controlling unit in building management system automation is a PLC. Every device in an installation is connected to the PLC. When a user wants to interact with a system an operator terminal, which is attached to a cabinet where the PLC is installed, is used. With this solution the user needs to be in front of the cabinet to interact with the system. Alarms do not get the user’s attention until the user checks the operator terminal.
  • PDA Forensic Tools: an Overview and Analysis

    PDA Forensic Tools: an Overview and Analysis

    NISTIR 7100 PDA Forensic Tools: An Overview and Analysis Rick Ayers Wayne Jansen NISTIR 7100 PDA Forensic Tools: An Overview and Analysis Rick Ayers Wayne Jansen C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20988-8930 August 2004 U.S. Department of Commerce Donald L. Evans, Secretary Technology Administration Phillip J. Bond, Under Secretary of Commerce for Technology National Institute of Standards and Technology Arden L. Bement, Jr., Director ii Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Interagency Report discusses ITL’s research, guidance, and outreach efforts in computer security, and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Interagency Report 67 pages (2004) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Techn ology, nor is it intended to imply that the entities, materials, or equipment are necessa rily the best available for the purpose.
  • Picmicro Mid-Range MCU Family Reference Manual

    Picmicro Mid-Range MCU Family Reference Manual

    M PICmicro™ Mid-Range MCU Family Reference Manual 1997 Microchip Technology Inc. December 1997 /DS33023A M Internationally Recognized Quality System Certifications Microchip’s Quality System embodies the requirements of ISO9001:1994. Our Microchip Chandler and Tempe Design and Manufacturing facilities have been certified to ISO 9001. The Microchip Kaohsiung Test facility, and primary Assembly houses have been certified to ISO 9002. ISO certification plans are in-process for an esti- mated certification grant by year-end 1997. In addition, Microchip has received numerous customer certifica- tions, including a Delco issued certificate of compliance to AEC-A100/QS9000. Microchip received ISO 9001 Quality System certifica- tion for its worldwide headquarters, design, and wafer fabrication facilities in January, 1997. Our field-pro- grammable PICmicro™ 8-bit MCUs, Serial EEPROMs, related specialty memory products and development systems conform to the stringent quality standards of the International Standard Organization (ISO). “All rights reserved. Copyright © 1997, Microchip Technology Trademarks Incorporated, USA. Information contained in this publication regarding device applications and the like is intended through The Microchip name, logo, PIC, KEELOQ, PICMASTER, suggestion only and may be superseded by updates. No rep- PICSTART, PRO MATE, and SEEVAL are registered resentation or warranty is given and no liability is assumed by trademarks of Microchip Technology Incorporated in the Microchip Technology Incorporated with respect to the accu- U.S.A. racy or use of such information, or infringement of patents or other intellectual property rights arising from such use or oth- MPLAB, PICmicro, ICSP and In-Circuit Serial Programming erwise. Use of Microchip’s products as critical components in are trademarks of Microchip Technology Incorporated.
  • Developing Applications for Pocket PC and GPRS/EDGE Devcentral White Paper

    Developing Applications for Pocket PC and GPRS/EDGE Devcentral White Paper

    Developing Applications for Pocket PC and GPRS/EDGE devCentral White Paper Document Number 12588 Revision 2.0 Revision Date 10/15/03 AT&T Wireless Developer Program © 2003 AT&T Wireless. All rights reserved. Legal Disclaimer This document and the information contained herein (collectively, the "Information") is provided to you (both the individual receiving this document and any legal entity on behalf of which such individual is acting) ("You" and "Your") by AT&T Wireless Services, Inc. ("AWS") for informational purposes only. AWS is providing the Information to You because AWS believes the Information may be useful to You. The Information is provided to You solely on the basis that You will be responsible for making Your own assessments of the Information and are advised to verify all representations, statements and information before using or relying upon any of the Information. Although AWS has exercised reasonable care in providing the Information to You, AWS does not warrant the accuracy of the Information and is not responsible for any damages arising from Your use of or reliance upon the Information. You further understand and agree that AWS in no way represents, and You in no way rely on a belief, that AWS is providing the Information in accordance with any standard or service (routine, customary or otherwise) related to the consulting, services, hardware or software industries. AWS DOES NOT WARRANT THAT THE INFORMATION IS ERROR-FREE. AWS IS PROVIDING THE INFORMATION TO YOU "AS IS" AND "WITH ALL FAULTS." AWS DOES NOT WARRANT,
  • Experience of Teaching the Pic Microcontrollers

    Experience of Teaching the Pic Microcontrollers

    Session 1520 EXPERIENCE OF TEACHING THE PIC MICROCONTROLLERS Han-Way Huang, Shu-Jen Chen Minnesota State University, Mankato, Minnesota/ DeVry University, Tinley Park, Illinois Abstract This paper reports our experience in teaching the Microchip 8-bit PIC microcontrollers. The 8-bit Motorola 68HC11 microcontroller has been taught extensively in our introductory microprocessor courses and used in many student design projects in the last twelve years. However, the microcontroller market place has changed considerably in the recent years. Motorola stopped new development for the 68HC11 and introduced the 8- bit 68HC908 and the 16-bit HCS12 with the hope that customers will migrate their low- end and high-end applications of the 68HC11 to these microcontrollers, respectively. On the other hand, 8-bit microcontrollers from other vendors also gain significant market share in the last few years. The Microchip 8-bit microcontrollers are among the most popular microcontrollers in use today. In addition to the SPI, USART, timer functions, and A/D converter available in the 68HC11 [6], the PIC microcontrollers from Microchip also provide peripheral functions such as CAN, I2C, and PWM. The controller-area- network (CAN) has been widely used in automotive and process control applications. The Inter-Integrated Circuit (I2C) has been widely used in interfacing peripheral chips to the microcontroller whereas the Pulse Width Modulation (PWM) function has been used extensively in motor control. After considering the change in microcontrollers and the technology evolution, we decided to teach the Microchip 8-bit microcontrollers. 1 Several major issues need to be addressed before a new microcontroller can be taught: textbook, demo boards, and development software and hardware tools.