DOCSLIB.ORG

Integrated Voice Recognition and Synthesis, in an Embedded System Creating an Interactive Electronic Cook Book

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

THE UNIVERSITY OF THE WEST OF ENGLAND FACULTY OF ENVIRONMENT & TECHNOLOGY FRENCHAY Integrated Voice Recognition and Synthesis, in an Embedded System creating an Interactive Electronic Cook Book BSc Computer Systems Engineering UFCE3B-40-3 - Computing Project Jonathan Mark William Ambrose Student Number: 07503425 Supervisor : Craig Duffy Second Reader : Prakash Chatterjee Word Count : 16,429 Chapter 1-INTRODUCTION Page | i ABSTRACT The purpose of this project was to research and implement technologies that enable us to integrate with embedded devices. These technologies involved exploring how to combine speech recognition and voice synthesis together in an interactive system. The project then looks at applying this interaction in conjunction with pre-stored recipes in an XML format with a recipe book, to create a fully interactive electronic cook book. It then looks at applying this interaction in conjunction with pre-stored recipes in an XML format, to create a fully interactive electronic cook book. Chapter 1-INTRODUCTION Page | ii ACKNOWLEDGEMENT I would like to thank the following people, without whom this project wouldn’t have been as successful: Craig Duffy for his continuous support, encouragement and guidance throughout the project. My Father, Julian Ambrose, for his proof reading, and in encouraging me to simplify the technologies I talk about within the report, to make it more understandable. Lorin Netsch of TIesr (Texas Instruments Embedded Speech Recogniser) developers, for the detailed and informative responses in various e-mails, and for his subsequent help with the issues of cross compiling for the IGEP hardware. Alan Black from Carnegie Mellon University for his email communication on Flite. ISEE, manufacturer of the IGEP hardware for their software and hardware support. I would like to thank the development team, particularly Manel Caro. I would also like to thank the open source developers of the Buildroot group, and the contributors to the mailing list. In particular, Thomas Petazzoni for his contributions to Festival. Lastly, all my close family and friends for their continuous support over the course of my final year. Chapter 1-INTRODUCTION Page | iii CONTENTS ABSTRACT ......................................................................................................................................................................... i ACKNOWLEDGEMENT ..................................................................................................................................................... ii CONTENTS ....................................................................................................................................................................... iii Chapter 1. INTRODUCTION ........................................................................................................................................ 1 1.1 Project motivation ............................................................................................................................................ 1 1.2 Objectives........................................................................................................................................................ 1 1.3 Equipment and software used ......................................................................................................................... 2 1.3.1 Linux host machine ................................................................................................................................2 1.3.2 Native Compiler .....................................................................................................................................2 1.3.3 ISEE IGEP v2 board ..............................................................................................................................3 1.3.4 Embedded Linux ....................................................................................................................................3 1.3.5 TIesr (Texas Instruments Embedded Speech Recogniser).....................................................................3 1.3.6 Flite (Text to speech engine) ..................................................................................................................3 1.4 Using open source software within my project ................................................................................................. 4 Chapter 2. METHODOLOGY ....................................................................................................................................... 5 2.1 Overview ......................................................................................................................................................... 5 2.2 Project research methodology ......................................................................................................................... 5 2.3 Project design methodology ............................................................................................................................. 5 2.4 Project implementation methodology ............................................................................................................... 6 2.5 Project testing methodology ............................................................................................................................. 6 Chapter 3. RESEARCH ............................................................................................................................................... 7 3.1 Embedded Systems ........................................................................................................................................ 7 3.1.1 What is an embedded system? ..............................................................................................................7 3.1.2 What is cross compiling and cross development toolchain? ...................................................................8 3.1.3 glibc & uClibc ....................................................................................................................................... 10 3.1.4 Static & Shared libraries ....................................................................................................................... 11 3.1.5 Choosing an embedded operating system ........................................................................................... 12 3.1.6 The Linux Kernel .................................................................................................................................. 15 3.1.7 The Linux Root File System ................................................................................................................. 17 3.1.8 Busybox ............................................................................................................................................... 18 3.1.9 Buildroot .............................................................................................................................................. 18 3.1.10 ALSA ................................................................................................................................................... 20 3.2 Analysing System Hardware .......................................................................................................................... 22 Chapter 1-INTRODUCTION Page | iv 3.2.1 O2 Joggler ........................................................................................................................................... 22 3.2.2 FriendlyArm Mini2440 (www.friendlyarm.net) ....................................................................................... 23 3.2.3 Texas Instruments’ (TI) BeagleBoard ................................................................................................... 25 3.2.4 ISEE IGEP V2. Rev.B & C ................................................................................................................... 26 3.3 Speech Synthesis .......................................................................................................................................... 28 3.3.1 Introduction .......................................................................................................................................... 28 3.3.2 Overview .............................................................................................................................................. 29 3.3.3 Flite: a small, fast run time synthesis engine ........................................................................................ 30 3.3.4 Festival Speech Synthesis System ...................................................................................................... 30 3.4 Speech Recognition ...................................................................................................................................... 31 3.4.1 Introduction .......................................................................................................................................... 31 3.4.2 Overview .............................................................................................................................................. 32 3.4.3 Why is Speech Recognition difficult to implement? .............................................................................. 34 3.4.4 Texas Instruments Embedded Speech Recogniser (TIesr) ................................................................... 35 3.5 Data storage with XML .................................................................................................................................
Recommended publications
  • Cubietruck – Mini PC

    Cubietruck – Mini PC

    SPRZĘT Cubietruck – mini PC Rynek komputerków jednopłytkowych opartych o procesory ARM zapoczątkowany przez Raspberry Pi rozwija się doskonale. Może nie jak grzyby po deszczu, ale systematycznie pojawiają się nowe rozwiązania: BeagleBoard, Marsboard, Cubieboard, Olinuxino itp. Różnią się one wyposażeniem, wydajnością, dostępnością dokumentacji oraz wsparciem technicznym. Ciekawie rozwija się propozycja Cubieboard. mocujących. Niby nic, ale te trzy kawałki two- org, zapoczątkowana płytką Cubieboard A10 rzywa i paczka tulejek umożliwiają poskładanie Fotografi a 3. Obudowa Cubietruck (opisaną w EP06/2013) i Cubieboard2 zgod- samodzielnego systemu mini-PC wyposażo- ną mechanicznie, ale zbudowaną w oparciu nego w dysk HDD 2,5”, wystarczająco zabez- rolę domowego centrum multimedialnego lub o nowszy, dwurdzeniowy procesor A20, zwięk- pieczając mechanicznie jego elementy. Osłony Linuxowego komputera PC. Jedyne zastrzeżenie szający wydajność Cubie i paletę jej zastosowań w odpowiednich miejscach mają wyfrezowane można mieć do kilku różnokolorowych LED, (fotografi a 1). Najnowsza propozycja to Cubie- otwory umożliwiające korzystanie z GPIO bez bezlitośnie informujących nasze oczy o stanie truck (Cubieboard3), oparty podobnie jak Cu- zdejmowania obudowy. pracy Cubie. bieboard2 (fotografi a 2) o procesor Allwinner Ciekawą propozycją dla osób wykorzy- Cubieboard3 oparty jest o SoC w architektu- A20, lecz mający znacznie bogatsze wyposaże- stujących Cubieboard3 w roli samodzielnego rze ARM7 – Allwinner A20, który w połączeniu nie, co niestety wiąże się z wyższą ceną. Porów- mini-PC, jest pełna obudowa pokazana na fo- ze sporej wielkości dyskiem NAND Flash oraz nanie parametrów poszczególnych komputer- tografi i 3. W swoim wnętrzu mieści swobodnie zwiększoną pamięcią RAM bezproblemowo ków Cubieboard umieszczono w tabeli 1. płytkę Cubieboard3, dysk HDD 2,5” (fotogra- sprawdza się w roli komputera PC pracującego Podobnie jak w przypadku poprzednich fi a 4) i przewody połączeniowe.
  • Create an Email with Subject Title “Embedded Software Engineer”, Email a Copy of Your Resume to Jessica@Princetechnology.Com

    Create an Email with Subject Title “Embedded Software Engineer”, Email a Copy of Your Resume to [email protected]

    To Apply for This Position: Create an email with subject title “Embedded Software Engineer”, email a copy of your resume to [email protected] Location Address: ALLEN PARK, MI,48101 Position Description: TITLE: Embedded Software Engineer ‐ Hypervisor OS technologies This position is responsible to develop QNX and Android operating system images for Ford infotainment products. This includes creating and integrating code for: bootloader, kernel, drivers, type 1 hypervisor, and build environment. Skills Required: • Lead the design, bring‐up and support of QNX and Android operating system images • Create virt‐io drivers for QNX or Android guest operating systems • Participate in root cause analysis of hardware quality problems and software defects • Participate in system design, documentation, and testing to deliver a best‐in‐class infotainment system Experience Required: • 5+ years operating system experience involving Linux or QNX • 5+ years C/C++ software development experience on embedded, mobile, or consumer electronic platforms Experience Preferred: • Experience with Type 1 hypervisors • Experience creating virt‐io drivers • Mastery of C/C++ language, GNU tool chain, and Unix (QNX, Linux, or equivalent) • Experience with embedded build systems including QNX system builder, buildroot, yocto, or equivalent • Knowledge of in‐vehicle signaling and communication mechanisms such as CAN • Proficiency with revision control including Git, Subversion, or equivalent • Multi‐site software project team experience Education Required: • Bachelor's degree in Computer Engineering, Electrical Engineering, Computer Science, or related Education Preferred: • Master's degree in Computer Engineering, Electrical Engineering or Computer Science Additional Information: Web Based Assessment not required for this position. Visa Sponsorship and Domestic Relocation is available for this position.
  • Release Notes for Debian GNU/Linux 5.0 (Lenny), Alpha

    Release Notes for Debian GNU/Linux 5.0 (Lenny), Alpha

    Release Notes for Debian GNU/Linux 5.0 (lenny), Alpha The Debian Documentation Project (http://www.debian.org/doc/) November 11, 2010 Release Notes for Debian GNU/Linux 5.0 (lenny), Alpha Published 2009-02-14 This document is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; with- out even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. The license text can also be found at http://www.gnu.org/copyleft/gpl.html and /usr/ share/common-licenses/GPL-2 on Debian GNU/Linux. ii Contents 1 Introduction 3 1.1 Reporting bugs on this document . .3 1.2 Contributing upgrade reports . .3 1.3 Sources for this document . .4 2 What’s new in Debian GNU/Linux 5.05 2.1 What’s new in the distribution? . .5 2.1.1 Package management . .7 2.1.2 The proposed-updates section . .7 2.2 System improvements . .8 2.3 Major kernel-related changes . .8 2.3.1 Changes in kernel packaging . .8 2.4 Emdebian 1.0 (based on Debian GNU/Linux lenny 5.0) . .9 2.5 Netbook support .
  • Symbian OS Platform Security Model

    Symbian OS Platform Security Model

    THE SYMBIAN OS BECAME FULLY OPEN sourced in February 2010, which opens even BO LI, ELENA RESHETOVA, AND T U O M A S A U R A more possibilities for application develop- ers to understand and analyze its security Symbian OS solution. We present a short introduction to the software features of Symbian plat- platform form security: three trust tiers, capability model, data caging, and the Symbian signed security model process. We also try to compare the security Bo Li is a second-year student in the master’s solution with the classical design principles program in security and mobile computing in this area, as well as briefly discuss gen- at Aalto University, Finland. He got his bach- elor’s degree in communications engineering eral design challenges and potential weak- in 2008 from Fudan University, China. nesses. [email protected] Elena Reshetova is a senior security engineer Introduction at Nokia, as well as a postgraduate student at Aalto University. She is interested in With the development of mobile devices and mo- various research areas related to platform bile computers, more and more people rely strongly security, security aspects of networking, and on them. People use mobile devices and mobile cryptography. computers to arrange their schedules, contact each [email protected] other, process emails, and share rich media con- tent. People believe it is safe to do so because it Tuomas Aura is a professor at Aalto Uni- versity, Finland. His research interests are feels secure just knowing it is “right there with security and privacy in communications you” [8].
  • Version 7.8-Systemd

    Version 7.8-Systemd

    Linux From Scratch Version 7.8-systemd Created by Gerard Beekmans Edited by Douglas R. Reno Linux From Scratch: Version 7.8-systemd by Created by Gerard Beekmans and Edited by Douglas R. Reno Copyright © 1999-2015 Gerard Beekmans Copyright © 1999-2015, Gerard Beekmans All rights reserved. This book is licensed under a Creative Commons License. Computer instructions may be extracted from the book under the MIT License. Linux® is a registered trademark of Linus Torvalds. Linux From Scratch - Version 7.8-systemd Table of Contents Preface .......................................................................................................................................................................... vii i. Foreword ............................................................................................................................................................. vii ii. Audience ............................................................................................................................................................ vii iii. LFS Target Architectures ................................................................................................................................ viii iv. LFS and Standards ............................................................................................................................................ ix v. Rationale for Packages in the Book .................................................................................................................... x vi. Prerequisites
  • Development Boards This Product Is Rohs Compliant

    Development Boards This Product Is Rohs Compliant

    Development Boards This product is RoHS compliant. PANDABOARD DEVELOPMENT PLATFORM Features: • Core Logic: OMAP4460 applications Processor • Interface: (1) General Purpose Expansion Header • Wireless Connectivity: 802.11 b/g/n (WiLink™ 6.0) • Memory: 1GB DDR2 RAM (I2C, GPMC, USB, MMC, DSS, ETM) • Debug options: JTAG, UART/RS-232, 1 GPIO button NTL • Full Size SD/MMC card port • Camera Expansion Header • Graphics APIs: OpenGL ES v2.0, OpenGL ES v1.1, • 10/100 Ethernet • Display Connectors: HDMI v1.3, DVI-D. LCD Expansion OpenVGv1.1, and EGL v1.3 • USB: (1) USB 2.0 OTG port, (2) USB 2.0 High-speed port • Audio Connectors: 3.5" In/Out, HDMI audio out For quantities greater than listed, call for quote. MOUSER Pandaboard Price Description STOCK NO. Part No. Each 595-PANDABOARD UEVM4430G-01-00-00 Pandaboard ARM Cortex-A9 MPCore 1GHz OMAP4430 SoC Platform 179.00 595-PANDABOARD-ES UEVM4460G-02-01-00 Pandaboard ARM Cortex-A9 MPCore 1GHz OMAP4460 SoC Platform 185.00 Embedded Modules Embedded BEAGLEBOARD SOC PLATFORMS BeagleBoard.org develops low-cost, fan-less single-board computers based on low-power Texas Instruments processors featuring the ARM Cortex-A8 core with all of the expandability of today's desktop machines, but without the bulk, expense, or noise. BeagleBoard.org provides an open source development platform for A B the creation of high-performance embedded designs. Beagleboard C4 Features: Beagleboard xM Features: Beaglebone Features: • Over 1,200 Dhrystone MIPS using the superscalar • Over 2,000 Dhrystone MIPS using the Super-scalar
  • OS Selection for Dummies

    OS Selection for Dummies

    OS SELECTION HOW TO CHOOSE HOW TO CHOOSE Choosing your OS is the first step, so take the time to consider your choice fully. There are many parameters to take into account: l Is this a new project or the evolution of an existing product? l Using the same SW stack? Re-using existing code? l Is your team familiar with a particular OS? Ø Using an OS you are already comfortable with can help l What are the HW constraints of your system? Ø Some operating systems require more memory/processing power than others l Have no SW team? Not sure about the above? Ø Contact us so we can help you decide! Ø We can also introduce you to one of our many partners! 1 OS SELECTION OPEN SOURCE VS. COMMERCIAL OS Embedded OS BSP Provider $ Cost Open-Source OS Boundary Devices • Embedded Linux / Android Embedded Linux $0, included • Large pool of developers available with Board Purchase • Strong community • Royalty-free And / or partners 3rd Party - Commercial OS Partners • QNX / Win10 IoT / Green Hills $>0, depends on • Professional support requirements • Unique set of development tools 2 OS SELECTION OPEN SOURCE SELECTION OS SELECTION PROS CONS Embedded Linux Most powerful / optimized Complexity for newcomers solution, maintained by NXP • Build systems Ø Yocto / Buildroot Simpler solution, makefile- Not as flexible as Yocto Ø Everything built from scratch based, maintained by BD Desktop-like approach, Harder to customize, non- Package-based distribution easy-to-use atomic updates, no cross- • Ubuntu / Debian compilation SDK Apt install / update, millions • Packages installed from server of prebuilt packages available Android Millions of apps available, same number of developers, Resource-hungry, complex • AOSP-based (no GMS) development environment, BSP modifications (HAL) • APK applications IDE + debugging tools 3 SOFTWARE PARTNERS Boundary Devices has an industry-leading group of software partners.
  • Embedded Systems 2/7

    Embedded Systems 2/7

    Embedded systems 2/7 J.-M Friedt Introduction Virtual memory access Embedded systems 2/7 Kernel module basics Using the kernel: timers J.-M Friedt Conclusion & lab session FEMTO-ST/d´epartement temps-fr´equence [email protected] slides at jmfriedt.free.fr September 9, 2020 1 / 24 Embedded systems 2/7 J.-M Friedt Operating system: the need for Introduction drivers Virtual memory access Kernel module basics Using the kernel: timers • Hardware abstraction: hide low level functions so that the developer Conclusion & lab session can focus on the functionalities provided by the peripheral ! a single entry point providing system calls (open, read, write, close) hiding access to hardware • Homogeneous interface to all peripherals (\Everything is a file") • Only the kernel can access hardware resources (DMA, interrupts) • Share resources and make sure only one process can access a given hardware function • Add functionalities to the Linux kernel: modules 2 / 24 Embedded systems 2/7 J.-M Friedt Virtual memory/hardware memory Introduction Hardware memory addressing Virtual memory • hardware memory: a value on the address bus identifies which access peripheral is active Kernel module basics • each peripheral decodes the address bus to detect whether it is the Using the kernel: target of a message timers • Conclusion & lab only one peripheral must match a given physical address (otherwise, session conflict) Virtual memory addressing • each process has its own address space • memory organization independent of physical constraints • dynamic loading
  • Pipewire: a Low-Level Multimedia Subsystem

    Pipewire: a Low-Level Multimedia Subsystem

    Proceedings of the 18th Linux Audio Conference (LAC-20), SCRIME, Université de Bordeaux, France, November 25–27, 2020 PIPEWIRE: A LOW-LEVEL MULTIMEDIA SUBSYSTEM Wim Taymans ∗ Principal Software Engineer Red Hat, Spain [email protected] ABSTRACT 2. LINUX AUDIO LANDSCAPE PipeWire is a low-level multimedia library and daemon that facili- Audio support on Linux first appeared with the Open Sound System tates negotiation and low-latency transport of multimedia content be- (OSS) [6] and was until the 2.4 kernel the only audio API available tween applications, filters and devices. It is built using modern Linux on Linux. It was based around the standard Unix open/close/read- infrastructure and has both performance and security as its core de- /write/ioctl system calls. sign guidelines. The goal is to provide services such as JACK and OSS was replaced by the Advanced Linux Sound Architecture PulseAudio on top of this common infrastructure. PipeWire is media (ALSA) [7]from Linux 2.5. ALSA improved on the OSS API and agnostic and supports arbitrary compressed and uncompressed for- included a user space library that abstracted many of the hardware mats. A common audio infrastructure with backwards compatibility details. The ALSA user-space library also includes a plugin infras- that can support Pro Audio and Desktop Audio use cases can poten- tructure that can be used to create new custom devices and plugins. tially unify the currently fractured audio landscape on Linux desk- Unfortunately, the plugin system is quite static and requires editing tops and workstations and give users and developers a much better of configuration files.
  • Symbian Foundation Press Conference

    Symbian Foundation Press Conference

    Symbian Foundation Press conference M/C – Merran Wrigley Exciting Internet experiences for the aspirations of billions 2 © 2008 Symbian Foundation Mobile software set free Symbian Foundation Kai Öistämö Executive Vice President, Nokia Shared vision for an unparalleled open mobile software platform 4 © 2008 Symbian Foundation That unites Symbian OS, S60, UIQ and MOAP(S) 5 © 2008 Symbian Foundation Creating the most proven, open, complete mobile software platform 6 © 2008 Symbian Foundation With over 200 million devices already shipped 7 © 2008 Symbian Foundation For free. 8 © 2008 Symbian Foundation Creating one platform, royalty-free Foundation Differentiated Member experience MOAP(S) 9 © 2008 Symbian Foundation Creating one platform, royalty-free Foundation Differentiated Member experience Symbian Foundation Platform Applications suite Runtimes UI framework Middleware Operating system Tools & SDK 10 © 2008 Symbian Foundation The first step to our goal • Acquiring Symbian Ltd • Closing expected in Q4 2008 • Symbian Ltd to be part of Nokia • Nokia will contribute Symbian OS and S60 to Symbian Foundation 11 © 2008 Symbian Foundation Fulfilling the Symbian mission Symbian Foundation Nigel Clifford CEO, Symbian Symbian Ltd Mission To become the most widely used software platform on the planet 13 © 2008 Symbian Foundation The leading global open platform 12% Symbian Linux 11% Microsoft RIM 60% Apple 11% Other Source Canalys – Cumulative 4% 12 month period to Q1 2008 2% 14 © 2008 Symbian Foundation The choice for the top vendors Samsung MOTO
  • Oracle® Secure Global Desktop Platform Support and Release Notes for Release 5.2

    Oracle® Secure Global Desktop Platform Support and Release Notes for Release 5.2

    Oracle® Secure Global Desktop Platform Support and Release Notes for Release 5.2 April 2015 E51729-03 Oracle Legal Notices Copyright © 2015, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
  • Openbricks Embedded Linux Framework - User Manual I

    Openbricks Embedded Linux Framework - User Manual I

    OpenBricks Embedded Linux Framework - User Manual i OpenBricks Embedded Linux Framework - User Manual OpenBricks Embedded Linux Framework - User Manual ii Contents 1 OpenBricks Introduction 1 1.1 What is it ?......................................................1 1.2 Who is it for ?.....................................................1 1.3 Which hardware is supported ?............................................1 1.4 What does the software offer ?............................................1 1.5 Who’s using it ?....................................................1 2 List of supported features 2 2.1 Key Features.....................................................2 2.2 Applicative Toolkits..................................................2 2.3 Graphic Extensions..................................................2 2.4 Video Extensions...................................................3 2.5 Audio Extensions...................................................3 2.6 Media Players.....................................................3 2.7 Key Audio/Video Profiles...............................................3 2.8 Networking Features.................................................3 2.9 Supported Filesystems................................................4 2.10 Toolchain Features..................................................4 3 OpenBricks Supported Platforms 5 3.1 Supported Hardware Architectures..........................................5 3.2 Available Platforms..................................................5 3.3 Certified Platforms..................................................7