≡

1. Olimex USB Devices Driver Download For Windows
2. Olimex Usb Devices Driver Download For Windows 10

Installing ARM-USB-OCD - rev.G drivers for Windows 7 First connect your programmer/debugger to your computer, open Device Manager and there you will find your device: Click on the first “Olimex OpenOCD JTAG” with the right button of the mouse and select “Update Driver Software.” After that the following window will appear. LG USB Drivers Ver. 4.5.0 and LG USB Drivers Ver 4.4.2 In this post, you can download and install the latest LG USB Drivers Ver 4.5.0 for your LG Phones or tablets. In order to establish communications between your LG devices and computer, you need to install the latest LG Drivers properly onto your computer.

FEATURES

• First on market three-in-one USB JTAG debugger - offers JTAG + RS232 (full modem signals supported) port + power supply all in one compact device
• Adds virtual RS232 port to your computer with all modem signals like: DTR, DSR, DCD, RTS, CTS, Rx, Tx
• Debugs all ARM microcontrollers with JTAG interface supported by OpenOCD
• Can be used to power your target board with three jumper-selectable power supplies: 5V, 9V and 12VDC; USB source current is limited with resetable fuse at 300mA, at the different output voltages the maximum current is different: 5V/200mA, 9V/100mA, 12V/70mA, note that this also depends on your USB host current capabilities, if other USB devices are attached to your computer or if the laptop is running on batteries these figures may be different and would depend on your computer USB host. Cable for the external powering included - 2.1x5.5x14mm female connectors at both ends
• Uses ARM's standard JTAG connector (2 rows × 10 pins at 0.1' step)
• Supports ARM targets working in voltage range 2.0 – 5.0 V DC
• Supported by the open-source community and OpenOCD debugger software
• Downloadable Windows installer for full featured and open source tools as alternative to the commercial ARM development packages: GCC C compiler, OpenOCD debugger and Eclipse IDE.
• Works with IAR EW for ARM via GDB server
• Works with Rowley Crossworks IDE
• Works with CooCox IDE
• Supported in Windows, Linux and Mac
• Dimensions 50x40mm ~ (2x1.6)' + 20cm ~ 8' JTAG cable - ribbon cable included

SOFTWARE

• Additional resources: tutorials, instructions, demo software, customer projects, older drivers and more might be found at the wiki page: ARM-USB-OCD article

FAQ

• Can I use ARM-USB-OCD with EW-ARM?
• IAR EW has support for GDB and works with ARM-USB-OCD.

Olimex USB Devices Driver Download For Windows

• I am currently using operating system X. It has FTDI drivers, how should I alter them to work with my installation?
• FTDI provide drivers and instructions at their web site, download them and use our ARM-USB-OCD PID: 0x0003, VID: 0x15BA to install the drivers.

• I have LPC1227 board and can't program it with your OpenOCD debugger. What do I do wrong?
• LPC1227 lacks JTAG according to the microcontroller's datasheet. The board can be programmed only via SWD (Serial Wire Debug) interface. Olimex OpenOCD debuggers have JTAG by default. You would need an addiitonal adapter – ARM-JTAG-SWD.

• How to install ARM-USB-OCD to work with CrossWorks

• Test with the FTDI drivers. The FTDI drivers can be downloaded from the following address:
  https://www.olimex.com/Products/ARM/JTAG/_resources/OLIMEX-FTDI-drivers-2-12-04.zip
  There is already profile for ARM-USB-OCD in CrossWorks but if you want to use it as 'Generic FTD2232' target interface you have to do as follows:

  1. Right click on a blank space in the targets window and select 'New Target Interface > Generic FT2232 Device'.
  2. Right click on the new target interface and select 'Properties' - set the following properties:
     Connected LED Inversion Mask 0x0000
     Connected LED Mask = 0x0800
     nSRST Inversion Mask = 0x0200
     nSRST Mask = 0x0200
     nTRST Inversion Mask = 0x0000
     nTRST Mask = 0x0100
     Output Pins = 0x0F1B
     Output Value = 0x0D08
     Running LED Inversion Mask = 0x0000
     Running LED Mask = 0x0800

  PID: 0x0003
  VID: 0x15BA

  In CrossWorks 1.7 there are Target interfaces for Olimex JTAGs, note that RTCK is not used with a FT2232 design so your JTAG clock should not exceed 1/6 of your target MCU clock or the JTAG will lock up. Start with JTAG divider 10 and decrease until you are able to debug to find your own value for your target.

• Can I debug high voltage targets with ARM-USB-OCD?
• ARM-USB-OCD is not isolated, but you can use a USB-ISO isolator device to protect your PC while debugging high voltage targets.

• Howdy, guys. I can't program my MSP430 and PIC16 boards with your robust debugger. I need help ASAP.
• Technically, it is possible to program targets different than ARM using our OpenOCD debugger. Practically, almost all users use the debugger for ARM programming and only ARM targets are officially supported. There is a reason that the prefix in the name of the debugger is 'ARM-'.

• I am the maintainer of a commercial IDE with custom debugger code. I want to include support for your OpenOCD tools in my software, however I can't find specific information. It is obviously a win-win situation for both parties. Is it possible to provide me with more specific technical information for your debuggers?
• Olimex can provide the necessary information and cooperate with interested parties if they want to add low-cost USB debugger support to their C compilers and IDEs.

Related Products - People who bought this product also bought

ARM debugger with JTAG and SWD interfaces, based on CoLinkEX

High-speed 3-IN-1 fast USB ARM JTAG, USB-to-RS232 virtual port and power supply 5VDC device (supported by OpenOCD arm debugger)

Low-cost high-speed ARM USB JTAG (supported by the OpenOCD arm debugger)

Important

This topic is for programmers. If you are a customer experiencing USB problems, see Troubleshoot common USB problems

This topic lists the Microsoft-provided drivers for the supported USB device classes.

• Microsoft-provided drivers for USB-IF approved device classes.
• For composite devices, use USB Generic Parent Driver (Usbccgp.sys) that creates physical device objects (PDOs) for each function.
• For non-composite devices or a function of a composite device, use WinUSB (Winusb.sys).

Olimex Usb Devices Driver Download For Windows 10

If you are installing USB drivers: You do not need to download USB device class drivers. They are installed automatically. These drivers and their installation files are included in Windows. They are available in the WindowsSystem32DriverStoreFileRepository folder. The drivers are updated through Windows Update.

If you are writing a custom driver: Before writing a driver for your USB device, determine whether a Microsoft-provided driver meets the device requirements. If a Microsoft-provided driver is not available for the USB device class to which your device belongs, then consider using generic drivers, Winusb.sys or Usbccgp.sys. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver.

USB Device classes

USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF. Each device class is identified by USB-IF approved class, subclass, and protocol codes, all of which are provided by the IHV in device descriptors in the firmware. Microsoft provides in-box drivers for several of those device classes, called USB device class drivers. If a device that belongs to a supported device class is connected to a system, Windows automatically loads the class driver, and the device functions with no additional driver required.

Hardware vendors should not write drivers for the supported device classes. Windows class drivers might not support all of the features that are described in a class specification. If some of the device's capabilities are not implemented by the class driver, vendors should provide supplementary drivers that work in conjunction with the class driver to support the entire range of functionality provided by the device.

For general information about USB-IF approved device classes see the USB Common Class Specification

The current list of USB class specifications and class codes is documented in the USB-IF Defined Class Code List.

Device setup classes

Windows categorizes devices by device setup classes, which indicate the functionality of the device.

Microsoft defines setup classes for most devices. IHVs and OEMs can define new device setup classes, but only if none of the existing classes apply. For more information, see System-Defined Device Setup Classes.

Two important device setup classes for USB devices are as follows:

• USBDevice {88BAE032-5A81-49f0-BC3D-A4FF138216D6}: IHVs must use this class for custom devices that do not belong to another class. This class is not used for USB host controllers and hubs.

• USB {36fc9e60-c465-11cf-8056-444553540000}: IHVs must not use this class for their custom devices. This is reserved for USB host controllers and USB hubs.

The device setup classes are different from USB device classes discussed earlier. For example, an audio device has a USB device class code of 01h in its descriptor. When connected to a system, Windows loads the Microsoft-provided class driver, Usbaudio.sys. In Device Manager, the device is shown under is Sound, video and game controllers, which indicates that the device setup class is Media.

Microsoft-provided USB device class drivers

Related topics