Drivers ARM USB Devices

The STSW-STM32102 software package contains four installation files based on the various versions of the Microsoft ® operating system. OS versions prior to Windows ® 7 are compatible with the Windows ® 7 installations included in the package. Starting from Windows ® 10, the STSW-STM32102 driver is no more adequate and the usage of the native inbox driver is recommended. This allows you to design your own USB device without any specific drivers on the host side as all operating systems have a built-in HID driver. For more information, please visit: USBHID. USBSerial¶ The USBSerial class uses the USB interface to emulate a serial.

Device Driver For Usb Camera

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
• High speed USB 2.0 with lower latency time, RTCK adaptive JTAG clock up to 30Mhz and higher throughput achieve x3-x5 times faster programming speed than ARM-USB-OCD
• Auto-detected powering to your target board with up to 200mA at 5V
• Uses ARM's standard JTAG connector (2 rows × 10 pins at 0.1' step)
• Supports ARM targets working in voltage range 1.65 – 5.0 V DC
• Supports adaptive clocking RTCK
• Able to power a target board via a standard DC barrel jack; cable for the external powering included - 2.1x5.5x14mm female connectors at both ends
• 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 50x40 mm (2x1.6') + 20 cm (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-H with EW-ARM?
• IAR EW has support for GDB and works with ARM-USB-OCD-H.

• 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: 0x002b, 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-H to work with CrossWorks
• 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

     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:

  PID: 0x002b
  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-H?
• ARM-USB-OCD-H 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

Drivers Arm Usb Devices Wireless Adapter

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

The CMSIS-Driver specification is a software API that describes peripheral driver interfaces for middleware stacks and user applications. The CMSIS-Driver API is designed to be generic and independent of a specific RTOS making it reusable across a wide range of supported microcontroller devices. The CMSIS-Driver API covers a wide range of use cases for the supported peripheral types, but can not take every potential use-case into account. Over time, it is indented to extend the CMSIS-Driver API with further groups to cover new use-cases.

Usb Device Drivers Windows 10

The CMSIS Software Pack publishes the API Interface under the Component Class CMSISDriver with header files and a documentation. These header files are the reference for the implementation of the standardized peripheral driver interfaces. These implementations are published typically in the Device Family Pack of a related microcontroller family under the Component Class CMSISDriver. A Device Family Pack may contain additional interfaces in the Component Class Device to extend the standard Peripheral Drivers covered by this CMSIS-Driver specification with additional device specific interfaces for example for Memory BUS, GPIO, or DMA.

The standard peripheral driver interfaces connect microcontroller peripherals for example with middleware that implements communication stacks, file systems, or graphic user interfaces. Each peripheral driver interface may provide multiple instances reflecting the multiple physical interfaces of the same type in a device. For example the two physical SPI interfaces are reflected with a separate Access Struct for SPI1 and SPI2. The Access Struct is the interface of a driver to the middleware component or the user application.

The following CMSIS-Driver API groups are defined:

• CAN: Interface to CAN bus peripheral.
• Ethernet: Interface to Ethernet MAC and PHY peripheral.
• I2C: Multi-master Serial Single-Ended Bus interface driver.
• MCI: Memory Card Interface for SD/MMC memory.
• NAND: NAND Flash Memory interface driver.
• Flash: Flash Memory interface driver.
• SAI: Serial audio interface driver (I2s, PCM, AC'97, TDM, MSB/LSB Justified).
• SPI: Serial Peripheral Interface Bus driver.
• Storage: Storage device interface driver.
• USART: Universal Synchronous and Asynchronous Receiver/Transmitter interface driver.
• USB: Interface driver for USB Host and USB Device communication.
• VIO: API for virtual I/Os (VIO).
• WiFi: Interface driver for wireless communication.

CMSIS-Driver in ARM::CMSIS Pack

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-H with EW-ARM?
• IAR EW has support for GDB and works with ARM-USB-OCD-H.

• 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: 0x002b, 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-H to work with CrossWorks
• 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

     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:

  PID: 0x002b
  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-H?
• ARM-USB-OCD-H 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

Drivers Arm Usb Devices Wireless Adapter

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

The CMSIS-Driver specification is a software API that describes peripheral driver interfaces for middleware stacks and user applications. The CMSIS-Driver API is designed to be generic and independent of a specific RTOS making it reusable across a wide range of supported microcontroller devices. The CMSIS-Driver API covers a wide range of use cases for the supported peripheral types, but can not take every potential use-case into account. Over time, it is indented to extend the CMSIS-Driver API with further groups to cover new use-cases.

Usb Device Drivers Windows 10

The CMSIS Software Pack publishes the API Interface under the Component Class CMSISDriver with header files and a documentation. These header files are the reference for the implementation of the standardized peripheral driver interfaces. These implementations are published typically in the Device Family Pack of a related microcontroller family under the Component Class CMSISDriver. A Device Family Pack may contain additional interfaces in the Component Class Device to extend the standard Peripheral Drivers covered by this CMSIS-Driver specification with additional device specific interfaces for example for Memory BUS, GPIO, or DMA.

The standard peripheral driver interfaces connect microcontroller peripherals for example with middleware that implements communication stacks, file systems, or graphic user interfaces. Each peripheral driver interface may provide multiple instances reflecting the multiple physical interfaces of the same type in a device. For example the two physical SPI interfaces are reflected with a separate Access Struct for SPI1 and SPI2. The Access Struct is the interface of a driver to the middleware component or the user application.

The following CMSIS-Driver API groups are defined:

• CAN: Interface to CAN bus peripheral.
• Ethernet: Interface to Ethernet MAC and PHY peripheral.
• I2C: Multi-master Serial Single-Ended Bus interface driver.
• MCI: Memory Card Interface for SD/MMC memory.
• NAND: NAND Flash Memory interface driver.
• Flash: Flash Memory interface driver.
• SAI: Serial audio interface driver (I2s, PCM, AC'97, TDM, MSB/LSB Justified).
• SPI: Serial Peripheral Interface Bus driver.
• Storage: Storage device interface driver.
• USART: Universal Synchronous and Asynchronous Receiver/Transmitter interface driver.
• USB: Interface driver for USB Host and USB Device communication.
• VIO: API for virtual I/Os (VIO).
• WiFi: Interface driver for wireless communication.

CMSIS-Driver in ARM::CMSIS Pack

The following files relevant to CMSIS-Driver are present in the ARM::CMSIS Pack directories: