> > Well, it's doing better than before. But the device has some nasty > bugs. > > It starts out okay. The device tells the computer that it has 64000 > sectors of data (that's a little under 32 MB since a sector holds 512 > bytes). The computer even reads the first few sectors successfully. > > Then the computer tries to read 8 sectors starting at sector 63872. > This shouldn't cause any problem. But the device chokes, returning an > error indication. When the computer sends a REQUEST SENSE command to > find out what went wrong, the device just sends another error > indication. (In other words, the device doesn't understand REQUEST > SENSE -- which is a mandatory command.) > > The same thing happened when the READ(10) command was repeated several > times, and it happened for other reads near the end of the device's > storage. > > It appears that this device is badly broken. Probably the only > reason it works with Windows is because Windows doesn't try to read the > sectors near the end. I bet it would fail the same way under Windows > if you tried to store a 30-MB file on the device and read it back. > > Alan Stern > Alan, I tried to open the device in Windows in HxD binary editor and - yes, I am getting I/O error when I want to read sectors near the end of the device. Can I disable the test of reading the sectors at the end in usb-storage module ? The debugging of STM8 itself is IMHO done through some custom USB MSC commands. Now I will ask as real newbie. I can either disable usb-storage for the kit (with the quirk) and make my own application with libusb. Or, if usb-storage somehow will succeed to correctly detect the device, I can use services of this kernel module. Am I right ? Is there some sample application which talks directly to usb-storage module (to have an idea how to do it by myself) ? Regards, Vaclav PS. I put the quirk options in /etc/modules but it does not work. I have no idea, why. I have standard Ubuntu Lucid. -- 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
