DOCSLIB.ORG

Mediatek Linkit™ Development Platform for RTOS Get Started Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mediatek Linkit™ Development Platform for RTOS Get Started Guide MediaTek LinkIt™ Development Platform for RTOS Get Started Guide Version: 3.0 Release date: 30 June 2016 © 2015 - 2016 MediaTek Inc. This document contains information that is proprietary to MediaTek Inc. (“MediaTek”) and/or its licensor(s). MediaTek cannot grant you permission for any material that is owned by third parties. You may only use or reproduce this document if you have agreed to and been bound by the applicable license agreement with MediaTek (“License Agreement”) and been granted explicit permission within the License Agreement (“Permitted User”). If you are not a Permitted User, please cease any access or use of this document immediately. Any unauthorized use, reproduction or disclosure of this document in whole or in part is strictly prohibited. THIS DOCUMENT IS PROVIDED ON AN “AS-IS” BASIS ONLY. MEDIATEK EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES OF ANY KIND AND SHALL IN NO EVENT BE LIABLE FOR ANY CLAIMS RELATING TO OR ARISING OUT OF THIS DOCUMENT OR ANY USE OR INABILITY TO USE THEREOF. Specifications contained herein are subject to change without notice. MediaTek LinkIt™ Development Platform for RTOS Get Started Guide Document Revision History Revision Date Description 1.0 24 March 2016 Initial version. 2.0 17 May 2016 Move the contents relative to flash, HDK, and build comments to corresponding documents. Add the support of Keil 3.0 30 June 2016 Add the support of IAR. Refine the architecture and provide more information on the SDK usage. © 2015 - 2016 MediaTek Inc. Page i of v This document contains information that is proprietary to MediaTek Inc. (“MediaTek”) and/or its licensor(s). Any unauthorized use, reproduction or disclosure of this document in whole or in part is strictly prohibited. MediaTek LinkIt™ Development Platform for RTOS Get Started Guide Table of contents 1. Overview ............................................................................................................................................ 1 1.1. Architecture of the platform .............................................................................................................. 1 1.2. Supported key components ............................................................................................................... 5 1.2.1. Wi-Fi .................................................................................................................................. 5 1.2.2. Network ............................................................................................................................ 5 1.2.3. Bluetooth/Bluetooth Low Energy ..................................................................................... 6 1.2.4. Sensor subsystem ............................................................................................................. 7 1.2.5. GNSS ................................................................................................................................. 7 1.2.6. FOTA ................................................................................................................................. 7 1.2.7. Peripheral drivers ............................................................................................................. 8 1.2.8. Battery management ........................................................................................................ 9 1.2.9. Advanced features and components .............................................................................. 10 1.3. Folder structure ................................................................................................................................ 10 1.4. Project source structure ................................................................................................................... 13 2. Getting Started Using GCC ................................................................................................................. 14 2.1. Environment ..................................................................................................................................... 14 2.2. Developing on LinkIt 7687 HDK ........................................................................................................ 14 2.2.1. Configuring the LinkIt 7687 HDK ..................................................................................... 14 2.2.2. Installing the LinkIt 7687 HDK drivers on Microsoft Windows ....................................... 16 2.2.3. Installing MT76x7 Flash Tool for LinkIt 7687 HDK .......................................................... 16 2.2.4. Flashing the image to LinkIt 7687 HDK ........................................................................... 18 2.2.5. Running the project on LinkIt 7687 HDK......................................................................... 20 2.2.6. Debugging with the LinkIt 7687 HDK from Microsoft Windows ..................................... 20 2.3. Developing on LinkIt 2523 HDK ........................................................................................................ 22 2.3.1. Configuring the LinkIt 2523 HDK ..................................................................................... 22 2.3.2. Installing the LinkIt 2523 HDK drivers on Microsoft Windows ....................................... 23 2.3.3. Installing MT2523 Flash Tool for LinkIt 2523 HDK .......................................................... 25 2.3.4. Flashing the image to LinkIt 2523 HDK ........................................................................... 26 2.3.5. Running the project on LinkIt 2523 HDK......................................................................... 28 2.3.6. Debugging with the LinkIt 2523 HDK from Microsoft Windows ..................................... 28 2.4. Building the project using the SDK ................................................................................................... 30 2.4.1. Preparing the SDK build environment ............................................................................ 31 2.4.2. Methods to build a project ............................................................................................. 38 2.5. Create your own project ................................................................................................................... 41 2.5.1. Using an existing project ................................................................................................. 41 2.5.2. Deleting a module ........................................................................................................... 42 2.5.3. Add the source and header files ..................................................................................... 42 3. Getting Started Using Keil µVision IDE ............................................................................................... 44 3.1. Environment ..................................................................................................................................... 44 3.2. Installing the Microsoft Windows version of Keil ............................................................................. 44 3.2.1. Installing the µVision IDE ................................................................................................ 44 3.2.2. Installing the Keil package for the SDK ........................................................................... 44 3.3. Build the project ............................................................................................................................... 45 3.4. Download and run the project ......................................................................................................... 47 3.4.1. Downloading the project binary using the Keil µVision IDE ........................................... 47 3.4.2. Downloading the project binary using Flash Tool or using HDK as a removable storage device .............................................................................................................................. 51 3.4.3. Running the project ........................................................................................................ 52 3.5. Debug configuration ......................................................................................................................... 53 © 2015 - 2016 MediaTek Inc. Page ii of v This document contains information that is proprietary to MediaTek Inc. (“MediaTek”) and/or its licensor(s). Any unauthorized use, reproduction or disclosure of this document in whole or in part is strictly prohibited. MediaTek LinkIt™ Development Platform for RTOS Get Started Guide 4. Getting Started Using IAR .................................................................................................................. 57 4.1. Environment ..................................................................................................................................... 57 4.2. Supported features on LinkIt HDK .................................................................................................... 57 4.3. Installing the Microsoft Windows version of IAR ............................................................................. 57 4.4. Build the project ............................................................................................................................... 57 4.5. Download and run the project ......................................................................................................... 59 4.5.1. Download the project ....................................................................................................
Load more

Recommended publications
  • Bootstomp: on the Security of Bootloaders in Mobile Devices
    BootStomp: On the Security of Bootloaders in Mobile Devices Nilo Redini, Aravind Machiry, Dipanjan Das, Yanick Fratantonio, Antonio Bianchi, Eric Gustafson, Yan Shoshitaishvili, Christopher Kruegel, and Giovanni Vigna, UC Santa Barbara https://www.usenix.org/conference/usenixsecurity17/technical-sessions/presentation/redini This paper is included in the Proceedings of the 26th USENIX Security Symposium August 16–18, 2017 • Vancouver, BC, Canada ISBN 978-1-931971-40-9 Open access to the Proceedings of the 26th USENIX Security Symposium is sponsored by USENIX BootStomp: On the Security of Bootloaders in Mobile Devices Nilo Redini, Aravind Machiry, Dipanjan Das, Yanick Fratantonio, Antonio Bianchi, Eric Gustafson, Yan Shoshitaishvili, Christopher Kruegel, and Giovanni Vigna fnredini, machiry, dipanjan, yanick, antoniob, edg, yans, chris, [email protected] University of California, Santa Barbara Abstract by proposing simple mitigation steps that can be im- plemented by manufacturers to safeguard the bootloader Modern mobile bootloaders play an important role in and OS from all of the discovered attacks, using already- both the function and the security of the device. They deployed hardware features. help ensure the Chain of Trust (CoT), where each stage of the boot process verifies the integrity and origin of 1 Introduction the following stage before executing it. This process, in theory, should be immune even to attackers gaining With the critical importance of the integrity of today’s full control over the operating system, and should pre- mobile and embedded devices, vendors have imple- vent persistent compromise of a device’s CoT. However, mented a string of inter-dependent mechanisms aimed at not only do these bootloaders necessarily need to take removing the possibility of persistent compromise from untrusted input from an attacker in control of the OS in the device.
    [Show full text]
  • Hannes Tschofenig
    Securing IoT applications with Mbed TLS Hannes Tschofenig Part#2: Public Key-based authentication March 2018 © 2018 Arm Limited Munich Agenda • For Part #2 of the webinar we are moving from Pre-Shared Secrets (PSKs) to certificated-based authentication. • TLS-PSK ciphersuites have • great performance, • low overhead, • small code size. • Drawback is the shared key concept. • Public key cryptography was invented to deal with this drawback (but itself has drawbacks). 2 © 2018 Arm Limited Public Key Infrastructure and certificate configuration © 2018 Arm Limited Public Key Infrastructure Various PKI deployments in existence Structure of our PKI The client has to store: self-signed • Client certificate plus corresponding private key. CA cert • CA certificate, which serves as the trust anchor. The server has to store: Signed by CA Signed by CA • Server certificate plus corresponding private key. Client cert Server cert (Some information for authenticating the client) 4 © 2018 Arm Limited Generating certificates (using OpenSSL tools) • When generating certificates you will be prompted to enter info. You are about to be asked to enter information that will be • The CA cert will end up in the trust incorporated into your certificate request. What you are about to enter is what is called a Distinguished anchor store of the client. Name or a DN. There are quite a few fields but you can leave some blank For some fields there will be a default value, • The Common Name used in the server If you enter '.', the field will be left blank. ----- cert needs to be resolvable via DNS Country Name (2 letter code) [AU]:.
    [Show full text]
  • We Shape the Connected World Automotive Autonomy Generating Energy Effectively Wearable Technology ARM’S Technology Is Cars Are Becoming Mobile Computing Platforms
    ARM Holdings plc Annual Report 2015: Strategic Report We shape the connected world Automotive autonomy Generating energy effectively Wearable technology ARM’s technology is Cars are becoming mobile computing platforms. Wind turbines and solar panels can be made Smart watches, biometric-monitors and More sensors and cameras are being included more effective by including technology that augmented reality headsets are intelligent, to assist the driver with lane detection, reading controls and monitors the wind turbine, and connected devices that can give us extra shaping the way we roadside signage and identifying potential hazards aggregates data across the entire wind farm. information to improve our health and or people crossing the road. In time, driver wellness, or just to help us have more fun. all live our lives; in the assistance may lead to a fully automated vehicle. home, as we travel, at school or work, and as we have fun with our friends Mobile computing Smart city streets Intelligent networks Smarter homes ARM-based mobile computers, including City infrastructure from street lights to car Broadband and mobile phone network speeds Cost-efficiency in the home can be improved smartphones, tablets and some laptops are, parking meters can be made more effective by are increasing, and latency decreasing, enabling through learning thermostats that understand for many people, the primary device for their embedding intelligent chips. Street lights that new services for operators to provide to your daily routine, domestic appliances that use work, whether in an office or on the road; can dim when no one is nearby will save energy consumers and enterprises, from delivering advanced algorithms for calculating water and for researching and writing school assignments; and reduce carbon emissions, and prognostics in more movie and TV options to collating and detergent requirements, and smart meters that and for engaging with friends.
    [Show full text]
  • Freescale Iot Solutions APF-SHB-T1454
    Freescale IoT Solutions APF-SHB-T1454 James Huang | Asia MICRO Business Development M A Y . 2 0 1 5 TM External Use The Internet of Things is Driving Explosive Growth 50 In Connected Devices BILLION 25 BILLION 12.5 BILLION 7.6B 7.2B 6.8B 6.5B World 6.3B Population # Connected <1x 1x 2x 3.5x 6.5x Devices/Person 2003 2008 2010 2015 2020 TM External Use 1 * Sources: Ericsson, February 2011; Cisco Internet Business Solutions Group (IBSG), April 2011 IoT emerging as the next mega-trend Internet subscribers over time Source: Goldman Sachs Global Investment Research TM External Use 2 * Sources: Ericsson, February 2011; Cisco Internet Business Solutions Group (IBSG), April 2011 Our Products Power The Internet of Things Microcontrollers | Digital Networking | Auto MCU | Analog and Sensors | RF Traffic Monitoring Metro Cells Base Stations Small Cells Advanced Safety Security Networked Printers Infotainment Radar + Vision Enterprise Gateways, Cloud Data Switchers, Routers Computing Center Home Health Monitors + Fitness Energy Management, Wind + Solar Telehealth Industrial Smart Energy Connected Networking Connected Grid Farms Appliances Digital Power Conversion Energy Human – Machine Meters Interface Home Hubs Machine – Machine Security TM External Use 3 IoT Is More Than M2M The Internet of Things (IoT) is about Machine to Entity (M2E): • Machine to Machine: − Automatic diagnostics for cars: Automatic information collection from your car’s engine management system and sending real- time alerts to drivers or service centers Machine to • Machine to
    [Show full text]
  • CR1000X Product Manual
    Revision: 07/20/2021 Copyright © 2000 – 2021 Campbell Scientific, Inc. Table of Contents 1. Introduction 1 2. Precautions 2 3. Initial inspection 3 4. CR1000X data acquisition system components 4 4.1 The CR1000X Datalogger 5 4.1.1 Overview 5 4.1.2 Operations 6 4.1.3 Programs 6 4.2 Sensors 6 5. Wiring panel and terminal functions 8 5.1 Power input 11 5.1.1 Powering a data logger with a vehicle 12 5.1.2 Power LED indicator 12 5.2 Power output 12 5.3 Grounds 13 5.4 Communications ports 15 5.4.1 USB device port 15 5.4.2 Ethernet port 15 5.4.3 C terminals for communications 16 5.4.3.1 SDI-12 ports 16 5.4.3.2 RS-232, RS-422, RS-485, TTL, and LVTTL ports 16 5.4.3.3 SDM ports 16 5.4.4 CS I/O port 17 5.4.5 RS-232/CPI port 18 5.5 Programmable logic control 19 6. Setting up the CR1000X 21 6.1 Setting up communications with the data logger 21 6.1.1 USB or RS-232 communications 21 6.1.2 Virtual Ethernet over USB (RNDIS) 23 6.1.3 Ethernet communications option 24 Table of Contents - i 6.1.3.1 Configuring data logger Ethernet settings 25 6.1.3.2 Ethernet LEDs 26 6.1.3.3 Setting up Ethernet communications between the data logger and computer 26 6.2 Testing communications with EZSetup 27 6.3 Making the software connection 29 6.4 Creating a Short Cut data logger program 29 6.5 Sending a program to the data logger 32 7.
    [Show full text]
  • Mediatek Inc
    01 May 2015 Asia Pacific/Taiwan Equity Research Semiconductor Devices MediaTek Inc. (2454.TW / 2454 TT) Rating NEUTRAL* Price (30 Apr 15, NT$) 395.00 RESULTS Target price (NT$) 405.00¹ Upside/downside (%) 2.5 Mkt cap (NT$ mn) 708,117 (US$ 23,121) 2Q lacks growth, but a high bar is set for 2H Enterprise value (NT$ mn) 544,619 ■ 1Q15 results in line with CS, but below street. 1Q15 sales were already Number of shares (mn) 1,792.70 Free float (%) 89.1 reported at NT$47.5 bn, -14.3% QoQ. Smartphone shipments were 85 mn 52-week price range 535.0 - 390.0 (30mn LTE), down from 95-100mn in 4Q14 due to seasonality and emerging ADTO - 6M (US$ mn) 101.0 market weakness. GMs met our 47.3% vs 46-48% guidance and OpM was also *Stock ratings are relative to the coverage universe in each analyst's or each team's respective sector. in line at 16.1% on cost controls. Lower non-op income kept EPS only in line ¹Target price is for 12 months. with our NT$4.62 and below street's NT$4.97. Research Analysts ■ 2Q15 guidance below, inventory elevated. Sales were guided -5% to +3% Randy Abrams, CFA QoQ, below CS/street's +9%/+18% QoQ on 3G price pressure and 4G mix 886 2 2715 6366 [email protected] skewed to the entry level. Margins are in line, with GMs at 45.5-47.5% and Nickie Yue OpM at 12.5-16.5%. Inventory is elevated, at 102 days and guided to stay 886 2 2715 6364 98-110 days in 2Q15, requiring 2H15 acceleration.
    [Show full text]
  • IN the UNITED STATES DISTRICT COURT for the WESTERN DISTRICT of TEXAS WACO DIVISION AMERICAN PATENTS LLC, Plaintiff, V. ANALOG D
    Case 6:18-cv-00356 Document 1 Filed 12/06/18 Page 1 of 64 IN THE UNITED STATES DISTRICT COURT FOR THE WESTERN DISTRICT OF TEXAS WACO DIVISION AMERICAN PATENTS LLC, CIVIL ACTION NO. 6:18-CV-356 Plaintiff, ORIGINAL COMPLAINT FOR v. PATENT INFRINGEMENT ANALOG DEVICES, INC., CYPRESS JURY TRIAL DEMANDED SEMICONDUCTOR CORPORATION, MARVELL INTERNATIONAL, LTD., MEDIATEK INC., and MEDIATEK USA INC., Defendants. ORIGINAL COMPLAINT FOR PATENT INFRINGEMENT Plaintiff American Patents LLC (“American Patents” or “Plaintiff”) files this original complaint against Defendants Analog Devices, Inc., Cypress Semiconductor Corporation, Marvell International, Ltd., MediaTek Inc., and MediaTek USA Inc. (collectively “Defendants”), alleging, based on its own knowledge as to itself and its own actions and based on information and belief as to all other matters, as follows: PARTIES 1. American Patents is a limited liability company formed under the laws of the State of Texas, with its principal place of business at 2325 Oak Alley, Tyler, Texas, 75703. 2. Analog Devices, Inc. (“Analog”) is a corporation organized and existing under the laws of the state of Massachusetts. It can be served via its registered agent: CT Corp System, 1999 Bryan Street, Suite 900, Dallas, TX 75201. 3. Analog is one of the world’s largest manufacturers of integrated circuits. Case 6:18-cv-00356 Document 1 Filed 12/06/18 Page 2 of 64 4. Cypress Semiconductor Corporation (“Cypress”) is a corporation organized under the laws of the state of Delaware. Cypress can be served with process by serving its registered agent: Corporation Service Company d/b/a CSC-Lawyers Incorporating Service Company, 211 E.
    [Show full text]
  • IP Production IBC Preview Cloud Playout AMC/Sundance Q&A
    IP production www.csimagazine.com IBC preview Cloud playout AMC/Sundance Q&A Welcome to High Dynamic Range television September 2015 cover.indd 1 19/08/2015 12:33:55 Expect More. AMOS Satellites. Meet us at More Coverage. More Throughput. More Services. IBC September 11-15, 2015 Across the Middle East, Europe, Africa and Asia. Amsterdam Hall 1, Booth C.65 Spacecom’s AMOS satellite constellation, consisting of AMOS-2 and AMOS-3 co-located at 4°W, AMOS-4 at 65°E and AMOS-5 at 17°E provides high-quality broadcast and communications services across Europe, Africa, Russia, Asia and the Middle East. With the upcoming launch of AMOS-6, Spacecom is expanding its coverage over Europe and Africa. The result: greater capacity, high-throughput Ka multibeam capabilities and affordable end-to-end satellite services. Spacecom. Expect More. EXPECT MORE www.amos-spacecom.com Untitled-2 1 10/08/2015 12:00:19 Contents IP production www.csimagazine.com IBC preview Cloud playout AMC/Sundance Q&A 30 Online piracy Editor Goran Nastic A new way of thinking about connected revenue security Commercial Welcome to High Dynamic Range television John Woods, Hammad Uddin September 2015 cover.indd 1 19/08/2015 12:33:55 36 Data corner A closer look at SVoD customers Design and production Matt Mills (Manager) 10 Analyst corner Jason Tucker With the first 4k channels launching in Europe, 40 IP production Matleena Lilja-Pelling an assessment of early services and the future It has its pros and cons, which broadcasters would do well to start preparing for Regular contributors 12 COVER STORY - HDR special Adrian Pennington, Philip Hunter, 44 Smart home David Adams, Stephen Cousins, High Dynamic Range really will take TV up a Anna Tobin level but it is not without challenges.
    [Show full text]
  • A Systematic Survey of Firmware Extraction Techniques for Iot Devices
    Breaking all the Things | A Systematic Survey of Firmware Extraction Techniques for IoT Devices Sebastian Vasile, David Oswald, and Tom Chothia University of Birmingham [email protected], [email protected], [email protected] Abstract. In this paper, we systematically review and categorize differ- ent hardware-based firmware extraction techniques, using 24 examples of real, wide-spread products, e.g. smart voice assistants (in particular Amazon Echo devices), alarm and access control systems, as well as home automation devices. We show that in over 45% of the cases, an exposed UART interface is sufficient to obtain a firmware dump, while in other cases, more complicated, yet still low-cost methods (e.g. JTAG or eMMC readout) are needed. In this regard, we perform an in-depth investiga- tion of the security concept of the Amazon Echo Plus, which contains significant protection methods against hardware-level attacks. Based on the results of our study, we give recommendations for countermeasures to mitigate the respective methods. 1 Introduction Extracting the firmware from IoT devices is a crucial first step when analysing the security of such systems. From a designer's point of view, preventing the firmware from falling into the hands of an adversary is often desirable: for in- stance, to protect cryptographic keys that identify a device and to impede prod- uct counterfeit or IP theft. The large variety of IoT devices results in different approaches to firmware extraction, depending on the device in question. Past work has looked at the state of security of IoT devices, e.g.
    [Show full text]
  • ARM Roadmap Spring 2017
    ARM Roadmap Spring 2017 Robert Boys [email protected] Version 9.0 Agenda . Roadmap . Architectures ARM1™ die . Issues . What is NEW ! . big.LITTLE™ . 64 Bit . Cortex®-A15 . 64 BIT . DynamIQ 3 © ARM 2017 In the Beginning… . 1985 32 years ago in a barn.... 12 engineers . Cash from Apple and VLSI . IP from Acorn Computers . Proof of concept . No patents, no independent customers, product not ready for mass market. A barn, some energy, experience and belief: “We’re going to be the Global Standard” 4 © ARM 2017 The Cortex Processor Roadmap in 2008 Application Real-time Microcontroller Cortex-A9 Cortex-A8 ARM11 Cortex-R4F ARM9 Cortex-R4 ARM7TDMI ARM7 Cortex-M3 SC300 Cortex-M1 5 © ARM 2017 5 Cortex-A73 ARM 2017 Processor Roadmap Cortex-A35 Cortex-A32 Cortex-A72 Cortex-A57 ARM 7, 9, 11 Cortex-A17 Application Cortex-A53 Cortex-A15 Real-time Not to scale to Not Cortex-A9 (Dual) Microcontroller Cortex-A9 (MPCore) Cortex-A8 Cortex-A7 ARM11(MP) Cortex-A5 MMU ARM926EJ-S Cortex-R52 No MMU Cortex-R8 200+ MHz Cortex-R7 ARM9 Cortex-R5 Cortex-R4 Cortex-M7 200+ MHz Cortex-M33 ARM7TDM 72 – 150 + MHz Cortex-M4 Cortex-M3 ARM7I SC300 Cortex-M23 DesignStart™ Cortex-M1 SC000 Cortex-M0+ Cortex-M0 6 © ARM 2017 6 Versions, cores and architectures ? Family Architecture Cores ARM7TDMI ARMv4T ARM7TDMI(S) ARM9 ARM9E ARMv5TE ARM926EJ-S, ARM966E-S ARM11 ARMv6 (T2) ARM1136(F), 1156T2(F)-S, 1176JZ(F), ARM11 MPCore™ Cortex-A ARMv7-A Cortex-A5, A7, A8, A9, A12, A15, A17 Cortex-R ARMv7-R Cortex-R4(F), Cortex-R5, R7, R8 … Cortex-M ARMv7-M Cortex-M3, M4, M7 (M7 is ARMv7-ME) ARMv6-M Cortex-M1, M0, M0+ NEW ! ARMv8-A 64 Bit: Cortex-A35/A53/57/A72 Cortex-A73 Cortex-A32 NEW ! ARMv8-R 32 Bit: Cortex-R52 NEW ! ARMv8-M 32 Bit: Cortex-M23 & M33 TrustZone® 7 © ARM 2017 What is New ? DynamIQ ! .
    [Show full text]
  • Iot Development Platform
    .org IoT Development Platform 1 Q&A . How many ARM cores shipped in 2012? 8,700,000,000 2020 . 2011 . Per Day: 23,835,616 . Per Hour: 993,151 150+ 25+ billion . Per Minute: 16,553 billion . Per Second: 276 2002 1+ billion 1998 2010 2020 2 ARM is a Semiconductor IP Company ARM’s Ecosystem Financial Tools/Technology IDM Foundry Fabless Semicon Co. Equipment Manufacturer ARM CPU GPU Software Platforms Networking Video RF Security DSP Other IP Carriers + Developers 3 ARM Cortex Advanced Processors Architectural innovation, compatibility across diverse application spectrum MP Cortex-A15 . ARM Cortex™-A family: ...2.5GHz . Applications processors for feature- Cortex-A9 rd rich OS and 3 party applications Cortex-A8 Cortex-A7 ARM Cortex-R family: Cortex-A5 . Cortex-R7 . Embedded processors for real-time Cortex-R5 signal processing, control applications Cortex-R4 Cortex-M4 . ARM Cortex-M family: Cortex-M3 Cortex-M1 . Microcontroller-oriented processors Cortex-M0 for MCU, ASSP, and SoC applications SC300 TM SC000 Applicability Unparalleled . ARM SecureCore Cortex-M0+ . Tamper-resistant security <12k gates... 4 ARM Cortex-M: Ultra Low Power, Size, + Cost 1.9 billion ARM Cortex-M devices shipped in 2012 by leading semiconductor companies MCUs radios sensors Think Powered by Watch Batteries & Energy Harvesting 5 MBED: Enabling Monetization of Disruption “By 2018, 50% of IoT solutions will be from start-ups less than 3 years old” - Gartner 6 From Sensor to Cloud Edge Clients Gateway Network Cloud Temp thin client Device Prox Provisioning and M2M Apps control Cortex-M Modem Diagnostics M2M Apps Smartphone / M2M Apps Short-Range Headless Radio e.g.
    [Show full text]
  • 042Cf377-Ed0c-4715-9260-770F680082fc.Pdf
    WiFi Tablets 70 Neon + The ARCHOS 70 Neon Plus is one of the most affordable tablets on the market. It includes a powerful quad-core processor running the latest Android operating system: Android™ 5.1 Lollipop®. The 7-inch IPS display provides incredible colors and wide viewing angles, perfect for enjoying your content on-the-go. The ARCHOS 70 Neon Plus is designed to offer a unique multimedia experience. AndroidTM 5.1, Lollipop® Android™ 5.1, “Lollipop” 7” IPS Capacitive Screen 1024x 600 pixels Rockchip 3126 Quad-Core CPU @ 1.3 GHz 1 GB RAM 8 GB flash memory (+ microSD slot) GB Micro SD Wifi WiFi, dual cameras, micro USB host, G-sensor, speaker... 8 4 5 90b Neon Featuring a powerful 1.2 GHz Quad-core processor and Dual-core graphics processor, the ARCHOS 90b Neon has a super smooth interface. At an affordable price, the ARCHOS 90b Neon delivers an amazing experience to meet all your needs: emails, movies, photos, web browsing… Android™ 4.4, “Kitkat” 9” Capacitive Screen 1024 x 600 pixels All Winner A33 Quad-Core CPU @ 1.2 GHz 512 MB RAM 8 GB flash memory (+ microSD slot) GB Wifi WiFi, dual cameras, micro USB host, G-sensor, 8 speaker... 6 7 101d Neon A mix between large screen and productivity, the ARCHOS 101d Neon includes a large 10.1” screen and ARCHOS media applications, perfect for your multimedia, wherever you are. Featuring a powerful Quad-core processor and Quad-core graphics processor, the ARCHOS 101d Neon offers a super smooth interface for an affordable price and delivers an amazing experience to meet all your needs.
    [Show full text]