DOCSLIB.ORG

OEM Cobranet Module Design Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
OEM Cobranet Module Design Guide CDK-8 OEM CobraNet Module Design Guide Date 8/29/2008 Revision 1.1 © Attero Tech, LLC 1315 Directors Row, Suite 107, Ft Wayne, IN 46808 Phone 260-496-9668 • Fax 260-496-9879 620-00001-01 CDK-8 Design Guide Contents 1 – Overview .....................................................................................................................................................................................................................................2 1.1 – Notes on Modules .................................................................................................................................................... 2 2 – Digital Audio Interface Connectivity...........................................................................................................................................................................3 2.1 – Pin Descriptions ....................................................................................................................................................... 3 2.1.1 - Audio clocks ..................................................................................................................................................... 3 2.1.2 – Digital audio..................................................................................................................................................... 3 2.1.3 – Serial bridge ..................................................................................................................................................... 4 2.1.4 – Control............................................................................................................................................................. 4 2.1.5 – Power ............................................................................................................................................................... 4 2.2 – Reference design...................................................................................................................................................... 4 3 – HMI Interfacing.....................................................................................................................................................................................................................13 3.1 – External Memory Bus Example................................................................................................................................ 13 3.1.1 – Schematic diagrams........................................................................................................................................ 13 3.1.2 – Software notes................................................................................................................................................ 15 3.1.3 – Source Code - ‘C’ file ...................................................................................................................................... 15 3.1.4 – Source code - header file ................................................................................................................................ 20 3.2 – GPIO Port Example ................................................................................................................................................. 21 3.2.1 – Schematic diagram ......................................................................................................................................... 21 3.2.2 – Software notes................................................................................................................................................ 22 3.2.3 – HMI Setup and Initialization............................................................................................................................ 23 3.2.4 – HMI Driver – Header file.................................................................................................................................. 23 3.2.5 – HMI Driver – ‘C’ code...................................................................................................................................... 24 4 – PCB Design Guidelines .....................................................................................................................................................................................................32 4.1 – Power Supply.......................................................................................................................................................... 32 4.2 – Clock Termination.................................................................................................................................................. 32 4.3 – Clock signal parallel end termination ..................................................................................................................... 32 4.4 – Grounding.............................................................................................................................................................. 32 4.5 – Signal Separation.................................................................................................................................................... 32 4.6 – Chassis Grounding ................................................................................................................................................. 32 5 – End Product Bring-up hints............................................................................................................................................................................................33 5.1 – Power Supplies ....................................................................................................................................................... 33 5.2 – Clocks and I2S lines ............................................................................................................................................... 33 5.3 – Ethernet LED activity............................................................................................................................................... 33 APPENDIX A – CDK-8DUART SHMI message protocol........................................................................................................................................... A-1 A1 – Terminology........................................................................................................................................................... A-1 A2 – System Description ................................................................................................................................................ A-2 A3 – Serial Format.......................................................................................................................................................... A-3 A3.1 – Message Format ............................................................................................................................................. A-3 A3.2 – Read Messages............................................................................................................................................... A-4 A3.3 – Write Messages .............................................................................................................................................. A-5 A3.4 – Baud Rate Change Message ............................................................................................................................ A-6 A3.5 – NACK Response Descriptions ......................................................................................................................... A-6 A4 – Commands & Responses ........................................................................................................................................ A-8 A4.1 – Legend ........................................................................................................................................................... A-9 A4.2 – sysDescr......................................................................................................................................................... A-9 A4.3 – sysContact ..................................................................................................................................................... A-9 A4.4 – sysName ........................................................................................................................................................ A-9 A4.5 – sysLocation .................................................................................................................................................. A-10 A4.6 – ifPhysAddress............................................................................................................................................... A-10 A4.7 – flashPersistEnable ........................................................................................................................................ A-10 A4.8 – errorCode..................................................................................................................................................... A-10 A4.9 – errorCount ................................................................................................................................................... A-10 A4.10 – modeRateControl ....................................................................................................................................... A-11 A4.11 – conductorStatus ........................................................................................................................................
Load more

Recommended publications
  • Lecture 10: Switching & Internetworking
    Lecture 10: Switching & Internetworking CSE 123: Computer Networks Alex C. Snoeren HW 2 due WEDNESDAY Lecture 10 Overview ● Bridging & switching ◆ Spanning Tree ● Internet Protocol ◆ Service model ◆ Packet format CSE 123 – Lecture 10: Internetworking 2 Selective Forwarding ● Only rebroadcast a frame to the LAN where its destination resides ◆ If A sends packet to X, then bridge must forward frame ◆ If A sends packet to B, then bridge shouldn’t LAN 1 LAN 2 A W B X bridge C Y D Z CSE 123 – Lecture 9: Bridging & Switching 3 Forwarding Tables ● Need to know “destination” of frame ◆ Destination address in frame header (48bit in Ethernet) ● Need know which destinations are on which LANs ◆ One approach: statically configured by hand » Table, mapping address to output port (i.e. LAN) ◆ But we’d prefer something automatic and dynamic… ● Simple algorithm: Receive frame f on port q Lookup f.dest for output port /* know where to send it? */ If f.dest found then if output port is q then drop /* already delivered */ else forward f on output port; else flood f; /* forward on all ports but the one where frame arrived*/ CSE 123 – Lecture 9: Bridging & Switching 4 Learning Bridges ● Eliminate manual configuration by learning which addresses are on which LANs Host Port A 1 ● Basic approach B 1 ◆ If a frame arrives on a port, then associate its source C 1 address with that port D 1 ◆ As each host transmits, the table becomes accurate W 2 X 2 ● What if a node moves? Table aging Y 3 ◆ Associate a timestamp with each table entry Z 2 ◆ Refresh timestamp for each
    [Show full text]
  • 802.11 BSS Bridging
    802.11 BSS Bridging Contributed by Philippe Klein, PhD Broadcom IEEE 8021/802.11 Study Group, Aug 2012 new-phkl-11-bbs-bridging-0812-v2 The issue • 802.11 STA devices are end devices that do not bridge to external networks. This: – limit the topology of 802.11 BSS to “stub networks” – do not allow a (STA-)AP-STA wireless link to be used as a connecting path (backbone) between other networks • Partial solutions exist to overcome this lack of bridging functionality but these solutions are: – proprietary only – limited to certain type of traffic – or/and based on Layer 3 (such IP Multicast to MAC Multicast translation, NAT - Network Address Translation) IEEE 8021/802.11 Study Group - Aug 2012 2 Coordinated Shared Network (CSN) CSN CSN Network CSN Node 1 Node 2 Shared medium Logical unicast links CSN CSN Node 3 Node 4 • Contention-free, time-division multiplexed-access, network of devices sharing a common medium and supporting reserved bandwidth based on priority or flow (QoS). – one of the nodes of the CSN acts as the network coordinator, granting transmission opportunities to the other nodes of the network. • Physically a shared medium, in that a CSN node has a single physical port connected to the half-duplex medium, but logically a fully-connected one-hop mesh network, in that every node can transmit frames to every other node over the shared medium. • Supports two types of transmission: – unicast transmission for point-to-point (node-to-node) – transmission and multicast/broadcast transmission for point-to-multipoint (node-to-other/all-nodes) transmission.
    [Show full text]
  • ISDN LAN Bridging Bhi
    ISDN LAN Bridging BHi Tim Boland U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 QC 100 NIST .U56 NO. 5532 199it NISTIR 5532 ISDN LAN Bridging Tim Boland U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 November 1994 U.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director DATE DUE - ^'' / 4 4 ' / : .f : r / Demco, Inc. 38-293 . ISDN LAN BRIDGING 1.0 Introduction This paper will provide guidance which will enable users to properly assimilate Integrated Services Digital Network (ISDN) local area network (LAN) bridging products into the workplace. This technology is expected to yield economic, functional and performance benefits to users. Section 1 (this section) provides some introductory information. Section 2 describes the environment to which this paper applies. Section 3 provides history and status information. Section 4 describes service features of some typical product offerings. Section 5 explains the decisions that users have to make and the factors that should influence their decisions. Section 6 deals with current ISDN LAN bridge interoperability activities. Section 7 gives a high-level summary and future direction. 2.0 ISDN LAN Bridging Environment 2 . 1 User Environment ISDN LAN bridge usage should be considered by users who have a need to access a LAN or specific device across a distance of greater than a few kilometers, or by users who are on a LAN and need to access a specific device or another network remotely, and, for both situations, have or are considering ISDN use to accomplish this access.
    [Show full text]
  • Bridging Strategies for LAN Internets Previous Screen Nathan J
    51-20-36 Bridging Strategies for LAN Internets Previous screen Nathan J. Muller Payoff As corporations continue to move away from centralized computing to distributed, peer-to- peer arrangements, the need to share files and access resources across heterogeneous networks becomes all the more necessary. The need to interconnect dissimilar host systems and LANs may arise from normal business operations or as the result of a corporate merger or acquisition. Whatever the justification, internetworking is becoming ever more important, and the interconnection device industry will grow for the rest of the decade. Introduction The devices that facilitate the interconnection of host systems and LANs fall into the categories of repeaters , bridges, routers, and gateways. Repeaters are the simplest devices and are used to extend the range of LANs and other network facilities by boosting signal strength and reshaping distorted signals. Gateways are the most complex devices; they provide interoperability between applications by performing processing-intensive protocol conversions. In the middle of this “complexity spectrum” are bridges and routers. At the risk of oversimplification, traditional bridges implement basic data-level links between LANs that use identical protocols; traditional routers can be programmed for multiple network protocols, thereby supporting diverse types of LANs and host systems over the same WAN facility. However, in many situations the use of routers is overkill and needlessly expensive; routers cost as much as $75,000 for a full-featured, multiport unit, compared with $6,000 to $30,000 for most bridges. The price difference is attributable to the number of protocols supported, the speed of the Central Processing Unit, port configurations, WAN interfaces, and network management features.
    [Show full text]
  • Bridging Internetwork Operating System Release 10.2
    Internetwork Operating System Release 10.2 cisc EM Bridging Software Release O2 September 1994 Corporate Headquarters 170 West Tasman Drive San Jose CA 95134-1706 USA Phone 408 526-4000 Fax 408 526-4100 Customer Order Number TRN-IRSC-1O.2 Text Part Number 2O91O1 The and and other technical information the products specifications configurations regarding products contained in this manual are subject to change without notice Alt statements technical information and recommendations contained in this manual are believed to be accurate and reliable but are without of and must take full for their presented warranty any kind express or implied users responsibility application of any products specified in this manual This radiate radio if not installed and used in equipment generates uses and can frequency energy and accordance with the instruction manual for this device may cause interference to radio communications This equipment has been tested and found to comply with the limits for Class computing device which reasonable pursuant to Subpart of Part 15 of FCC Rules are designed to provide protection against such interference when operated in commercial environment of this in residential is in which their Operation equipment area likely to cause interference case users at own expense will be required to take whatever measures may be required to correct the interference will The following third-party software may be included with your product and be subject to the software license agreement The Cisco implementation of TCP header compression
    [Show full text]
  • Understanding Linux Internetworking
    White Paper by David Davis, ActualTech Media Understanding Linux Internetworking In this Paper Introduction Layer 2 vs. Layer 3 Internetworking................ 2 The Internet: the largest internetwork ever created. In fact, the Layer 2 Internetworking on term Internet (with a capital I) is just a shortened version of the Linux Systems ............................................... 3 term internetwork, which means multiple networks connected Bridging ......................................................... 3 together. Most companies create some form of internetwork when they connect their local-area network (LAN) to a wide area Spanning Tree ............................................... 4 network (WAN). For IP packets to be delivered from one Layer 3 Internetworking View on network to another network, IP routing is used — typically in Linux Systems ............................................... 5 conjunction with dynamic routing protocols such as OSPF or BGP. You c an e as i l y use Linux as an internetworking device and Neighbor Table .............................................. 5 connect hosts together on local networks and connect local IP Routing ..................................................... 6 networks together and to the Internet. Virtual LANs (VLANs) ..................................... 7 Here’s what you’ll learn in this paper: Overlay Networks with VXLAN ....................... 9 • The differences between layer 2 and layer 3 internetworking In Summary ................................................. 10 • How to configure IP routing and bridging in Linux Appendix A: The Basics of TCP/IP Addresses ....................................... 11 • How to configure advanced Linux internetworking, such as VLANs, VXLAN, and network packet filtering Appendix B: The OSI Model......................... 12 To create an internetwork, you need to understand layer 2 and layer 3 internetworking, MAC addresses, bridging, routing, ACLs, VLANs, and VXLAN. We’ve got a lot to cover, so let’s get started! Understanding Linux Internetworking 1 Layer 2 vs.
    [Show full text]
  • XMOS for AVB Ethernet Based Networking for Audio/Video
    Only a few years ago, computer networks were complex beasts tended by special acolytes and running on different standards. Today they have become commonplace in many homes and offices, simply plugged together using Ethernet technology. The same revolutionary change is coming for Audio/Video (AV) networking, as AVB (Audio XMOS for AVB: Video Bridging) products that run over the same network, Ethernet based networking begin to enter the market. for Audio/Video Putting together networks of AV equipment for professional and consumer use, or for use in How Ethernet Works vehicles, is about to become simpler while also Within Ethernet, data is transmitted between delivering better quality. No longer will devices (such as a computer and a printer) in specialist connectors and cables be needed to packets. Each packet carries one or more create a rats' nest of connectivity. Instead addresses for its destination. Like a postal packet traversing the postal system, the network has no Audio Video Bridging (AVB), a set of knowledge of what is in the packet, but uses the international standards, will make setting up address to pass the packet to the next point in the and managing networks almost as simple as network. just plugging together the different elements. In an Ethernet based network, each endpoint Sound and video sources will be mixed and (computer, storage element, printer etc.) is distributed to screens and speakers, with high identified by a unique address and has a single quality, low latency and tight synchronization. connection to the network, through an Ethernet Furthermore, the connectors and cables are switch.
    [Show full text]
  • IED GLOBALCOM Installation Instructions IED Announcement Control System
    IED GLOBALCOM Installation Instructions IED Announcement Control System IED1100 / IED1200 REV: 06-13 DOC1201B ©2013, Innovative Electronic Designs, LLC IED GLOBALCOM IED1100 / IED1200 INSTALLATION INSTRUCTIONS Copyright © 2013 Innovative Electronic Designs, LLC. All Rights Reserved If this document is distributed with software that includes an end user agreement, this document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permit- ted by any such license, no part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, storage in an information retrieval system, or otherwise, without the prior written permission of Innovative Electronic Designs, LLC. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this document is furnished for informational use only and is subject to change without notice. It should not be con- strued as a commitment by Innovative Electronic Designs, LLC. Innovative Electronic Designs, LLC assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this document. Any reference to company names in examples are for demonstration purposes only and are not intended to refer to any actual organization or an endorsement of any kind. Innovative Electronic Designs, IED, 500ACS, 500ACS Announcement Control System, CAS, Courtesy Announcement System, T-CAS, FAS, Flight Announcement System, IED On Call, IED On Call & Design, and LANcom are all registered trademarks or trade- marks of Innovative Electronic Designs, LLC in the United States and/or other countries.
    [Show full text]
  • Calrec Network Primer V2
    CALREC NETWORK PRIMER V2 Introduction to professional audio networks - 2017 edition Putting Sound in the Picture calrec.com NETWORK PRIMER V2 CONTENTS Forward 5 Introduction 7 Chapter One: The benefits of networking 11 Chapter Two: Some technical background 19 Chapter Three: Routes to interoperability 23 Chapter Four: Control, sync and metadata over IP 27 The established policy of Calrec Audio Ltd. is to seek improvements to the design, specifications and manufacture of all products. It is not always possible to provide notice outside the company of the alterations that take place continually. No part of this manual may be reproduced or transmitted in any form or by any means, Despite considerable effort to produce up to electronic or mechanical, including photocopying date information, no literature published by and scanning, for any purpose, without the prior the company nor any other material that may written consent of Calrec Audio Ltd. be provided should be regarded as an infallible Calrec Audio Ltd guide to the specifications available nor does Nutclough Mill Whilst the Company ensures that all details in this it constitute an offer for sale of any particular Hebden Bridge document are correct at the time of publication, product. West Yorkshire we reserve the right to alter specifications and England UK equipment without notice. Any changes we make Apollo, Artemis, Summa, Brio, Hydra Audio HX7 8EZ will be reflected in subsequent issues of this Networking, RP1 and Bluefin High Density Signal document. The latest version will be available Processing are registered trade marks of Calrec Tel: +44 (0)1422 842159 upon request.
    [Show full text]
  • Improving Mobile IP Handover Latency on End-To-End TCP in UMTS/WCDMA Networks
    Improving Mobile IP Handover Latency on End-to-End TCP in UMTS/WCDMA Networks Chee Kong LAU A thesis submitted in fulfilment of the requirements for the degree of Master of Engineering (Research) in Electrical Engineering School of Electrical Engineering and Telecommunications The University of New South Wales March, 2006 CERTIFICATE OF ORIGINALITY I hereby declare that this submission is my own work and to the best of my knowledge it contains no materials previously published or written by another person, nor material which to a substantial extent has been accepted for the award of any other degree or diploma at UNSW or any other educational institution, except where due acknowledgement is made in the thesis. Any contribution made to the research by others, with whom I have worked at UNSW or elsewhere, is explicitly acknowledged in the thesis. I also declare that the intellectual content of this thesis is the product of my own work, except to the extent that assistance from others in the project's design and conception or in style, presentation and linguistic expression is acknowledged. (Signed)_________________________________ i Dedication To: My girl-friend (Jeslyn) for her love and caring, my parents for their endurance, and to my friends and colleagues for their understanding; because while doing this thesis project I did not manage to accompany them. And Lord Buddha for His great wisdom and compassion, and showing me the actual path to liberation. For this, I take refuge in the Buddha, the Dharma, and the Sangha. ii Acknowledgement There are too many people for their dedications and contributions to make this thesis work a reality; without whom some of the contents of this thesis would not have been realised.
    [Show full text]
  • AES67 Standard and What It Means for the AV Industry
    TECH TALK 78 Systems Integration Asia August - September 2015 About AES67 Standard And What It Means For The AV Industry AES67 is not intended to replace existing solutions, but to offer means for interoperability among them Many of you would have heard about the AES67 standard that was developed by the Audio Engineering Society and published in September 2013. To promote the adoption of AES67, The Media Networking Alliance (MNA) was formed in October 2014. SI Asia speaks to Andreas Hildebrand,Senior Product Manager at ALC NetworX GmbH, the company that is responsible for RAVENNA networking technologies and also a member of MNA, to know more about AES67. What is AES67 all about? guidelines. A prerequisite was not In the overall audio eco- What loophole or space is to invent yet another, completely system, how does AES67 this meant to fill which was new solution, but to try to identify and the solutions fit into the not previously available? commonalities among the existing picture? AES67 is a standard published by solutions and use available technology The advantage of having an the Audio Engineering Society on standards and protocols already interoperability standard for various September 11th, 2013, addressing employed. The idea was to allow solutions is obvious: while there may be “High-performance Streaming Audio- current solution providers to adopt a sound ecosystem of products already over-IP Interoperability”. It defines a AES67 with as little effort as possible available for individual solutions, none set of guidelines which provide a basis and provide AES67 interoperability of these solutions can fit all applications for achieving interoperability between either via a special mode of operation areas.
    [Show full text]
  • Bridging Principles
    Bridging Principles 1 By the end of this session you will be able to... n Define bridging modes – Source Routing – Transparent – Source Route Transparent (SRT) n Describe how Spanning Tree functions Token Ring Bridging 2 2 Flexible Frame Forwarding Choice of Techniques Source Route Source Route Transparent Transparent Bridging Bridging Bridging n Transparent u Ethernet and Token Ring u simple to implement u not easy to manage in a complex network n Source Routing u Token Ring u requires management effort to implement u trouble shooting is simplified n SRT u short term combination solution Token Ring Bridging 3 Bridging Techniques Transparent Can be used on both Token Ring and Ethernet networks Nothing is identified so implementation is simple Nothing is identified so locating problems can be difficult on complex networks Source Route Bridging Designed for Token Ring networks Requires each ring and bridge to be identified Locating potential and actual trouble spots is simplified SRT Useful when combing transparent and source routing networks, e.g. when adding a department using ‘the other method’ to a company network. Allows bridges/switches to forward both source routed and transparent frames appropriately. Also allows the bridges/switches to communicate with each other. A short term solution, ultimately MAKE UP YOUR MIND; use source routing OR transparent for the whole network. 3 What is the purpose of a Bridge ? 2 4 1 Ring A Ring B 6 3 5 n Connects two physical rings n Forwards or Filters Frames n Single logical network n Keeps local traffic local Token Ring Bridging 4 Bridges are used to physically connect two rings.
    [Show full text]