Hello, STMicroelectronics sells so called Discovery kit - http://www.st.com/mcu/contentid-130-113-STM8S_DISCOVERY.html . On windows there is no problem with debugger which uses Mass Storage Class. But on Linux, there is a plenty of resets and the device is not fully recognized. The problem is likely in a non-correct implementation on the kit. I tried USB Command Verifier and it gave me following log (just excerpt). See below. Is it somehow possible to get the device to work on Linux as well ? I am 90% sure that nobody in STM will fix the bugs. Therefore I am looking for some way how to skip the problems with the detection. Thank you in advance, Vaclav =============== Test log initialized. User Input module initialized Microsoft Windows XP (Build 2600) Service Pack 3.0 USBCommandVerifier.dll ver 1.4.2.3 TestServices.dll ver 1.4.2.3 StackSwitcher.dll ver 1.4.2.3 =============== Now Starting Test: USB Mass Storage Serial Number Test (Configuration Index 0) Start time: Wed Jul 28 11:00:25 2010 Serial Number string for MSC device : iSerialNumber = 0x3 ENGLISH_US language string descriptor is : 4 Using Language ID 0x409 MSC Serial Number length = 26 MSC Serial Number length = 26 MSC Serial Number string descriptor type = 0x3 MSC Serial Number length = 26 MSC Serial Number string descriptor type = 0x3 MSC Serial Number character [0] = 0x34 MSC Serial Number character [1] = 0x0 Invalid MSC Serial Number character ************************* Invalid MSC Serial Number character ************************* ************************* (5.1.3) Serial number characters must be 0x0030-0x0039 or 0x0041-0x0046. ************************* . . . =============== Now Starting Test: USB Mass Storage Power Up Test (Configuration Index 0) Start time: Wed Jul 28 11:00:49 2010 Attempting to re-enumerate device Device has been re-enumerated, perform PowerUp test Configuring device, set configuration = 0x1 NOTE: It is expected the device has reset the data toggles on all Bulk endpoints after the above SetConfiguration call Setting device interface, interface number = 0x0 and alternate setting = 0x0 NOTE: It is expected the device has reset the data toggles on all Bulk endpoints after the above SetInterface call Issuing Get Max LUN request Max LUN value = 0 Getting Device Type Issuing INQUIRY Issuing CBW (attempt #1): |----- CBW LUN = 0x0 |----- CBW Flags = 0x80 |----- CBW Data Transfer Length = 0x24 |----- CBW CDB Length = 0x6 |----- CBW CDB-00 = 0x12 |----- CBW CDB-01 = 0x0 |----- CBW CDB-02 = 0x0 |----- CBW CDB-03 = 0x0 |----- CBW CDB-04 = 0x24 |----- CBW CDB-05 = 0x0 Issuing DATA IN Issuing CSW : try 1 ************************* Expecting a STALL after data phase completes with a zero-length or short packet ************************* If the device actually transfers less data than the host indicated, the device shall STALL the Bulk-In pipe CSW residue returned = 0x13 CSW status returned = 0x0 Failed INQUIRY request, returned 17 bytes of data and expected 36 (5.7.1) All devices must support the commands marked as required in 4.2 based on PDT. Devices that support all the commands marked as required for Bootable devices will be reported as Bootable. Failed PowerUp test (5.8.1) The interface shall be capable of responding to commands without failure immediately following configuration. Unconfiguring the device Stop time: Wed Jul 28 11:00:58 2010 Duration: 9 seconds. Stopping Test [ USB Mass Storage Power Up Test (Configuration Index 0): Number of: Fails (2); Aborts (0); Warnings (1) ] ** Device is NOT considered compliant with the Bootability specification. ** Summary Log Counts [ Fails (17); Aborts (0); Warnings (24) ] -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
