User Guide

Document Number: 333966-003EN

Intel® Quark™ Microcontroller Developer Kit D2000

User Guide May 2016

Intel® Quark™ Microcontroller Developer Kit D2000 User Guide May 2016 2 Document Number: 333966-003EN You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmaps. The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548-4725 or by visiting: /design/literature.htm Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Learn more at / or from the OEM or retailer. No computer system can be absolutely secure. Intel, Intel Quark, and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries. *Other names and brands may be claimed as the property of others. Copyright © 2016, Intel Corporation. All rights reserved.

MANUAL Release 02.2023Debugging via Intel® DCI User´s GuideDebugging via Intel® DCI User´s Guide | 2©1989-2023 Lauterbach Debugging via Intel® DCI User´s GuideTRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... Intel® DCI [Direct Connect Interface] .......................................................................................... Debugging via Intel® DCI User´s Guide ...................................................................................1 Introduction .............................................................................................................................4 4-wire DCI OOB4 DCI OOB Hardware6 DCI DbC7 Target System Requirements8 Related Documents8 Start a TRACE32 Session using Intel® DCI ..........................................................................9 Prepare Your Target9 Connecting to an Intel® SoC using DCI OOB9 Connecting to an Intel® Client or Server System using DCI OOB10 Connecting to an Intel® SoC using DCI DbC11 Connecting to an Intel® Client or Server System using DCI DbC12 Troubleshooting ......................................................................................................................13 DCI error: no response to connect pattern13 Could not stop the target13 Target Power Fail13 Intel® DCI Specific Commands ..............................................................................................14 DCICommands to configure the Intel® DCI trace handler14 DCI.DESTinationSet trace destination14 DCI.ONEnable trace handler14 DCI.OFFDisable trace handler15 SYStem.DCIIntel® DCI specific SYStem commands16 SYStem.DCI.BridgeSelect DCI bridge16 SYStem.DCI.BssbClockConfigure DCI OOB clock rate16 SYStem.DCI.CKDIroutingRouting of the CK and DI signals17 SYStem.DCI.DisCONnectForce DCI disconnect17 SYStem.DCI.DOroutingRouting of the DO signals18 SYStem.DCI.PortPowerConfigure VBUS19 SYStem.DCI.TimeOutConfigure timeouts of internal operations20 Intel® DCI Specific Functions ................................................................................................21Debugging via Intel® DCI User´s Guide | 3©1989-2023 Lauterbach In This Section21 SYStem.DCI.Bridge()Currently selected DCI bridge21 SYStem.DCI.BssbClock()Currently selected DCI OOB clock21 SYStem.DCI.TIMEOUT()Timeouts of internal operations22Debugging via Intel® DCI User´s Guide | 4©1989-2023 Lauterbach Debugging via Intel® DCI User´s GuideVersion 10-Feb-2023IntroductionThe Intel® Direct Connect Interface (DCI) allows debugging of Intel® targets using the USB3 port. The technology supports debugging via the USB Stack (DCI DbC) as well as a dedicated protocol using a USB3 connector only (DCI OOB).4-wire DCI OOBDCI OOB uses a special protocol on the USB3 pins. This makes the mode independent of the actual USB implementation on the target board. This allows debugging of cold boot scenarios, reset flows, and sleep states.The figure above illustrates a typical setup. A Power Debug Module with a CombiProbe and a Whisker Cable DCI OOB (LA-4515) [A] is connected to the debug host running TRACE32 PowerView. On the target side the Whisker Cable DCI OOB connects to a USB port of the target system using a short USB cable [B].TRACE32 sends DCI commands encoded in the DCI OOB protocol to the target system. In the target system the commands are decoded by the OOB module and forwarded to the DCI module where they are translated to JTAG sequences. These JTAG sequences allow to access the internal TAP of the SoC/PCH as well as externally connected JTAG devices (e.g., the CPU of a client or server system).ABDebugging via Intel® DCI User´s Guide | 5©1989-2023 Lauterbach Trace data can be exported through the DCI module and recorded by the CombiProbe.Debugging via Intel® DCI User´s Guide | 6©1989-2023 Lauterbach DCI OOB HardwareIn the following the available DCI OOB hardware is shown.Whisker Cable DCI OOB for CombiProbe Version 1Whisker Cable DCI OOB for CombiProbe Version 2AUSB cable to target systemDUSB connector for target systemBVBUS jumperE34-pin expansion connector (proprietary)CCable to CombiProbeAUSB cable to target systemDUSB connector for target systemBVBUS sliderE34-pin expansion connector (proprietary)CCable to CombiProbeABCEDABCDEDebugging via Intel® DCI User´s Guide | 7©1989-2023 Lauterbach DCI DbCDCI DbC allows debugging using the OS USB stack.The figure above illustrates a typical setup. TRACE32 only runs on the debug host. The target system connects to the debug host using a USB cable.TRACE32 sends DCI commands encoded in the USB protocol to the target system using libusb and the USB Stack of the operating system. In the target system the commands are decoded by the USB implementation and forwarded to the DCI module where they are translated to JTAG sequences. These JTAG sequences allow to access the internal TAP of the SoC/PCH as well as externally connected JTAG devices (e.g., the CPU of a client or server system).Trace data can be directly exported via USB and recorded by TRACE32 on the debug host. DCI DbC also provides a DMA capability for fast download of the system RAM. Support of these capabilities by TRACE32 depends on the used target system.For using DCI DbC, please observe the “System Requirements” (usbdebug_user.pdf).

Live Optics

Make IT decisions with confidence

Sizing IT systems for performance and capacity can be complex, imprecise and costly if done

incorrectly. To help guide our customers through mission critical decisions, Dell EMC’s team of

solution experts developed LIVE OPTICS, an innovative and complimentary tool that reduces the

guesswork involved in data center expansion and troubleshooting. Through a simply-run program,

LIVE OPTICS collects data from your environment and produces a report that gives you the

confidence and knowledge you need to make the right decisions for your business.

This tool is available at no charge and will help you make the most impactful resource decisions,

whether it’s eliminating system bottlenecks or analyzing opportunities for virtualization or data

center expansion. With LIVE OPTICS, you get an accurate sense of your current IT environment

User Guide Including the ADMIRALTY Information Overlay S-63 Edition 1.1 Version 3.4

2 1 Quick Start Guide 3 Electronic Navigational Charts (ENCs) 3 Before You Start 3 ECDIS Containing Existing ENCs 3 Step 1: Install the Public Key 4 Step 2: Install Permits 4 Step 3: Install AVCS ENCs 4 Step 4: Update AVCS 4 Step 5: Install the ADMIRALTY Information Overlay 5 Step 6: Maintain your Holdings 5 2 ADMIRALTY Vector Chart Service Overview 6 2.1 Introduction 6 2.2 AVCS Overview 6 2.3 Quality 6 2.4 Carriage Compliant 6 2.5 Electronic Navigational Charts 6 2.6 Licensing 6 3 Getting Started 7 3.1 General 7 3.2 Media formats for AVCS 7 3.3 New AVCS Customers 7 3.4 The AVCS Licence 8 3.5 The ‘Schedule A’ 8 3.6 Data Cleansing 9 3.7 Public Key 9 4 Installing and Maintaining the Chart Outfit 10 4.1 New ENC Permits 10 4.2 Updating 10 4.3 Base Discs 10 4.4 README.TXT File 10 4.5 Cancelled ENCs 11 4.6 Adding Chart Coverage 11 5 ADMIRALTY Information Overlay 12 6 S-58 Recommended ENC Validation Checks 13 6.1 Important Information for Users 13 7 Security Scheme Errors (SSE) 14 7.1 Common Error Codes 14 7.2 Decryption Failure 14 7.3 Conversion Errors 14 8 Getting Help 16 8.1 Technical Support 16 8.2 Feedback 17 UKHO 2016 All Rights Reserved The copyright in this document, which contains information of a proprietary nature, is vested in UKHO. The content of this document may not be used for purposes other than that for which it has been supplied and may not be reproduced, either wholly or in part, in any way whatsoever.