DOCSLIB.ORG

ENT-AN1144-4.00 Application Note SPI Flash Design for Vcore-III

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ENT-AN1144-4.00 Application Note SPI Flash Design for Vcore-III ENT-AN1144-4.00 Application Note SPI Flash Design for VCore-III Microsemi makes no warranty, representation, or guarantee regarding the information contained herein or the suitability of its products and services for any particular purpose, nor does Microsemi assume any liability whatsoever arising out of the application or use of any product or circuit. The products sold hereunder and any other products sold by Microsemi have been subject to limited testing and should not be used in conjunction with mission-critical equipment or applications. Any performance specifications are believed to be reliable but are not verified, and Buyer must conduct and complete all performance and other testing of the products, alone and together with, or installed in, any end-products. Buyer shall not Microsemi Corporate Headquarters rely on any data and performance specifications or parameters provided by Microsemi. It is the Buyer's responsibility to One Enterprise, Aliso Viejo, independently determine suitability of any products and to test and verify the same. The information provided by Microsemi CA 92656 USA hereunder is provided “as is, where is” and with all faults, and the entire risk associated with such information is entirely Within the USA: +1 (800) 713-4113 with the Buyer. Microsemi does not grant, explicitly or implicitly, to any party any patent rights, licenses, or any other IP Outside the USA: +1 (949) 380-6100 rights, whether with regard to such information itself or anything described by such information. Information provided in this Fax: +1 (949) 215-4996 document is proprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in this Email: [email protected] document or to any products and services at any time without notice. www.microsemi.com About Microsemi © 2019 Microsemi Corporation. All Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductor and system solutions for aerospace & defense, communications, data center and industrial markets. Products include high-performance and rights reserved. Microsemi and the radiation-hardened analog mixed-signal integrated circuits, FPGAs, SoCs and ASICs; power management products; Microsemi logo are trademarks of timing and synchronization devices and precise time solutions, setting the world's standard for time; voice processing Microsemi Corporation. All other devices; RF solutions; discrete components; enterprise storage and communication solutions, security technologies and trademarks and service marks are the scalable anti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well as custom design property of their respective owners. capabilities and services. Microsemi is headquartered in Aliso Viejo, California, and has approximately 4,800 employees globally. Learn more at www.microsemi.com. VPPD-04306. 1.0 8/19 Contents 1 Revision History . 1 1.1 Revision 1.0 . 1 2 Flash Design for VCore-III . 2 2.1 Hardware Design . 2 2.1.1 Flash Support . 2 2.2 Flash Programming . 2 2.2.1 Installing Software from Scratch: How to Flash a Board . 3 2.2.2 Upgrading Software from Within an Existing Installation . 3 2.2.3 Updating an Existing Board with New RedBoot (CLI) . 3 2.3 Flash Layout . 3 2.3.1 Flash Layout (32 MB) . 4 2.3.2 Flash Layout (16 MB) . 4 2.4 Creating a Flash Image . 4 2.5 Flash Size Recommendations . 6 VPPD-04306 ENT-AN1144-4.00 Application Note Revision 1.0 iii Tables Table 1 Flash Layout Detail (32 MB) . 4 Table 2 Flash Layout Detail (16 MB) . 4 Table 3 Recommended Flash Size . 6 VPPD-04306 ENT-AN1144-4.00 Application Note Revision 1.0 iv Revision History 1 Revision History The revision history describes the changes that were implemented in the document. The changes are listed by revision, starting with the most current publication. 1.1 Revision 1.0 Revision 1.0 was the first publication of this document. VPPD-04306 ENT-AN1144-4.00 Application Note Revision 1.0 1 Flash Design for VCore-III 2 Flash Design for VCore-III This document provides guidelines for designing the SPI NOR flash and NAND flash on a Microsemi Enterprise or Carrier Ethernet switch. It includes hardware design and RedBoot bootloader update guidelines and is relevant for all VCore-III based Ethernet switches. 2.1 Hardware Design The Vcore-III CPU boots from the Serial Interface (SI) and Serial Peripheral Interface (SPI). Initially the CPU uses 24-bit addressing for accessing 16 MB of data, but it can access a larger data area using 32-bit addressing after initial boot. Accessing the SPI NOR flash in 32-bit addressing mode is done under full CPU control (bit-banging). To make sure the SPI NOR flash is brought back to 24-bit addressing mode after a reset, the flash reset should be connected to the switch reset signal through a resistor. For SPI flash programming, a pin header can be used for connecting a flash programmer. The switch reset signal needs to be held low for tri-stating the switch and allowing the flash programmer control of the SPI signals. In this case, the flash reset should not be active. For chip selecting the SPI NOR flash, SI_nEN is used. To extend the total flash memory, NAND flash can be added. NANAD flash are available with both parallel and SPI interface. See the actual reference design for detailed design. Note: NAND flash is only supported under Linux OS, and not by the RedBoot bootloader. 2.1.1 Flash Support The bootloader (and eCos OS) supports m25p80 compatible SPI NOR flash and automatically detects the flash sector size and numbers of sectors through jedec id. A list of supported SPI NOR flash types is found at: ecos/packages/devs/flash/spi/m25pxx/current/src/m25pxx.c The Macronix NAND flash driver SPI NAND MX35LF2GE4AB is included in the Linux kernel. The procedures in this document describe the single-chip flash designs. Designs using multiple flash chips are possible, but outside the scope of this document. Adding a new NOR flash type to RedBoot is done by adding the jedec_id/sector_size/sector_count information into ecos/packages/devs/flash/spi/m25pxx/current/src/m25pxx.c Note: Both application code and bootloader need to be recompiled if NOR flash type is updated of added. 2.2 Flash Programming To support the WebStaX software package family, the NOR must be initialized with the following components. • Bootloader (RedBoot) • Configuration sections • Main eCos-based WebStaX image (dual images for fails-safe firmware upgrade) • RedBoot flash partition info (FIS) The process of initializing the NOR for operating the WebStaX software involves using a SPI NOR programmer with flash images created for the desired switch target system. The flash images are generated as described in Creating a Flash Image, page 4. VPPD-04306 ENT-AN1144-4.00 Application Note Revision 1.0 2 Flash Design for VCore-III 2.2.1 Installing Software from Scratch: How to Flash a Board The procedure for installing the software from scratch on a new board involves using a SPI programmer. For more information about the requirements and the procedure, see the AN1184 application note. Although the application note is part of the Linux documentation, the information applies to eCos as well. 2.2.2 Upgrading Software from Within an Existing Installation If the system is already capable of booting and network connectivity, the Web GUI or CLI can be used to update the main application. To update the main application: log in and click Maintenance > Software > Upload, and upgrade using the eCos.dat firmware image. Use the firmware upgrade CLI command to upload the.dat firmware image. A TFTP or HTTP URL might be used to point the network location of the image. The CLI can be accesses by RS232 or SSH. 2.2.3 Updating an Existing Board with New RedBoot (CLI) To update an existing board using CLI, perform the following steps: 1. Ensure that the RedBoot image is available on a TFTP/FTP/HTTP server. 2. Ensure the necessary network connections and IP configuration to create connectivity to the TFTP/FTP/HTTP server. 3. Establish a CLI session on the system to be updated. 4. Enter the debug command enabler: platform debug allow. 5. Execute the debug firmware bootloader <url> CLI command to perform the update. 6. After the update succeeds, restart the device. 7. Identify the new bootloader by the boot banner on the RS232 console. 2.3 Flash Layout Flash is used with the RedBoot flash image system (FIS) and the layout is as shown in Table 1, page 4, Table 2, page 4, and Table 3, page 6. In RedBoot, use the fis list command to display the flash layout. The first area is the RedBoot bootloader, which takes up 32 KB. The next area is the conf used to store board-specific information, such as the MAC address and board ID. Use the following CLI commands to display board data. #platform debug allow #debug board MAC Address: 00-01-c1-00-b6-e0 Board ID: 75 Board Type Conf: 0 Board Type Active: Serval (11) Note: The debug command for older releases is in the vcli. Type debug vcl debug board. • Stackconf contains the switch configuration. • Syslog is the persistent system log that logs system events like port link-up or -down. • Crashfile contains the information stored after a software crash. For dual images (managed and managed.bk), 6 MB is allocated in a 16-MB flash layout and 12 MB is allocated in a 32-MB flash layout. The Diag area is used to store manufacturing diagnostic data. RedBoot reserves some partition names for internal use; namely: RedBoot, Redundant FIS, and FIS directory.
Load more

Recommended publications
  • Embedded Linux Systems with the Yocto Project™
    OPEN SOURCE SOFTWARE DEVELOPMENT SERIES Embedded Linux Systems with the Yocto Project" FREE SAMPLE CHAPTER SHARE WITH OTHERS �f, � � � � Embedded Linux Systems with the Yocto ProjectTM This page intentionally left blank Embedded Linux Systems with the Yocto ProjectTM Rudolf J. Streif Boston • Columbus • Indianapolis • New York • San Francisco • Amsterdam • Cape Town Dubai • London • Madrid • Milan • Munich • Paris • Montreal • Toronto • Delhi • Mexico City São Paulo • Sidney • Hong Kong • Seoul • Singapore • Taipei • Tokyo Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales depart- ment at [email protected] or (800) 382-3419. For government sales inquiries, please contact [email protected]. For questions about sales outside the U.S., please contact [email protected]. Visit us on the Web: informit.com Cataloging-in-Publication Data is on file with the Library of Congress.
    [Show full text]
  • OS-9 for Intel IXDP425 Board Guide
    OS-9® for IXDP425 Board Guide Version 4.7 www.radisys.com Revision A • July 2006 Copyright and publication information Reproduction notice This manual reflects version 4.7 of Microware OS-9. The software described in this document is intended to Reproduction of this document, in part or whole, by any means, be used on a single computer system. RadiSys electrical, mechanical, magnetic, optical, chemical, manual, or Corporation expressly prohibits any reproduction of the otherwise is prohibited, without written permission from RadiSys software on tape, disk, or any other medium except for Microware Communications Software Division, Inc. backup purposes. Distribution of this software, in part or whole, to any other party or on any other system Disclaimer may constitute copyright infringements and misappropriation of trade secrets and confidential The information contained herein is believed to be accurate as of processes which are the property of RadiSys the date of publication. However, RadiSys Corporation will not be Corporation and/or other parties. Unauthorized liable for any damages including indirect or consequential, from distribution of software may cause damages far in use of the OS-9 operating system, Microware-provided software, excess of the value of the copies involved. or reliance on the accuracy of this documentation. The information contained herein is subject to change without notice. July 2006 Copyright ©2006 by RadiSys Corporation All rights reserved. EPC and RadiSys are registered trademarks of RadiSys Corporation. ASM, Brahma, DAI, DAQ, MultiPro, SAIB, Spirit, and ValuePro are trademarks of RadiSys Corporation. DAVID, MAUI, OS-9, OS-9000, and SoftStax are registered trademarks of RadiSys Corporation.
    [Show full text]
  • Building Embedded Linux Systems ,Roadmap.18084 Page Ii Wednesday, August 6, 2008 9:05 AM
    Building Embedded Linux Systems ,roadmap.18084 Page ii Wednesday, August 6, 2008 9:05 AM Other Linux resources from O’Reilly Related titles Designing Embedded Programming Embedded Hardware Systems Linux Device Drivers Running Linux Linux in a Nutshell Understanding the Linux Linux Network Adminis- Kernel trator’s Guide Linux Books linux.oreilly.com is a complete catalog of O’Reilly’s books on Resource Center Linux and Unix and related technologies, including sample chapters and code examples. ONLamp.com is the premier site for the open source web plat- form: Linux, Apache, MySQL, and either Perl, Python, or PHP. Conferences O’Reilly brings diverse innovators together to nurture the ideas that spark revolutionary industries. We specialize in document- ing the latest tools and systems, translating the innovator’s knowledge into useful skills for those in the trenches. Visit con- ferences.oreilly.com for our upcoming events. Safari Bookshelf (safari.oreilly.com) is the premier online refer- ence library for programmers and IT professionals. Conduct searches across more than 1,000 books. Subscribers can zero in on answers to time-critical questions in a matter of seconds. Read the books on your Bookshelf from cover to cover or sim- ply flip to the page you need. Try it today for free. main.title Page iii Monday, May 19, 2008 11:21 AM SECOND EDITION Building Embedded Linux SystemsTomcat ™ The Definitive Guide Karim Yaghmour, JonJason Masters, Brittain Gilad and Ben-Yossef, Ian F. Darwin and Philippe Gerum Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo Building Embedded Linux Systems, Second Edition by Karim Yaghmour, Jon Masters, Gilad Ben-Yossef, and Philippe Gerum Copyright © 2008 Karim Yaghmour and Jon Masters.
    [Show full text]
  • Lecture 2 - Bootloader
    Lecture 2 - Bootloader ¾ ARM architecture overview ¾ Bootloader overview ¾ Case study – UBoot – PART1: Startup – PART2: Monitoring mode – PART3: OS Boot ¾ Available bootloaders for Linux 1 ARM Architecture Overview • ARM Operating Modes – User mode: a normal program execution state – FIQ – Fast Interrupt: for fast interrupt handling – IRQ – Normal Interrupt: for general purpose interrupt handling – Supervisor mode (SVC): a protected mode for operating system – Abort mode: when a data or instruction pre-fetch is aborted – Undefined mode: when an undefined instruction is executed – System mode: a privileged user mode for the operating system • ARM Processor States – Arm state: all instructions are 32bits long, word-aligned. – Thumb state: all instructions are 16 bits wide, half-word aligned. – Jazelle state: all instructions are 8 bits wide for Java Bytecode (for v5TEJ only) 2 ARM Architecture Overview • ARM-State Registers 3 ARM Architecture Overview • Thumb-State Registers 4 ARM Architecture Overview • Program Status Register (PSR) ¾ CPSR: Current Program Status Register ¾ SPSR: Saved Program Status Register 5 ARM Architecture Overview • ARM Exception Types – Reset • Hardware reset: when the processor reset pin is asserted • Software reset: by branching to the reset vector (0x0000) – Undefined instruction • the processor cannot recognize the currently execution instruction – Software Interrupt (SWI) • By s/w instruction, to allow a program running in User mode to request privileged operations that are in Supervisor mode – Prefetch Abort
    [Show full text]
  • Redboot · User Manual
    RedBoot · User Manual RedBoot · User Manual Important hints Thank you very much for purchasing a Garz & Fricke product. Our products are dedicated to professional use and therefore we suppose extended technical knowledge and practice in working with such products. The information in this manual is subject to technical changes, particularly as a result of continuous product upgrades. Thus this manual only reflects the technical status of the products at the time of printing. Before design-in the device into your or your customer’s product, please verify that this document and the therein described specification is the latest revision and matches to the PCB version. We highly recommend contacting our technical sales team prior to any activity of that kind. A good way getting the latest information is to check the release notes of each product and/or service. Please refer to the chapter [Online Support]. The attached documentation does not entail any guarantee on the part of Garz & Fricke GmbH with respect to technical processes described in the manual or any product characteristics set out in the manual. We do not accept any liability for any printing errors or other inaccuracies in the manual unless it can be proven that we are aware of such errors or inaccuracies or that we are unaware of these as a result of gross negligence and Garz & Fricke has failed to eliminate these errors or inaccuracies for this reason. Garz & Fricke GmbH expressly informs that this manual only contains a general description of technical processes and instructions which may not be applicable in every individual case.
    [Show full text]
  • Practical Practical
    PRACTICAL PRACTICAL GPLCOMPLIANCE GPLCOMPLIANCE A GUIDE FOR STARTUPS, SMALL ABUSINESSES GUIDE FOR STARTUPS, AND ENGINEERS SMALL BUSINESSES AND ENGINEERS ARMIJN HEMEL, MSC AND SHANE COUGHLAN ARMIJN HEMEL, MSC AND SHANE COUGHLAN Copyright © 2017 Linux Foundation All rights reserved. This book or any portion thereof may not be reproduced or used in any manner whatsoever without the express written permission of the publisher except for the use of brief quotations in a book review and certain other noncommercial uses permitted by copyright law. Printed in the United States of America First Edition, 2017 ISBN: 978-0-9989078-0-2 1 Letterman Drive Building D Suite D4700 San Francisco CA 94129 Phone/Fax: +1 415 723 9709 https://linuxfoundation.org About the Authors Shane Coughlan Shane Coughlan is an expert in communi- cation, security, and business development. His professional accomplishments include spearheading the licensing team that elevated Open Invention Network into the largest patent non-aggression community in history, establishing the leading professional network of open source legal experts, and aligning stakeholders to launch both the first law journal and the first law book dedicated to open source. He currently leads the OpenChain community as Program Manager. Shane has extensive knowledge of open source governance, internal process development, supply chain management, and community building. His experience includes engagement with the enterprise, embedded, mobile, and automotive industries. Armijn Hemel Armijn Hemel is the owner of Tjaldur Software Governance Solutions. He is an active re- searcher of and internationally recognized expert in open source license compliance and supply chain management. He studied computer science at Utrecht University in The Netherlands, where he pioneered reproducible builds with NixOS.
    [Show full text]
  • Anthony J. Massa
    EMBEDDED SOFTWARE DEVELOPMENT WITH ECOS™ Anthony J. Massa EMBEDDED SOFTWARE DEVELOPMENT WITH ECOS Anthony J. Massa PRENTICE HALL PROFESSIONAL TECHNICAL REFERENCE UPPER SADDLE RIVER, NJ 07458 WWW.PHPTR.COM WWW.PHPTR.COM/MASSA/ Library of Congress Cataloging-in-Publication Data Massa, Anthony J. Embedded software development with eCos / Anthony J. Massa p. cm.--(Bruce Perens' Open source series) ISBN 0-13-035473-2 1. Embedded computer systems--Programming. 2. Application software--Development. 3. Real-time data processing. I. Title. II. Series. QA76.6 .M364317 2002 005.26--dc21 2002035507 Editorial/production supervision: Techne Group Cover design director: Jerry Votta Cover design: Anthony Gemmellaro Art director: Gail Cocker-Bogusz Interior design: Meg Van Arsdale Manufacturing buyer: Maura Zaldivar Editor-in-Chief: Mark L. Taub Editorial assistant: Kate Wolf Marketing manager: Bryan Gambrel Full-service production manager: Anne R. Garcia © 2003 Pearson Education, Inc. Publishing as Prentice Hall Professional Technical Reference Upper Saddle River, New Jersey 07458 This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at <http://www.opencontent.org/openpub/>). Prentice Hall books are widely used by corporations and government agencies for training, marketing, and resale. For information regarding corporate and government bulk discounts please contact: Corporate and Government Sales (800) 382-3419 or [email protected] Other company and product names mentioned herein are the trademarks or registered trademarks of their respective owners. All rights reserved. No part of this book may be reproduced, in any form or by any means, without permission in writing from the publisher.
    [Show full text]
  • Intelligent Medical Device Integration with Real Time Operating System
    Copyright is owned by the Author of the thesis. Permission is given for a copy to be downloaded by an individual for the purpose of research and private study only. The thesis may not be reproduced elsewhere without the permission of the Author. Intelligent Medical Device Integration with Real Time Operating System by © Zaid Jan A thesis submitted to the School of Engineering in partial fulfilment of the requirements for the degree of Master of Engineering Department of Electronics and Computer Syetem Engineering at Massey University, [Albany], New Zealand April 2009 Abstract Many commercial devices now being produced have the ability to be remotely monitored and controlled. This thesis aims to develop a generic platform that can easily be extended to interface with many different kinds of devices for remote monitoring and control via a TCP/IP connection. The deployment will be concentrated on Medical devices but can be extended to all serial device interfaces. The hardware to be used in the development of this platform is an ARM Cortex M3 based Micro-Controller board which has to be designed to meet the requirement set by the Precept Health the founder of this platform. The design was conducted at Massey University in collaboration with senior engineer from the company. The main task in achieving the aim was the development of the necessary software layers to implement remote monitoring and control. The eCosCentric real-time embedded operating system was used to form a generic base for developing applications to monitor and control specific devices. The majority of the work involved in this project was the deployment of the operating system to the Micro-Controller.
    [Show full text]
  • Uboot and Redboot a Compartive Study
    Jeevan Prasath S Tejas Krishna UBOOT AND REDBOOT A COMPARTIVE STUDY Abstract :This Paper attempts to provide the basic understanding of the BIOS and the Boot loader in general and does a comparative study of the two Boot loaders the Redboot and the Uboot .With its main focus on the hardware abstraction layers that are provided by these bootloaders ,which acts as an generic interface between the underlying hardware and the Operating System Software. The paper goes ahead and provides the basic sequences that are followed during the power on startup in each of the boot loaders and the Hardware abstraction layers of the two boot loaders are compared through their interfaces and the standardized modularity through their layers which brings about the compatibility of the boot loaders across all the CPU architectures. In this paper we attempt to study the HAL (Hardware Abstraction Layer) organization for a simple serial device across the two boot loaders. The basic boot up configuration procedure followed for a Beagle Board using the Uboot is also covered as a part of this paper. As a conclusion the paper tries to summarize the need for the HAL and how the standardization of this is achieved in both the boot loaders. The scope of the paper does not cover the need for having different boot loaders with all providing the same services. Introduction: BIOS this stands for the Basic Input and Output System this is a piece of the software that generally resides on the processor chip the main responsibility of this is locate the source of the bootloader that is in which storage device it is available and then give control to the bootloader for its execution.
    [Show full text]
  • Interfacing Freebsd with U-Boot
    Interfacing FreeBSD with U-Boot Rafał Jaworowski [email protected] BSDCan 2008, Ottawa Introduction – TOC ● U-Boot basics ● Overview of FreeBSD booting process ● loader(8) + U-Boot ● New API for standalone applications ● Summary Interfacing FreeBSD with U-Boot BSDCan 2008 Was ist Das U-Boot? ● Firmware – Stored in permanent memory (NOR/NAND FLASH) ● Initial level boot loader ● Configures H/W and starts operating system ● Overall operation – First executing from the permanent memory – Elementary CPU initialization, cache enable/disable, stack fixup etc. – Console – RAM initialization (controller, memory modules) – Relocation to RAM, continue executing from there – Further configuration of a system – Autoboot or interactive loop (user prompt) – No interrupts (polling) Interfacing FreeBSD with U-Boot BSDCan 2008 After relocation to RAM RAM end U-Boot code/data Heap (malloc area) Stack User area Reserved RAM start Interfacing FreeBSD with U-Boot BSDCan 2008 U-Boot highlights ● Written in C and assembly ● Accompanied by helper applications, host tools, documentation ● Self-contained source tree ● Closely tied to Linux – Follows its standards – Coding style – Interfaces (Flattened Device Tree) – License (GPLv2) ● Omnipresent in the PowerPC world, popular on other architecters too ● History: PPCBoot Interfacing FreeBSD with U-Boot BSDCan 2008 Supported systems ● Architectures – ARM, AVR32, BlackFin, ColdFire, MicroBlaze, MIPS, NIOS, PowerPC, SH ● SoCs ● Platforms (boards) – $ ls include/configs/ | wc 423 423 4363 ● Peripherals – FLASH, DRAM chips,
    [Show full text]
  • Standard Bootstrap Firmware Technical Overview Functionality
    Standard Bootstrap Firmware RedBoot™ is a comprehensive debug and bootstrap firmware solution for the development, deployment and management of embedded devices. It supports the installation, execution and debugging of all types of embedded applications, ranging from native stand-alone, proprietary and eCos® RTOS based applications, through to embedded Linux® systems. RedBoot has been adopted by many semiconductor and development board manufacturers as their standard bootstrap firmware. It is the standard firmware shipped with all Intel® XScale® development boards, various Freescale ARM and PowerPC platforms, and NXP set top box reference designs. All major architectures are supported including ARM®, ColdFire®, MIPS®, PowerPC®, SuperH®, XScale® and x86. RedBoot has been deployed in embedded products from ASCOM®, Axis®, HP®, Intel®, Linksys®, Meraki®, NETGEAR®, Watchguard®, Yamaha®, Zyxel® and many others. Most development boards supported by eCosCentric’s eCosPro® Developer’s Kit also include a port of RedBoot. The feature set of RedBoot provides support for all phases of a product’s life-cycle. In the initial development phases it provides a standardized bootstrap and debug environment on commercial development boards and on an OEM’s own prototype hardware. During manufacturing it can provide application installation, power-on self tests (POST), and built-in diagnostic tests to enhance quality control and assurance. Finally, when deployed in products and used in the field, RedBoot provides the system bootstrap mechanism, site specific configuration ability, as well as a straightforward migration path for firmware upgrades. eCosCentric provides a range of commercial RedBoot focused services that cover porting, customization and technical support, simplifying the provision of firmware for your embedded design.
    [Show full text]
  • Building a Linux Image and Downloading Onto I.MX Processors Using a Virtual Machine
    Freescale Semiconductor Document Number: AN3875 Application Note Rev. 1, 08/2009 Building a Linux Image and Downloading onto i.MX Processors Using a Virtual Machine Multimedia Applications Division Freescale Semiconductor, Inc. Detroit, MI A virtual machine (VM) is a software Contents implementation of a machine (computer) that 1 Introduction .................................................. 2 executes programs like a real machine. This 2 Creating a Virtual Machine ............................ 5 application note specifies the following: 3 Installing VM Player....................................... 9 • The details of how to create a virtual 4 Installing Debian in the Virtual Machine ..... 14 machine using open source software 5 Install Freescale LTIB for i.MX Processors . 41 Appendix A i.MX51 Bootlog ............................ 59 on a Windows machine. • Installation of Debian Linux on this virtual machine. • Installation of Linux Target Image Builder (LTIB) on the virtual machine and set up the host to TFTP files on the target. © Freescale Semiconductor, Inc., 2009. All rights reserved. _______________________________________________________________________ 1 Introduction This document details the following steps using open source tools and Freescale provided board support packages. • Creating a virtual machine using open source software on a Windows machine • Installing Debian Linux on this virtual machine • Installing Linux Target Image Builder (LTIB) on the virtual machine and setting up the host to TFTP files on the target 1.1 Scope This document is meant to serve as a step-by-step guide for hardware and software engineers to create their own virtual machines, install Linux on it, and create their own Linux image to be downloaded onto i.MX processors. 1.2 Overview This section includes a brief introduction to virtual machines, discusses different embedded operating systems, and presents how they fit into the i.MX development environment.
    [Show full text]