|
From: Hugo S. <hugosg@u.washington.edu> - 2009-05-17 19:56:44
|
Guys, I did significant progress during last night, I am happy 1) I sniff my device under windows and I found out that the communications protocol is pretty simple. 2) I manage to talk with my device using libusb with my windows computer using a hava wrapper for libusb -javalibusb- 3) I compile and install libusb for my Mac PPC 1.5 4) I compile and install the java wrapper on the Mac The device is being recognized by the computer because on my System Profiler I can see it Communication Device: Product ID: 0x6119 Vendor ID: 0x03eb (Atmel Corporation) Version: 0.01 Speed: Up to 12 Mb/sec Location ID: 0x0b200000 Current Available (mA): 500 Current Required (mA): 100 However When I list the USB devices with libusb I can see to normal devices -mouse, keyboard, etc...- but not my little USB Dongle. Should I mount the device is some way? Am I forgetting something? Can somebody help me? It would be greatly appreciate it. Warm regards Hugo On May 16, 2009, at 1:47 PM, Peter Stuge wrote: > Hugo Solis wrote: >> Thanks so much for you quick response. I really appreciate it. > > You're welcome! Thanks for coming back on list so that others can > help you better, and so that replies will be available in archives > for your followers! > > >>> libusb is not active in this regard. Recognition happens in the >>> operating system kernel and the USB support there. >> >> Do you mean that I still need a driver for the device I am using. > > No, not beyond the general USB support in the system. > > >> It's seems -or at least I have not found after hours and hours- a >> driver for the usb chip that my device is using. I tough libusb >> could replace it. > > libusb is never a 1:1 replacement for a kernel driver, but maybe it > will be suitable for you! > > >> How can I know if my device is been recognized by the Mac computer. >> I guess it is because people manage to use it on Mac. > > It should be recognized. Maybe look for it in "About this Mac" and > the device listing available there. > > >>> At best you will be able to communicate with the device by writing >>> an application that utilizes libusb. >> >> I am fine writing the application using libusb -I will use >> Javalibusb- but once that I have access to the device I do not know >> what to send to it if it's expecting a serial protocol. Maybe I am >> totally confuse. > > Ah yes! This is the key. > > We have no idea what protocol the device expects. The fact that it > shows up as a serial device in some operating systems unfortunately > does not mean anything, because the kernel drivers in those systems > can communicate in any way with the device via USB. > > Maybe you can look to the Linux/BSD communities for more information > about the particular device? > > Or even the vendor itself? Maybe the Raven documentation details the > USB communication used by the device and/or it's firmware? > > Recommend looking at the USB specification if you end up writing a > libusb application (directly or through wrapper) because there are > some things that need to be right, and vendor documentation is not > always helpful enough, so getting everything correct requires good > understanding of the several USB protocol layers, as well as lots of > trial and error. > > But once every now and then, vendors surprise you and have made > simple and efficient designs with good documentation. Maybe you're > one of the lucky few - it could happen! :) > > > //Peter > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libusb-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-devel |