![]() But there is a driver for the LIDE60, but the LIDE60 is on a different USB ID to the LIDE50.īut. I actually had to do this last week, as I have an old flatbed scanner, a Canon LIDE50, but there isn't a windows 7 driver. It appears to be possible to attach a driver to a different USB ID to the one its designed to work with. If you change the INF file for a windows driver before you install them. There also appears to be a huge loophole in the USB IDs signed drivers thing. The drivers are shipped with what appears to be a standard GNU 3.0 license, which seems to imply that you can do anything you like with the drivers. I suspect a lot of people will ignore that request. I know they need to recoup their costs, but I'm somewhat surprised that they are banging on about not using the USB ID's even if you build your own hardware for your own use. However this is not how its worded on the Adafruit site. On reflection, possibly using the Adafruit drivers with non Adafruit hardware is actually what may be illegal depending on the license terms. The Adafruit website is at pains to point out that you are not allowed to used their USB IDs on anything you build for yourself, however I'm not entirely sure that you would be doing anything illegal by compiling the VUSB code using the trinket IDs. I commend Limor for buying certified drivers, but I do think its all smoke and mirrors regarding USB vid and PID But I keep forgetting to download the MS DDK kit which contains the necessary programs.īut with all the different flavours of Windows, already out there, and Windows 10 on the way, I agree that Windows is now the major stumbling block, when it used to be the easiest platform to maintain. Its ok for Limor as she will eventually recoup the costs.Īctually there is a good work around, by installing local trust certificates, but I've not had time to investigate that idea. I read they cost $2000, so I doubt it will ever happen on a non commercial project like this.Īnd Maple uses 2 separate drivers, so it could be $4000 So the STM32 stuff will need to take a back seat for a while. The source code must exist somewhere and clients are starting to return from their Christmas holidays, so my workload is increasing, and I've still not finished all the DIY stuff I was hoping to complete over the holidays. I recall updating its firmware, but I don't think I recompiled, I think I just got an updated bin film somewhere. I have one of those devices kicking around somewhere. Its main advantage would be its low cost, and easy availability. The hardware for one of the cheap USBASP clones would be capable of being adapted for the STM32, but that would involve an alternative mode/firmware hack, so not sure if the idea has much mileage in it. On the subject of programmers/serial ports etc.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |