Manuals / Company X Accessories / Musical Instruments & Equipment / Electronic Keyboard

Company X Accessories C1030-5510 manual Windows, Requirements, Driver installation, Build UDK

Models: C1030-5510

1 71

Download 71 pages 45.45 Kb

Page 31

Windows

Requirements

To use the UDK in own projects, the following is required:

•Installed drivers

•Microsoft Visual Studio 2005 or 2008; 2010 is experimental

•CMake 2.6 or higher ⇒ http://www.cmake.org

•wxWidgets 2.8.10 or higher (must be build separately) ⇒ http://www.wxwidgets.org [optionally, only if UDKLab should be build]

Driver installation

The driver installation is part of the UDK installation but can run standalone on final customer machines without the need to install the UDK itself. During installation, a choice of drivers to install can be made, so it is not necessary to install i.e. PCI drivers on machines that should run USB devices only or vice versa. If USB drivers get installed on a machine that has a pre-2.0 UDK driver installation, we prefer the option for USB driver cleanup offered by the installer, this cleanly removes all dependencies of the old driver installation.

Note: There are separate installers for 32 and 64 bit systems.

Important: At least one device should be present when installing the drivers !

Build UDK

Prerequisites

The most components of the UDK are part of one large CMake project. There are some options that need to be fixed in msvc.cmake inside the UDK installation root:

•BUILD_UI_TOOLS If 0, UDKLab will not be part of the subsequent build procedure, if 1 it will. This requires an installation of an already built wxWidgets.

•WX_WIDGETS_BASE_PATH Path to wxWidgets build root, only needed if BUILD_UI_TOOLS is not 0.

•USE_STATIC_RTL If 0, all projects are build against the dynamic runtime libraries. This requires the installation of the appropriate Visual Studio redistributable pack on every machine the UDK is used on. Using a static build does not create such dependencies, but will conflict with the standard wxWidgets build configuration.

Solution creation and build

The preferred way is to open a command prompt inside the installation root of the UDK,

USBS6 / C1030-5510		http://www.cesys.com/
User Doc V0.3	-31-	preliminary

Image 31

Company X Accessories C1030-5510 manual Windows, Requirements, Driver installation, Build UDK

Contents

June 29 USBS6 Copyright information Summary of USBS6 Feature listIncluded in delivery XC6SLX16-2CSG324C Fpga features Block DiagramSpartan-6TMFPGA USBS6 Top View Mode Powering USBS6Bus- powered USB is used as power supply input 3V@ ??? mA Modes of operation Jtag connector ConfigurationName USB2.0 controller Signal NameUSB2.0 FX2LPTM Microcontroller Cypresstm CY7C68013A Lpddr Sdram MT46H64M16LFCK-5 External memory MCB1DQ0 SPI Flash MX25L12845EMI-10G Peripherals LEDs HEX rotary DIP switchFpga Pin N8 Fpga Pin M11 Fpga Pin M10 Fpga Pin N9 USB to serial Uart interface External expansion connectorsDirection Comment J3 VG 96-pin external expansion connector J4 IDC 2x25-Pin external expansion connector IDC 2x25-Pin external expansion connector J4 ADDIO16 Clocking Fpga designs Cypress FX-2 LP and USB basics Introduction to example Fpga designs FX-2/FPGA slave Fifo connection ISE Generate Programming File Properties Gen. Opt Fpga source code copyright information Disclaimer of warrantyFpga source code license Files and modules Design usbs6socSrc/wishbonepkg.vhd Src/wbslbram.vhd Src/usbs6soctop.vhdSrc/wbintercon.vhd Src/wbmafx2.vhd Src/xilmcbmig Src/wbslmcb.vhdSrc/wbsluart.vhd Src/xiluartmacro Signals appusbh2ppktcounto70 and appusbp2hpktcounto70 Wishbone transactions Wishbone signals driven by slaves Wishbone signals driven by the master Example Design usbs6bram Usbs6bram.ucf Src/usbs6bramtop.vhdSrc/simtb/wbslbramtb.vhd Usbs6bram.xise Wbslbramtb.cmd Changes to previous versions Introduction Build UDK Driver installationWindows Requirements Lets assume to use c\\udkapi Drivers Linux PCI Makefile creation and build Preliminary Add project to UDK build Use APIs in own projects API Functions in detail API Error handling++ and .NET API Methods/Functions GetLastErrorCodeError code Kind of error GetLastErrorText Init Device enumerationDeInit Static unsigned int ceDeviceGetDeviceCount EnumerateDeviceType Description GetDeviceCount Static ceDevice *ceDeviceGetDeviceunsigned int uiIdx GetDevice GetDeviceName Information gatheringGetUDKVersionString GetDeviceUID Constant Bus GetBusTypeGetMaxTransferSize Void ceDeviceOpen Using devicesOpen Close WriteBlock ReadRegisterWriteRegister ReadBlock ResetFPGA EnableInterruptWaitForInterrupt ProgramFPGAFromMemoryZ SetTimeOutProgramFPGAFromBIN ProgramFPGAFromMemory Void ceDeviceEnableBurstbool bEnable EnableBurst Introduction UDKLab UDKLab Main Screen Main screen Device selection flow Using UDKLab Prepare to work with device Fpga configuration Projects Fpga design flashing Sequence contents Add new initializing task Sequence start Content panel Register panel Register entry Data area panel Data area entry How to store configuration data in SPI-Flash Using SPI-Flash for configuration M25P16 Fpga Connection Jtag Signal Name Direction IO pairing and etch length reportJ3 VG-96 pin connector Differential pairs 28 IN, 12 IN/OUT Net name 52.506 Etch Length mm B18 Direction Fpga Bank Etch Length mm A28 J4 IDC-50 pin connector Differential pairs 17 IN/OUT Addio 42.990 USBS6 mechanical dimensions in mm Mechanical dimensions Table of contents Table of Contents USB PCI ++ API