DOCSLIB.ORG

ARM Debugger

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ARM Debugger ARM Debugger TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... ICD In-Circuit Debugger ................................................................................................................ Processor Architecture Manuals .............................................................................................. ARM/CORTEX/XSCALE ........................................................................................................... ARM Debugger ..................................................................................................................... 1 History ................................................................................................................................ 7 Warning .............................................................................................................................. 8 Introduction ....................................................................................................................... 9 Brief Overview of Documents for New Users 9 Demo and Start-up Scripts 10 Quick Start of the JTAG Debugger .................................................................................. 12 FAQ ..................................................................................................................................... 13 Troubleshooting ................................................................................................................ 14 Communication between Debugger and Processor cannot be established 14 Trace Extensions ............................................................................................................... 15 Symmetric Multiprocessing ............................................................................................. 16 ARM Specific Implementations ........................................................................................ 17 TrustZone Technology 17 Debug Permission 17 Checking Debug Permission 18 Checking Secure State 18 Changing the Secure State from within TRACE32 18 Accessing Memory 18 Accessing Coprocessor CP15 Register 19 Accessing Cache and TLB Contents 19 Breakpoints and Vector Catch Register 19 Breakpoints and Secure Modes 19 big.LITTLE 20 Debugger Setup 20 Consequence for Debugging 21 Requirements for the Target Software 21 ©1989-2021 Lauterbach GmbH ARM Debugger 1 big.LITTLE MP 21 Breakpoints 22 Software Breakpoints 22 On-chip Breakpoints for Instructions 22 On-chip Breakpoints for Data 22 Hardware Breakpoints (Bus Trace only) 24 Example for Standard Breakpoints 25 Complex Breakpoints 31 Direct ICE Breaker Access 31 Example for ETM Stopping Breakpoints 32 Access Classes 33 Coprocessors 41 Accessing Memory at Run-time 43 Semihosting 47 SVC (SWI) Emulation Mode 47 DCC Communication Mode (DCC = Debug Communication Channel) 49 Virtual Terminal 51 Large Physical Address Extension (LPAE) 52 Consequence for Debugging 52 Virtualization Extension, Hypervisor 53 Consequence for Debugging 53 Run-time Measurements 53 Trigger 53 ARM specific SYStem Commands ...................................................................................54 SYStem.CLOCK Inform debugger about core clock 54 SYStem.CONFIG.state Display target configuration 54 SYStem.CONFIG Configure debugger according to target topology 55 <parameters> describing the “DebugPort” 63 <parameters> describing the “JTAG” scan chain and signal behavior 68 <parameters> describing a system level TAP “Multitap” 72 <parameters> configuring a CoreSight Debug Access Port “DAP” 74 <parameters> describing debug and trace “Components” 78 <parameters> which are “Deprecated” 89 SYStem.CONFIG.EXTWDTDIS Disable external watchdog 94 SYStem.CONFIG SMMU Internal use 95 SYStem.CPU Select the used CPU 97 SYStem.JtagClock Define the frequency of the debug port 97 SYStem.LOCK Tristate the JTAG port 100 SYStem.MemAccess Run-time memory access 101 SYStem.Mode Establish the communication with the target 107 SYStem.Option Special setup 110 SYStem.Option ABORTFIX Do not access memory area from 0x0 to 0x1f 110 SYStem.Option AHBHPROT Select AHB-AP HPROT bits 110 ©1989-2021 Lauterbach GmbH ARM Debugger 2 SYStem.Option AMBA Select AMBA bus mode 110 SYStem.Option ASYNCBREAKFIX Asynchronous break bugfix 111 SYStem.Option AXIACEEnable ACE enable flag of the AXI-AP 111 SYStem.Option AXICACHEFLAGS Select AXI-AP CACHE bits 111 SYStem.Option AXIHPROT Select AXI-AP HPROT bits 112 SYStem.Option BUGFIX Breakpoint bug fix 112 SYStem.Option BUGFIXV4 Asynch. break bug fix for ARM7TDMI-S REV4 113 SYStem.Option BigEndian Define byte order (endianness) 114 SYStem.Option BOOTMODE Define boot mode 114 SYStem.Option CINV Invalidate the cache after memory modification 115 SYStem.Option CFLUSH FLUSH the cache before step/go 115 SYStem.Option CacheParam Define external cache 115 SYStem.Option CorePowerDetection Set methods to detect core power 115 SYStem.Option DACRBYPASS Ignore DACR access permission settings 117 SYStem.Option DAPDBGPWRUPREQ Force debug power in DAP 117 SYStem.Option DAP2DBGPWRUPREQ Force debug power in DAP2 118 SYStem.Option DAPSYSPWRUPREQ Force system power in DAP 118 SYStem.Option DAP2SYSPWRUPREQ Force system power in DAP2 119 SYStem.Option DAPNOIRCHECK No DAP instruction register check 120 SYStem.Option DAPREMAP Rearrange DAP memory map 120 SYStem.Option DBGACK DBGACK active on debugger memory accesses 120 SYStem.Option DBGNOPWRDWN DSCR bit 9 will be set in debug mode 121 SYStem.Option DBGUNLOCK Unlock debug register via OSLAR 121 SYStem.Option DCDIRTY Bugfix for erroneously cleared dirty bits 121 SYStem.Option DCFREEZE Disable data cache linefill in debug mode 122 SYStem.Option DEBUGPORTOptions Options for debug port handling 122 SYStem.Option DIAG Activate more log messages 123 SYStem.Option DisMode Define disassembler mode 124 SYStem.Option DynVector Dynamic trap vector interpretation 125 SYStem.Option EnReset Allow the debugger to drive nRESET (nSRST) 125 SYStem.Option ETBFIXMarvell Read out on-chip trace data 125 SYStem.Option ETMFIX Shift data of ETM scan chain by one 126 SYStem.Option ETMFIXWO Bugfix for write-only ETM register 126 SYStem.Option ETMFIX4 Use only every fourth ETM data package 126 SYStem.Option EXEC EXEC signal can be used by bustrace 126 SYStem.Option EXTBYPASS Switch off the fake TAP mechanism 127 SYStem.Option FASTBREAKDETECTION Fast core halt detection 127 SYStem.Option HRCWOVerRide Enable override mechanism 127 SYStem.Option ICEBreakerETMFIXMarvell Lock on-chip breakpoints 128 SYStem.Option ICEPICK Enable/disable assertions and wait-in-reset 128 SYStem.Option IMASKASM Disable interrupts while single stepping 128 SYStem.Option IMASKHLL Disable interrupts while HLL single stepping 129 SYStem.Option INTDIS Disable all interrupts 129 ©1989-2021 Lauterbach GmbH ARM Debugger 3 SYStem.Option IRQBREAKFIX Break bugfix by using IRQ 129 SYStem.Option KEYCODE Define key code to unsecure processor 130 SYStem.Option L2Cache L2 cache used 130 SYStem.Option L2CacheBase Define base address of L2 cache register 130 SYStem.Option LOCKRES Go to 'Test-Logic Reset' when locked 131 SYStem.Option MACHINESPACES Address extension for guest OSes 132 SYStem.Option MEMORYHPROT Select memory-AP HPROT bits 133 SYStem.Option MemStatusCheck Check status bits during memory access 133 SYStem.Option MMUPhysLogMemaccess Memory access preferences 133 SYStem.Option MMUSPACES Separate address spaces by space IDs 134 SYStem.Option MonitorHoldoffTime Delay between monitor accesses 135 SYStem.Option MPUBYPASS Ignore MPU access permission settings 135 SYStem.Option MultiplesFIX No multiple loads/stores 135 SYStem.Option NODATA No data connected to the trace 135 SYStem.Option NOIRCHECK No JTAG instruction register check 136 SYStem.Option NoPRCRReset Do not cause reset by PRCR 136 SYStem.Option NoRunCheck No check of the running state 136 SYStem.Option NoSecureFix Do not switch to secure mode 137 SYStem.Option OVERLAY Enable overlay support 138 SYStem.Option PALLADIUM Extend debugger timeout 138 SYStem.Option PC Define address for dummy fetches 139 SYStem.Option PROTECTION Sends an unsecure sequence to the core 139 SYStem.Option PWRCHECK Check power and clock 139 SYStem.Option PWRCHECKFIX Check power and clock 140 SYStem.Option PWRDWN Allow power-down mode 140 SYStem.Option PWRDWNRecover Mode to handle special power recovery 141 SYStem.Option PWRDWNRecoverTimeOut Timeout for power recovery 141 SYStem.Option PWROVR Specifies power override bit 141 SYStem.Option ResBreak Halt the core after reset 142 SYStem.Option ResetDetection Choose method to detect a target reset 143 SYStem.Option RESetREGister Generic software reset 143 SYStem.Option RESTARTFIX Wait after core restart 144 SYStem.Option RisingTDO Target outputs TDO on rising edge 144 SYStem.Option ShowError Show data abort errors 145 SYStem.Option SOFTLONG Use 32-bit access to set breakpoint 145 SYStem.Option SOFTQUAD Use 64-bit access to set breakpoint 145 SYStem.Option SOFTWORD Use 16-bit access to set breakpoint 146 SYStem.Option SPLIT Access memory depending on CPSR 146 SYStem.Option StandByTraceDelaytime Trace activation after reset 146 SYStem.Option STEPSOFT Use software breakpoints for ASM stepping 146 SYStem.Option SYSPWRUPREQ Force system power 147 SYStem.Option TIDBGEN Activate initialization for TI derivatives 147 SYStem.Option TIETMFIX Bug fix for customer specific ASIC 147 ©1989-2021 Lauterbach GmbH ARM Debugger 4 SYStem.Option TIDEMUXFIX Bug fix for customer
Load more

Recommended publications
  • KDE 2.0 Development, Which Is Directly Supported
    23 8911 CH18 10/16/00 1:44 PM Page 401 The KDevelop IDE: The CHAPTER Integrated Development Environment for KDE by Ralf Nolden 18 IN THIS CHAPTER • General Issues 402 • Creating KDE 2.0 Applications 409 • Getting Started with the KDE 2.0 API 413 • The Classbrowser and Your Project 416 • The File Viewers—The Windows to Your Project Files 419 • The KDevelop Debugger 421 • KDevelop 2.0—A Preview 425 23 8911 CH18 10/16/00 1:44 PM Page 402 Developer Tools and Support 402 PART IV Although developing applications under UNIX systems can be a lot of fun, until now the pro- grammer was lacking a comfortable environment that takes away the usual standard activities that have to be done over and over in the process of programming. The KDevelop IDE closes this gap and makes it a joy to work within a complete, integrated development environment, combining the use of the GNU standard development tools such as the g++ compiler and the gdb debugger with the advantages of a GUI-based environment that automates all standard actions and allows the developer to concentrate on the work of writing software instead of managing command-line tools. It also offers direct and quick access to source files and docu- mentation. KDevelop primarily aims to provide the best means to rapidly set up and write KDE software; it also supports extended features such as GUI designing and translation in con- junction with other tools available especially for KDE development. The KDevelop IDE itself is published under the GNU Public License (GPL), like KDE, and is therefore publicly avail- able at no cost—including its source code—and it may be used both for free and for commer- cial development.
    [Show full text]
  • FIPS 140-2 Non-Proprietary Security Policy
    Kernel Crypto API Cryptographic Module version 1.0 FIPS 140-2 Non-Proprietary Security Policy Version 1.3 Last update: 2020-03-02 Prepared by: atsec information security corporation 9130 Jollyville Road, Suite 260 Austin, TX 78759 www.atsec.com © 2020 Canonical Ltd. / atsec information security This document can be reproduced and distributed only whole and intact, including this copyright notice. Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy Table of Contents 1. Cryptographic Module Specification ..................................................................................................... 5 1.1. Module Overview ..................................................................................................................................... 5 1.2. Modes of Operation ................................................................................................................................. 9 2. Cryptographic Module Ports and Interfaces ........................................................................................ 10 3. Roles, Services and Authentication ..................................................................................................... 11 3.1. Roles .......................................................................................................................................................11 3.2. Services ...................................................................................................................................................11
    [Show full text]
  • Using the GNU Debugger (Gdb) a Debugger Is a Very Useful Tool for Finding Bugs in a Program
    Using the GNU debugger (gdb) A debugger is a very useful tool for finding bugs in a program. You can interact with a program while it is running, start and stop it whenever, inspect the current values of variables and modify them, etc. If your program runs and crashes, it will produce a ‘core dump’. You can also use a debugger to look at the core dump and give you extra information about where the crash happened and what triggered it. Some debuggers (including recent versions of gdb) can also go backwards through your code: you run your code forwards in time to the point of an error, and then go backwards looking at the values of the key variables until you get to the start of the error. This can be slow but useful sometimes! To use a debugger effectively, you need to get the compiler to put extra ‘symbol’ information into the binary, otherwise all it will contain is machine code level – it is much more useful to have the actual variable names you used. To do this, you use: gfortran –g –O0 mycode.f90 –o mybinary where ‘-g’ is the compiler option to include extra symbols, -O0 is no optimization so the code is compiled exactly as written, and the output binary is called ’mybinary’. If the source files and executable file is in the same directory, then you can run the binary through the debugger by simply doing: gdb ./mybinary This will then put you into an interactive debugging session. Most commands can be shortened (eg ‘b’ instead of ‘break’) and pressing ‘enter’ will repeat the last command.
    [Show full text]
  • MIPI Alliance Test and Debug - Nidnt-Port White Paper
    MIPI Alliance Test and Debug - NIDnT-Port White paper Approved Version: 1.0 – 10 January 2007 MIPI Board Approved for Public Distribution NOTE and DISCLAIMER: This is an informative document, not a MIPI Specification. Various rights and obligations which apply solely to MIPI Specifications (as defined in the MIPI Membership Agreement and MIPI Bylaws) including, but not limited to, patent license rights and obligations, do not apply to this document. The material contained herein is not a license, either expressly or impliedly, to any IPR owned or controlled by any of the authors or developers of this material or MIPI. The material contained herein is provided on an “AS IS” basis and to the maximum extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material and MIPI hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THIS MATERIAL. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR MIPI BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Freescale In-Circuit Emulator Base User Manual
    Freescale In-Circuit Emulator Base User Manual Rev. 1.1 1/2005 FSICEBASEUM How to Reach Us: Information in this document is provided solely to enable system and software implementers to use Freescale Semiconductor products. There are no express or implied copyright licenses USA/Europe/Locations Not Listed: granted hereunder to design or fabricate any integrated circuits or integrated circuits based on Freescale Semiconductor Literature Distribution Center the information in this document. P.O. Box 5405 Freescale Semiconductor reserves the right to make changes without further notice to any Denver, Colorado 80217 products herein. Freescale Semiconductor makes no warranty, representation or guarantee 1-800-521-6274 or 480-768-2130 regarding the suitability of its products for any particular purpose, nor does Freescale Semiconductor assume any liability arising out of the application or use of any product or Japan: circuit, and specifically disclaims any and all liability, including without limitation Freescale Semiconductor Japan Ltd. consequential or incidental damages. “Typical” parameters that may be provided in Freescale Technical Information Center Semiconductor data sheets and/or specifications can and do vary in different applications and 3-20-1, Minami-Azabu, Minato-ku actual performance may vary over time. All operating parameters, including “Typicals”, must Tokyo 106-8573, Japan be validated for each customer application by customer’s technical experts. Freescale 81-3-3440-3569 Semiconductor does not convey any license under its patent rights nor the rights of others. Freescale Semiconductor products are not designed, intended, or authorized for use as Asia/Pacific: components in systems intended for surgical implant into the body, or other applications Freescale Semiconductor Hong Kong Ltd.
    [Show full text]
  • 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].
    [Show full text]
  • An Emerging Architecture in Smart Phones
    International Journal of Electronic Engineering and Computer Science Vol. 3, No. 2, 2018, pp. 29-38 http://www.aiscience.org/journal/ijeecs ARM Processor Architecture: An Emerging Architecture in Smart Phones Naseer Ahmad, Muhammad Waqas Boota * Department of Computer Science, Virtual University of Pakistan, Lahore, Pakistan Abstract ARM is a 32-bit RISC processor architecture. It is develop and licenses by British company ARM holdings. ARM holding does not manufacture and sell the CPU devices. ARM holding only licenses the processor architecture to interested parties. There are two main types of licences implementation licenses and architecture licenses. ARM processors have a unique combination of feature such as ARM core is very simple as compare to general purpose processors. ARM chip has several peripheral controller, a digital signal processor and ARM core. ARM processor consumes less power but provide the high performance. Now a day, ARM Cortex series is very popular in Smartphone devices. We will also see the important characteristics of cortex series. We discuss the ARM processor and system on a chip (SOC) which includes the Qualcomm, Snapdragon, nVidia Tegra, and Apple system on chips. In this paper, we discuss the features of ARM processor and Intel atom processor and see which processor is best. Finally, we will discuss the future of ARM processor in Smartphone devices. Keywords RISC, ISA, ARM Core, System on a Chip (SoC) Received: May 6, 2018 / Accepted: June 15, 2018 / Published online: July 26, 2018 @ 2018 The Authors. Published by American Institute of Science. This Open Access article is under the CC BY license.
    [Show full text]
  • The Xen Port of Kexec / Kdump a Short Introduction and Status Report
    The Xen Port of Kexec / Kdump A short introduction and status report Magnus Damm Simon Horman VA Linux Systems Japan K.K. www.valinux.co.jp/en/ Xen Summit, September 2006 Magnus Damm ([email protected]) Kexec / Kdump Xen Summit, September 2006 1 / 17 Outline Introduction to Kexec What is Kexec? Kexec Examples Kexec Overview Introduction to Kdump What is Kdump? Kdump Kernels The Crash Utility Xen Porting Effort Kexec under Xen Kdump under Xen The Dumpread Tool Partial Dumps Current Status Magnus Damm ([email protected]) Kexec / Kdump Xen Summit, September 2006 2 / 17 Introduction to Kexec Outline Introduction to Kexec What is Kexec? Kexec Examples Kexec Overview Introduction to Kdump What is Kdump? Kdump Kernels The Crash Utility Xen Porting Effort Kexec under Xen Kdump under Xen The Dumpread Tool Partial Dumps Current Status Magnus Damm ([email protected]) Kexec / Kdump Xen Summit, September 2006 3 / 17 Kexec allows you to reboot from Linux into any kernel. as long as the new kernel doesn’t depend on the BIOS for setup. Introduction to Kexec What is Kexec? What is Kexec? “kexec is a system call that implements the ability to shutdown your current kernel, and to start another kernel. It is like a reboot but it is indepedent of the system firmware...” Configuration help text in Linux-2.6.17 Magnus Damm ([email protected]) Kexec / Kdump Xen Summit, September 2006 4 / 17 . as long as the new kernel doesn’t depend on the BIOS for setup. Introduction to Kexec What is Kexec? What is Kexec? “kexec is a system call that implements the ability to shutdown your current kernel, and to start another kernel.
    [Show full text]
  • The Linux 2.4 Kernel's Startup Procedure
    The Linux 2.4 Kernel’s Startup Procedure William Gatliff 1. Overview This paper describes the Linux 2.4 kernel’s startup process, from the moment the kernel gets control of the host hardware until the kernel is ready to run user processes. Along the way, it covers the programming environment Linux expects at boot time, how peripherals are initialized, and how Linux knows what to do next. 2. The Big Picture Figure 1 is a function call diagram that describes the kernel’s startup procedure. As it shows, kernel initialization proceeds through a number of distinct phases, starting with basic hardware initialization and ending with the kernel’s launching of /bin/init and other user programs. The dashed line in the figure shows that init() is invoked as a kernel thread, not as a function call. Figure 1. The kernel’s startup procedure. Figure 2 is a flowchart that provides an even more generalized picture of the boot process, starting with the bootloader extracting and running the kernel image, and ending with running user programs. Figure 2. The kernel’s startup procedure, in less detail. The following sections describe each of these function calls, including examples taken from the Hitachi SH7750/Sega Dreamcast version of the kernel. 3. In The Beginning... The Linux boot process begins with the kernel’s _stext function, located in arch/<host>/kernel/head.S. This function is called _start in some versions. Interrupts are disabled at this point, and only minimal memory accesses may be possible depending on the capabilities of the host hardware.
    [Show full text]
  • Kdump, a Kexec-Based Kernel Crash Dumping Mechanism
    Kdump, A Kexec-based Kernel Crash Dumping Mechanism Vivek Goyal Eric W. Biederman Hariprasad Nellitheertha IBM Linux NetworkX IBM [email protected] [email protected] [email protected] Abstract important consideration for the success of a so- lution has been the reliability and ease of use. Kdump is a crash dumping solution that pro- Kdump is a kexec based kernel crash dump- vides a very reliable dump generation and cap- ing mechanism, which is being perceived as turing mechanism [01]. It is simple, easy to a reliable crash dumping solution for Linux R . configure and provides a great deal of flexibility This paper begins with brief description of what in terms of dump device selection, dump saving kexec is and what it can do in general case, and mechanism, and plugging-in filtering mecha- then details how kexec has been modified to nism. boot a new kernel even in a system crash event. The idea of kdump has been around for Kexec enables booting into a new kernel while quite some time now, and initial patches for preserving the memory contents in a crash sce- kdump implementation were posted to the nario, and kdump uses this feature to capture Linux kernel mailing list last year [03]. Since the kernel crash dump. Physical memory lay- then, kdump has undergone significant design out and processor state are encoded in ELF core changes to ensure improved reliability, en- format, and these headers are stored in a re- hanced ease of use and cleaner interfaces. This served section of memory. Upon a crash, new paper starts with an overview of the kdump de- kernel boots up from reserved memory and pro- sign and development history.
    [Show full text]
  • 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
    [Show full text]
  • Renesas RX62N RDK User's Manual
    Renesas Demonstration Kit (RDK) for RX62N User’s Manual: Hardware RENESAS MCU 32 RX Family / RX600 Series / RX62N Group R20UT2531EU0100 All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com). i Disclaimer By using this Renesas Demonstration Kit (RDK), the user accepts the following terms. The RDK is not guaranteed to be error free, and the User assumes the entire risk as to the results and performance of the RDK. The RDK is provided by Renesas on an “as is” basis without warranty of any kind whether express or implied, including but not limited to the implied warranties of satisfactory quality, fitness for a particular purpose, title and non-infringement of intellectual property rights with regard to the RDK. Renesas expressly disclaims all such warranties. Renesas or its affiliates shall in no event be liable for any loss of profit, loss of data, loss of contract, loss of business, damage to reputation or goodwill, any economic loss, any reprogramming or recall costs (whether the foregoing losses are direct or indirect) nor shall Renesas or its affiliates be liable for any other direct or indirect special, incidental or consequential damages arising out of or in relation to the use of this RDK, even if Renesas or its affiliates have been advised of the possibility of such damages.
    [Show full text]