DOCSLIB.ORG

Eclipse Based Environment for Multi-Architecture Cross Developments

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Faculdade de Engenharia da Universidade do Porto Eclipse based Environment for Multi-Architecture Cross Developments Flávio Emanuel Santos Dias Mestrado Integrado em Engenharia Electrotécnica e de Computadores Supervisor: João Paulo de Sousa July 29th, 2016 c Flávio Emanuel Santos Dias, 2016 Abstract As the pressure to meet stricter deadlines increases in order to deliver a project in time, hardware and software developers have been struggling to cut the time wasted on activities not directly related to the project. One of tools used to improve the productivity is the Integrated Development Environment (IDE), generally provided by the vendors of embedded system(s). This dissertation looks into the current state of the art of compilers, IDEs, programmers and debuggers on the attempt of unifying the development environments of some embedded systems architectures, under an Eclipse based IDE, thus providing an open-source and operating system agnostic platform that can be improved without the need to directly engage with the embedded systems vendors. A special focus is given to the current status of the debugging tools, since detecting defects is one of the main contributors to the increasing difficulties in estimating the delivery time of an hardware/software project. An additional study is performed on non-critical tools, such as version control systems and tools that generate documentation from annotated source files. When correctly used, they can provide a huge boost on the productivity of a developer or a team of developers. A proof of concept IDE is proposed, proving that the idea of integrating tools for different hardware architectures is feasible and showing that, unfortunately, the weakest part in that integration is the debug component. i ii Acknowledgments I would like to acknowledge the support of professor João Paulo de Sousa for his availability to supervise this project and the help of the technical assistants Vítor Pinto and Pedro Galvão. I also want to express my gratitude to my family, due to their constant support and patience for the last few months. And to the countless developers that dedicate their free time and knowledge on de- veloping open-source tools without ever asking for money or recognition and are always available to help those in need. Flávio Emanuel Santos Dias iii iv Contents Abstract i 1 Introduction 1 1.1 Context . .1 1.2 Motivation and goals . .2 1.3 Reading Guide . .4 2 State of the Art 5 2.1 Development tools for AVR micro controllers . .6 2.1.1 Atmel Studio . .6 2.1.2 AVR Eclipse Plug-in . .7 2.2 Development tools for PIC micro controllers . .8 2.2.1 MPLAB X . .8 2.2.2 PikLab . .8 2.2.3 Discontinued Eclipse Plug-ins . .9 2.3 Development tools for TI MSP430 micro controllers . 10 2.3.1 Code Composer Studio . 10 2.3.2 MSP430 Eclipse . 11 2.4 Development tools for ARM based micro controllers . 12 2.4.1 ARM DS-5 Development Studio . 12 2.4.2 GNU ARM Eclipse . 12 2.4.3 MDK Micro Controller Development Kit 5 . 13 2.5 Preliminary Conclusions . 14 3 Related Work 15 3.1 PlatformIO . 15 4 Eclipse IDE 17 4.1 Architecture . 17 4.1.1 Workspace . 18 4.1.2 Workbench . 18 4.2 Plug-ins and Development Environment . 19 4.3 Selected plug-ins and productivity tools . 20 4.3.1 Doxygen . 20 4.3.2 Version Control Systems: Git and SVN . 21 4.3.3 Serial Console . 22 4.4 Transition to Code Composer Studio . 22 4.4.1 Configuration of the MISRA-C compliance checker . 22 v vi CONTENTS 5 Embedded System Debugger 25 5.1 Source Level Debugging . 25 5.2 Debugging using GDB . 26 5.2.1 Technical Overview . 26 5.2.2 Interfaces for GDB . 28 5.2.3 Standalone debugging of embedded systems . 28 5.2.4 Integration into Eclipse . 30 5.3 Approaches for Embedded Systems Debugging . 31 5.3.1 In-Circuit Emulator . 31 5.3.2 On-Chip Debugger . 32 5.4 Debugging through JTAG . 33 5.4.1 OpenOCD . 33 5.4.2 AVaRICE . 34 6 Project Development 35 6.1 Hardware acquisitions . 35 6.2 Test Code Algorithms . 36 6.2.1 Software Delay . 37 6.2.2 Timer Interrupt . 37 6.2.3 External Interrupt . 38 6.2.4 Internal Peripheral . 38 6.3 Evaluation of the tool-chains . 39 6.3.1 AVR Eclipse Plug-in . 39 6.3.2 MPLAB X . 40 6.3.3 Code Composer Studio . 41 6.3.4 ARM DS-5 Development Studio and GNU ARM Eclipse . 41 7 Conclusions 43 7.1 Contributions . 43 7.2 Future Work . 44 7.2.1 AVaRICE . 44 7.2.2 Microchip PIC tool-chain integration . 44 7.2.3 Detailed test of ARM tool-chains . 44 A Listings of test cases 45 A.1 Software Delay . 45 A.1.1 For Atmel AVR micro controllers . 45 A.1.2 For Microchip PIC line of 8-bit micro controllers . 46 A.1.3 For Microchip PIC line of 32-bit micro controllers . 47 A.1.4 For Texas Instruments MSP430 micro controllers . 48 A.2 Timer Interrupt . 48 A.2.1 For Atmel AVR micro controllers . 48 A.2.2 For Microchip PIC line of 8-bit micro controllers . 49 A.2.3 For Microchip PIC line of 32-bit micro controllers . 50 A.2.4 For Texas Instruments MSP430 micro controllers . 51 A.3 External Interrupt . 52 A.3.1 For Atmel AVR micro controllers . 52 A.3.2 For Microchip PIC line of 8-bit micro controllers . 53 A.3.3 For Microchip PIC line of 32-bit micro controllers . 54 CONTENTS vii A.3.4 For Texas Instruments MSP430 micro controllers . 55 A.4 Internal Peripheral . 56 A.4.1 For Atmel AVR micro controllers . 56 A.4.2 For Microchip PIC line of 8-bit micro controllers . 58 A.4.3 For Microchip PIC line of 32-bit micro controllers . 60 A.4.4 For Texas Instruments MSP430 micro controllers . 61 References 63 viii CONTENTS List of Figures 1.1 Project completion ratios . .1 2.1 Atmel Studio 7 Integrated Development Platform Composition . .6 2.2 Optimization Levels of different versions of the compiler . .8 2.3 Code Composer Studio accessing the Eclipse Marketplace . 10 2.4 Fundamental Components of the MDK core . 13 4.1 Simplified view of Eclipse subsystems . 18 4.2 Relationship between Eclox and Doxygen . 21 5.1 Overall Structure of GDB . 27 5.2 Text User Interface of a simple adder . 28 5.3 GDB connected to remote target on port 55000 . 29 5.4 A debug session on Eclipse . 31 6.1 Loading from the target hardware . 40 ix x LIST OF FIGURES List of Tables 1.1 Main Differences between Eclipse and Visual Studio . .2 2.1 List of tools to be further investigated . .5 2.2 Summary of each development environment feature . 14 6.1 Acquired hardware . 36 xi xii LIST OF TABLES List of source codes 3.1 Platformio.ini file . 16 4.1 Masking libraries with pragma directives . 23 A.1 A simple loop for Atmel AVR micro controllers . 45 A.2 A simple loop for Microchip PIC line of 8-bit micro controllers . 46 A.3 A simple loop for Microchip PIC line of 32-bit micro controllers . 47 A.4 A simple loop for Texas Instruments MSP430 micro controllers . 48 A.5 A timer interrupt for Atmel AVR micro controllers . 48 A.6 A timer interrupt for Microchip PIC line of 8-bit micro controllers . 49 A.7 A timer interrupt for Microchip PIC line of 32-bit micro controllers . 50 A.8 A timer interrupt for Texas Instruments MSP430 micro controllers . 51 A.9 An external interrupt for Atmel AVR micro controllers . 52 A.10 An external interrupt for Microchip PIC line of 8-bit micro controllers . 53 A.11 An external interrupt for Microchip PIC line of 32-bit micro controllers . 54 A.12 An external interrupt for Texas Instruments MSP430 micro controllers . 55 A.13 Peripheral (ADC) for Atmel AVR micro controllers . 57 A.14 Peripheral (ADC) for Microchip PIC line of 8-bit micro controllers . 58 A.15 Peripheral (ADC) for Microchip PIC line of 32-bit micro controllers . 60 A.16 Peripheral (ADC) for Texas Instruments MSP430 micro controllers . 62 xiii Chapter 1 Introduction 1.1 Context As in many other consumer oriented industries, the embedded systems industry is suffering an increasing pressure to reduce the time to market the products. However, recent market studies [1, 2] confirm an unfortunate trend - more than half of the projects end up being late and a small number is even canceled. In fact, while in 2012 44% of all the projects were completed on schedule or ahead of schedule and 56% were late or canceled [1], from 2013 to 2015 these ratios became 43/57,.
Recommended publications
  • Linux and Electronics

    Linux and Electronics

    Linux and Electronics Urs Lindegger Linux and Electronics Urs Lindegger Copyright © 2019-11-25 Urs Lindegger Table of Contents 1. Introduction .......................................................................................................... 1 Note ................................................................................................................ 1 2. Printed Circuits ...................................................................................................... 2 Printed Circuit Board design ................................................................................ 2 Kicad ....................................................................................................... 2 Eagle ..................................................................................................... 13 Simulation ...................................................................................................... 13 Spice ..................................................................................................... 13 Digital simulation .................................................................................... 18 Wings 3D ....................................................................................................... 18 User interface .......................................................................................... 19 Modeling ................................................................................................ 19 Making holes in Wings 3D .......................................................................
  • Fill Your Boots: Enhanced Embedded Bootloader Exploits Via Fault Injection and Binary Analysis

    Fill Your Boots: Enhanced Embedded Bootloader Exploits Via Fault Injection and Binary Analysis

    IACR Transactions on Cryptographic Hardware and Embedded Systems ISSN 2569-2925, Vol. 2021, No. 1, pp. 56–81. DOI:10.46586/tches.v2021.i1.56-81 Fill your Boots: Enhanced Embedded Bootloader Exploits via Fault Injection and Binary Analysis Jan Van den Herrewegen1, David Oswald1, Flavio D. Garcia1 and Qais Temeiza2 1 School of Computer Science, University of Birmingham, UK, {jxv572,d.f.oswald,f.garcia}@cs.bham.ac.uk 2 Independent Researcher, [email protected] Abstract. The bootloader of an embedded microcontroller is responsible for guarding the device’s internal (flash) memory, enforcing read/write protection mechanisms. Fault injection techniques such as voltage or clock glitching have been proven successful in bypassing such protection for specific microcontrollers, but this often requires expensive equipment and/or exhaustive search of the fault parameters. When multiple glitches are required (e.g., when countermeasures are in place) this search becomes of exponential complexity and thus infeasible. Another challenge which makes embedded bootloaders notoriously hard to analyse is their lack of debugging capabilities. This paper proposes a grey-box approach that leverages binary analysis and advanced software exploitation techniques combined with voltage glitching to develop a powerful attack methodology against embedded bootloaders. We showcase our techniques with three real-world microcontrollers as case studies: 1) we combine static and on-chip dynamic analysis to enable a Return-Oriented Programming exploit on the bootloader of the NXP LPC microcontrollers; 2) we leverage on-chip dynamic analysis on the bootloader of the popular STM8 microcontrollers to constrain the glitch parameter search, achieving the first fully-documented multi-glitch attack on a real-world target; 3) we apply symbolic execution to precisely aim voltage glitches at target instructions based on the execution path in the bootloader of the Renesas 78K0 automotive microcontroller.
  • MSP430FR2433 Mixed-Signal Microcontroller

    MSP430FR2433 Mixed-Signal Microcontroller

    Product Order Technical Tools & Support & Folder Now Documents Software Community MSP430FR2433 SLASE59C –OCTOBER 2015–REVISED AUGUST 2018 MSP430FR2433 Mixed-Signal Microcontroller 1 Device Overview 1.1 Features 1 • Embedded Microcontroller Storage – 16-Bit RISC Architecture – 1015 Write Cycle Endurance – Clock Supports Frequencies up to 16 MHz – Radiation Resistant and Nonmagnetic – Wide Supply Voltage Range From 3.6 V Down – High FRAM-to-SRAM Ratio, up to 4:1 to 1.8 V (Minimum Supply Voltage is Restricted • Clock System (CS) by SVS Levels, See the SVS Specifications) – On-Chip 32-kHz RC Oscillator (REFO) • Optimized Ultra-Low-Power Modes – On-Chip 16-MHz Digitally Controlled Oscillator – Active Mode: 126 µA/MHz (Typical) (DCO) With Frequency-Locked Loop (FLL) – Standby: <1 µA With VLO – ±1% Accuracy With On-Chip Reference at – LPM3.5 Real-Time Clock (RTC) Counter With Room Temperature 32768-Hz Crystal: 730 nA (Typical) – On-Chip Very Low-Frequency 10-kHz Oscillator – Shutdown (LPM4.5): 16 nA (Typical) (VLO) • High-Performance Analog – On-Chip High-Frequency Modulation Oscillator – 8-Channel 10-Bit Analog-to-Digital Converter (MODOSC) (ADC) – External 32-kHz Crystal Oscillator (LFXT) – Internal 1.5-V Reference – Programmable MCLK Prescalar of 1 to 128 – Sample-and-Hold 200 ksps – SMCLK Derived from MCLK With • Enhanced Serial Communications Programmable Prescalar of 1, 2, 4, or 8 – Two Enhanced Universal Serial Communication • General Input/Output and Pin Functionality Interfaces (eUSCI_A) Support UART, IrDA, and – Total of 19 I/Os on
  • Atmega328p Xplained Mini User Guide

    Atmega328p Xplained Mini User Guide

    USER GUIDE ATmega328P Xplained Mini User Guide Introduction This user guide describes how to get started with the Atmel® ATmega328P Xplained Mini board. The ATmega328P Xplained Mini evalutation kit is a hardware platform to evaluate the Atmel ATmega328P microcontroller. The evaluation kit comes with a fully integrated debugger that provides seamless integration with Atmel Studio 6.2 (and later version). The kit provides access to the features of the ATmega328P enabling easy integration of the device in a custom design. 42287A-MCU-05/2014 Table of Contents Introduction .................................................................................... 1 1. Getting Started ........................................................................ 3 1.1. Features .............................................................................. 3 1.2. Design Documentation and Related Links .................................. 3 1.3. Board Assembly .................................................................... 3 1.3.1. In Customer Development Assembly ............................. 3 1.3.2. Connecting an Arduino Shield ..................................... 3 1.3.3. Standalone Node ...................................................... 3 1.4. Connecting the Kit ................................................................. 3 1.4.1. Connect the Kit to Atmel Studio ................................... 3 1.4.2. Connect the Target UART to the mEBDG COM Port ......... 3 1.5. Programming and Debugging .................................................
  • Getting Started with STK200 Dragon Introduction This Guide Is Designed to Get You up and Running with Main Software and Hardware

    Getting Started with STK200 Dragon Introduction This Guide Is Designed to Get You up and Running with Main Software and Hardware

    Getting Started with STK200 Dragon Introduction This guide is designed to get you up and running with main software and hardware. As you work through it, there could be lots of details you do not understand, but these are covered in books and other documentation that you can read later. The main software package is AVRStudio, which is Atmel’s Integrated Development Environment or IDE. There is also a plugin C Compiler module called WinAVR that compiles C programs within AVRStudio. The Kanda installer will install these packages and copy documentation to a folder on your hard drive. Default install path is C:\Program Files\STK200 Dragon AVRStudio has its own Atmel-AVR Tools folder in Program Files, and can be run from there or you can run from desktop icon. WinAVR never needs to be run directly, only from AVRStudio. The AVRStudio IDE is designed for writing source code, in C (.c files) or assembler (.asm files). These are then built or compiled into object code (.hex files) for programming into the AVR using ISP or debug files (.elf files) to step through the code. The AVR Dragon hardware is a programmer and In Circuit Emulator (ICE) in one tool. Once source code is built, it can be programmed into the AVR using ISP, which will just run the code or it can be set in Debug mode (using DebugWire or JTAG )that allows you to examine the code operation to find bugs. There are two Debug methods depending on the AVR device you are using • JTAG Mode for AVR devices with 40-pins or more • DebugWire for smaller pin-count devices.
  • Using Energia (Arduino)

    Using Energia (Arduino)

    Using Energia (Arduino) Introduction This chapter of the MSP430 workshop explores Energia, the Arduino port for the Texas Instruments Launchpad kits. After a quick definition and history of Arduino and Energia, we provide a quick introduction to Wiring – the language/library used by Arduino & Energia. Most of the learning comes from using the Launchpad board along with the Energia IDE to light LED’s, read switches and communicate with your PC via the serial connection. Learning Objectives, Requirements, Prereq’s Prerequisites & Objectives Prerequisites Basic knowledge of C language Basic understanding of using a C library and header files This chapter doesn’t explain clock, interrupt, and GPIO features in detail, this is left to the other chapters in the MSP430 workshop Requirements - Tools and Software Hardware Windows (XP, 7, 8) PC with available USB port MSP430F5529 Launchpad Software Already installed, if you Energia Download have installed CCSv5.x Launchpad drivers (Optional) MSP430ware / Driverlib Objectives Define ‘Arduino’ and describe what is was created for Define ‘Energia’ and explain what it is ‘forked’ from Install Energia, open and run included example sketches Use serial communication between the board & PC Add an external interrupt to an Energia sketch Modify CPU registers from an Energia sketch MSP430 Workshop - Using Energia (Arduino) 8 - 1 What is Arduino Chapter Topics Using Energia (Arduino) ............................................................................................................
  • Power Debugger [USER GUIDE] 2 Atmel-42696D-Power-Debugger User Guide-10/2016 5.2.5

    Power Debugger [USER GUIDE] 2 Atmel-42696D-Power-Debugger User Guide-10/2016 5.2.5

    Programmers and Debuggers Power Debugger USER GUIDE Atmel-42696D-Power-Debugger_User Guide-10/2016 Table of Contents 1. The Atmel Power Debugger...................................................................................... 4 1.1. Kit Contents..................................................................................................................................5 2. Getting Started with the Power Debugger................................................................. 6 3. Connecting the Power Debugger...............................................................................8 3.1. Connecting to AVR and SAM Target Devices...............................................................................8 4. Detailed Use Cases.................................................................................................10 4.1. Low-power Application............................................................................................................... 10 4.1.1. Requirements.............................................................................................................. 10 4.1.2. Initial Hardware Setup................................................................................................. 10 4.1.3. Connections.................................................................................................................12 4.1.4. Disabling the debugWIRE Interface.............................................................................13 4.1.5. Disabling On-board Power Supply on the Xplained
  • Code Compose Code Composer Studio

    Code Compose Code Composer Studio

    Code Composer Studio Code Composer Studio Developer(s) Texas Instruments Initial release 1999; 20 years ago Stable release 8.1 (8.1.0.00011) / 13 June 2018 ; 9 months ago Operating system Windows, Linux and macOS Platform IA-32 and x86-64 Available in 1 languages Type Integrated Development Environment Website ti.com/ccstudio Code Composer Studio (CCStudio or CCS) is an integrated development environment (IDE) to develop applications for Texas Instruments (TI) embedded processors. Texas Instruments embedded processors include TMS320 DSPs, OMAP system-on-a-chip, DaVinci system- on-a-chip, Sitara applications processors, Hercules microcontrollers, Simplelink MCUs (MSP432 and Wireless connectivity[2]microcontrollers), MSP430 and Tiva/Stellaris microcontrollers. It also enables debugging on several subsystems such as Ducati,[3] IVA Accelerator[4] and PRU-ICSS.[5] Code Composer Studio is primarily designed as for embedded project design and low-level (baremetal) JTAG based debugging. However, the latest releases are based on unmodified versions of the Eclipse open source IDE, which can be easily extended to include support for OS level application debug (Linux, Android, Windows Embedded) and open source compiler suites such as GCC. Early versions included a real time kernel called DSP/BIOS and its later inception SYS/BIOS. Currently, the successor to these tools, the TI-RTOS embedded tools ecosystem, is available for downloading as a free plugin to Code Composer Studio. History Originally Code Composer was a product from a company called GO DSP located in Toronto, Canada, and it was acquired by TI in 1997.[6] After the acquisition, Code Composer was bundled with a real-time kernel named DSP/BIOS[7] and its name was appended with the word Studio.
  • Design Considerations When Using the MSP430 Graphics Library, and Provides an Example of Implementation and Optimization

    Design Considerations When Using the MSP430 Graphics Library, and Provides an Example of Implementation and Optimization

    www.ti.com 1 Trademarks MSP430, MSP430Ware are trademarks of Texas Instruments. Stellaris is a registered trademark of Texas Instruments. All other trademarks are the property of their respective owners. SLAA548–October 2012 1 Submit Documentation Feedback Copyright © 2012, Texas Instruments Incorporated Application Report SLAA548–October 2012 Design Considerations When Using MSP430 Graphics Library Michael Stein ABSTRACT LCDs are a growing commodity in today’s market with products as diverse as children’s toys to medical devices. Modern LCDs, along with the graphics displayed on them, are growing in complexity. A graphics library can simplify and accelerate development while creating the desired user experience. TI provides the MSP430 Graphics Library for use in developing products with the MSP430™ MCU. This application report describes design considerations when using the MSP430 Graphics Library, and provides an example of implementation and optimization. Project collateral discussed in this application report can be downloaded from the following URL: www.ti.com/lit/zip/SLAA548. Contents 2 Introduction to the MSP430 Graphics Library............................................................................ 2 3 System Overview ............................................................................................................ 3 4 Hardware Implementation - LCD Bus Type .............................................................................. 4 5 Software Implementation- LCD Display Driver Layer ..................................................................
  • Tesis De Microcontroladores.Pdf

    Tesis De Microcontroladores.Pdf

    UNIVERSIDAD DE EL SALVADOR FACULTAD MULTIDISCIPLINARIA DE OCCIDENTE DEPARTAMENTO DE INGENIERÍA Y ARQUITECTURA. TRABAJO DE GRADUACIÓN DENOMINADO: “DISEÑO DE GUÍAS DE TRABAJO Y CONSTRUCCIÓN DE EQUIPO DIDÁCTICO PARA LA IMPLANTACIÓN DE PRÁCTICAS DE LABORATORIO CON MICRO CONTROLADORES EN LA CARRERA DE INGENIERÍA DE SISTEMAS INFORMÁTICOS DE LA FACULTAD MULTIDISCIPLINARIA DE OCCIDENTE.” PARA OPTAR AL GRADO DE: INGENIERO DE SISTEMA INFORMÁTICOS PRESENTAN: FRANCIA ESCOBAR, ROBERTO ANTONIO GARCÍA, JUAN CARLOS UMAÑA ORDOÑEZ, JORGE ARTURO DOCENTE DIRECTOR ING. JOSE FRANCISCO ANDALUZ NOVIEMBRE, 2007. SANTA ANA EL SALVADOR CENTRO AMÉRICA UNIVERSIDAD DE EL SALVADOR RECTOR MÁSTER RUFINO ANTONIO QUEZADA SÁNCHEZ VICERRECTOR ACADÉMICO MÁSTER MIGUEL ÁNGEL PÉREZ RAMOS VICE RECTOR ADMINISTRATIVO MÁSTER ÓSCAR NOÉ NAVARRETE SECRETARIO GENERAL LICENCIADO DOUGLAS VLADIMIR ALFARO CHÁVEZ FACULTAD MULTIDISCIPLINARIA DE OCCIDENTE DECANO LIC. JORGE MAURICIO RIVERA VICE DECANO LIC. ELADIO ZACARÍAS ORTEZ SECRETARIO LIC. VÍCTOR HUGO MERINO QUEZADA JEFE DE DEPARTAMENTO DE INGENIERÍA ING. RENÉ ERNESTO MARTÍNEZ BERMÚDEZ AGRADECIMIENTOS A DIOS TODOPODEROSO Por permitir que llegara hasta el final de la carrera, por no dejarme solo en este camino y siempre levantarme cuando necesite de su apoyo y fuerza para continuar adelante. A MI MADRE ÁNGELA VICTORIA ESCOBAR DE FRANCIA Por su apoyo, paciencia y ser un pilar en mi vida; sin la cual no hubiese podido culminar la carrera., le dedico este triunfo con las palabras con las que siempre me ha dado confianza y fuerza de seguir adelante “se triunfa cuando se persevera”. A MI PADRE JOSÉ ANTONIO FRANCIA ESCOBAR Que su ejemplo formo en mi la idea de siempre mirar más adelante, seguir luchando y creer que siempre es posible superarse cada día más; gracias por su inmenso apoyo desde todos los puntos de mi carrera y mi vida, como padre, docente, asesor y amigo.
  • Genel Amaçli Robot Kolu Tasarimi

    Genel Amaçli Robot Kolu Tasarimi

    DOKUZ EYLÜL ÜNøVERSøTESø FEN Bø/øMLERø ENSTøTÜSÜ GENEL AMAÇLI ROBOT KOLU TASARIMI Orhan Efe ALP Nisan, 2012 øZMøR GENEL AMAÇLI ROBOT KOLU TASARIMI Dokuz Eylül Üniversitesi Fen Bilimleri Enstitüsü Yüksek Lisans Tezi Mekatronik Mühendisli÷i Bölümü, Mekatronik Mühendisli÷i ProgramÕ Orhan Efe ALP Nisan, 2012 øZMøR TEùEKKÜR ÇalÕúmalarÕm boyunca de÷erli yardÕm ve katkÕlarÕyla beni yönlendiren, hoúgörü ve sabÕr gösteren de÷erli hocam ve tez danÕúmanÕm Yrd. Doç. Dr. Nalan ÖZKURT’a, yine önemli tecrübelerinden faydalandÕ÷Õm Prof. Dr. Erol UYAR hocama, robotik konusunda yo÷un tecrübelerinden yararlandÕ÷Õm de÷erli arkadaúÕm Aytekin GÜÇLÜ ’ye, mekanik aksam konusunda yo÷un eme÷i geçen, atölye ve teçhizatlarÕQÕ kullanÕPÕma açan de÷erli ustalarÕm Önder ve Erkan KURTKAFA’ya, bana verdikleri destek için çok teúekkür ederim. Son olarak bu günleri görmemi sa÷layan, hayatÕmda herúeyi borçlu oldu÷um herúeyden çok sevdi÷im, güvenlerini ve sevgilerini her zaman yo÷un hissetti÷im Húim Hatice ALP, annem Nüzhet ALP, babam Ali Ergün ALP, ablalarÕm Fethiye Yelkin ALP, Ceren SERøNKAN, Canan TOKEM, dayÕm Niyazi TOKEM ve anneannem Fikriye TOKEM’ en büyük teúekkürü borç bildi÷imi söylemek isterim. Orhan Efe ALP iii GENEL AMAÇLI ROBOT KOLU TASARIMI ÖZ Bu tez, üç eksen ve bir adet tutucuya sahip bir robot manipülatör ve robot manipülatöre insansÕ el hassasiyeti kazandÕrmak amacÕ ile ivmeölçer sensörlerden gönderilen komutlarla yönlendirilen, mikroiúlemci ailesinden PIC ile kontrol edilen servo motor sürücü kartÕ tasarÕm çalÕúmasÕQÕ ortaya koymaktadÕr. Robot manipülatörün tasarÕPÕ için Dassault Systemes firmasÕQÕn üretti÷i Solidworks programÕ kullanÕlmÕúWÕr. BaskÕ devre tekni÷i ile üretilen 5 adet servo motoru sürebilen motor sürücü kartÕ Proteus ve Eagle çizim programlarÕnda tasarlanmÕú ve çizilmiútir.
  • Universidad De San Carlos De Guatemala Facultad De Ingeniería Escuela De Ingeniería Mecánica Eléctrica

    Universidad De San Carlos De Guatemala Facultad De Ingeniería Escuela De Ingeniería Mecánica Eléctrica

    Universidad de San Carlos de Guatemala Facultad de Ingeniería Escuela de Ingeniería Mecánica Eléctrica IMPLEMENTACIÓN DEL PIC PLC AL LABORATORIO DE ELECTRÓNICA III Juan Alejandro Ortíz Chial Asesorado por el Ing. Enrique Sarvelio Ortíz Chial Guatemala, mayo de 2018 UNIVERSIDAD DE SAN CARLOS DE GUATEMALA FACULTAD DE INGENIERÍA IMPLEMENTACIÓN DEL PIC PLC AL LABORATORIO DE ELECTRÓNICA III TRABAJO DE GRADUACIÓN PRESENTADO A LA JUNTA DIRECTIVA DE LA FACULTAD DE INGENIERÍA POR JUAN ALEJANDRO ORTÍZ CHIAL ASESORADO POR EL ING. ENRIQUE SARVELIO ORTÍZ CHIAL AL CONFERÍRSELE EL TÍTULO DE INGENIERO ELECTRICISTA GUATEMALA, MAYO DE 2018 UNIVERSIDAD DE SAN CARLOS DE GUATEMALA FACULTAD DE INGENIERÍA NÓMINA DE JUNTA DIRECTIVA DECANO Ing. Pedro Antonio Aguilar Polanco VOCAL I Ing. Angel Roberto Sic García VOCAL II Ing. Pablo Christian De León Rodríguez VOCAL III Ing. José Milton De León Bran VOCAL IV Br. Óscar Humberto Galicia Núñez VOCAL V Br. Carlos Enrique Gómez Donis SECRETARIA Inga. Lesbia Magalí Herrera López TRIBUNAL QUE PRACTICÓ EL EXAMEN GENERAL PRIVADO DECANO a.i. Ing. Angel Roberto Sic García EXAMINADOR Ing. Bayron Armando Cuyán Culajay EXAMINADOR Ing. Julio Rolando Barrios Archila EXAMINADOR Ing. Jorge Gilberto González Padilla SECRETARIO Ing. Hugo Humberto Rivera Pérez HONORABLE TR¡BUNAL EXAMINADOR En cumplimiento con Ios preceptos que establece la ley de la Universidad de San Carlos de Guatemala, presento a su consideracién mi trabajo de graduación titulado: IMPLEMENTACIÓN DEL PIC PLC AL LABORATORIO DE ELECTRÓNICA I¡I Tema que me fuera asignado por la Dirección de la Escuela de lngeniería Mecánica Eléctrica, con fecha 01 de julio de 2011. Ghial ACTO QUE DEDICO A: Dios Por ser una importante influencia en mi carrera, entre otras cosas.