Author Topic: HID filestream.write freeze  (Read 10181 times)

blabla

  • Member
  • ***
  • Posts: 1
HID filestream.write freeze
« on: July 19, 2012, 04:21:53 am »
hi,
I had written a HID C# tool based on wimars  c# filestream implementation. But i still have problems with
some software freezes. The write  m_oFile.Write(oOutRep.Buffer, 0, oOutRep.BufferLength) funktion freezes - sometimes. Especially when you send and receive much data.
Is the a way to debug the write function? Or perhaps someone has the same problems and a solution?


Thanks
Alexander


PS: my tool is communicating with a ST µC with 64byte frames in 1ms update interval
Code: [Select]
Connection Information
 Port: 2
 Speed: Full Speed
 Device address: 7
 Open pipes: 2
 Connection status: Device connected

Device Descriptor
 USB version: 2.0
 Device class: 0x0 - (Defined at Interface level)
 Device subclass: 0x0 - Unknown
 Device protocol: 0x0 - Unknown
 Control pipe max size: 64 bytes
 Vendor ID: 0x483 (SGS Thomson Microelectronics)
 Product ID: 0x5750 (Unknown)
 Product version: 2.0
 Manufacturer: STMicroelectronics
 Product: STM32 HID
 Serial Number: 01234
 Configurations: 1


Configuration Descriptor
 Number of interfaces: 1
 Configuration value: 0x1
 Attributes: Self powered, Bus powered
 Max power: 100 mA

Interface Descriptor: 0, Alternate setting: 0
 Number of endpoints: 2
 Interface class: 0x3 - Human Interface Device
 Interface subclass: 0x0 - No Subclass
 Interface protocol: 0x0 - None
 Endpoint address 0x1, Input, Interrupt, max packet size: 64 bytes, update interval: 1 1-millisecond frames
 Endpoint address 0x1, Output, Interrupt, max packet size: 64 bytes, update interval: 1 1-millisecond frames

Jan Axelson

  • Administrator
  • Frequent Contributor
  • *****
  • Posts: 3033
    • Lakeview Research
Re: HID filestream.write freeze
« Reply #1 on: July 19, 2012, 10:26:33 am »
A protocol analyzer will show what is happening on the bus and can help you find out if the device firmware is failing and if so, how. For example, is the device NAKing all incoming data?

If you don't have a protocol analyzer, use whatever debugging tools you have to find out what the host is sending and how the device is responding.

Jan