Re: USB Serial - RS232
Re: USB Serial - RS232
- Subject: Re: USB Serial - RS232
- From: "Allen Curtis" <email@hidden>
- Date: Sun, 8 Jun 2008 11:49:40 -0700
Good news!
I went to the Prolific website and downloaded the device driver from there. The package claims to be the same version that I have installed. Installed the driver again and then I could see one of the two devices I had purchased. (both of them were Prolific devices according to System Profiler) Now when you plug in the device, a device entry appears in /dev. The SerialPortSample program can find the device!
Question: This time when I rebooted the system after installing the driver it said, updating the boot cache. I did not notice this message before. Should this always appear when installing a new driver? Perhaps this will be a clue in the future.
Thanks
Allen
On Sun, Jun 8, 2008 at 11:28 AM, Ben Greenfield <
email@hidden> wrote:
On Jun 8, 2008, at 2:24 PM, Allen Curtis wrote:
Ok, If I list the contents of the /dev directory, both before and after the device is connected, I do not see a new device file created. Could USB serial not be in the standard OS X kernel configuration?
Then I think you don't have the driver. I would guess that it is the prolific chip do a search and download that driver and see what you get.
Ben
In OS X, where are the hotplug events logged? I looked in /var/log/system.log but I don't see anything there.
I am running Linux in Parallels and it recognizes the USB serial device just fine.
TIA
- Allen
On Sun, Jun 8, 2008 at 9:54 AM, Allen Curtis <
email@hidden> wrote:
Thanks Ben,
I had changed this like of code to match kIOSerialBSDAllTypes. The enumeration finds the Bluetooth modem and PDA sync but nothing from USB. I didn't see anything about matching but types.
Oh well, I guess the brute force method of specifying the device name directly will work.
- Allen
On Sun, Jun 8, 2008 at 4:00 AM, Ben Greenfield <
email@hidden> wrote:
I'm only guessing but...
On Jun 8, 2008, at 12:00 AM, Allen Curtis wrote:
Is there a reason that the USB serial device is not part of the enumeration with the SerialPortSample project? The searching I had done implied that this should work.
I found this in the SerialPortSample.c file. My guess is that you have to add the modem to the service matching dictionary.
In iokit their are families of devices and to use a driver a device advertises it family class which gets matched in software. What is currently happen is SerialPortSample.c file is not finding the advertised device in it's dictionary of devices that can use the software.
CFDictionarySetValue(classesToMatch,
CFSTR(kIOSerialBSDTypeKey),
CFSTR(kIOSerialBSDModemType));
// Each serial device object has a property with key
// kIOSerialBSDTypeKey and a value that is one of kIOSerialBSDAllTypes,
// kIOSerialBSDModemType, or kIOSerialBSDRS232Type. You can experiment with the
// matching by changing the last parameter in the above call to CFDictionarySetValue.
// As shipped, this sample is only interested in modems,
// so add this property to the CFDictionary we're matching on.
// This will find devices that advertise themselves as modems,
// such as built-in and USB modems. However, this match won't find serial modems.
Thanks
Allen
On Sat, Jun 7, 2008 at 7:29 PM, Ben Greenfield <
email@hidden> wrote:
On Jun 7, 2008, at 10:04 PM, Allen Curtis wrote:
Hello,
I have searched the mailing list for the answers to my question but it appears that what I have done should work.
I have purchase a USB to serial adapter from two different vendors. One from ioGear, the other from i.Connect. In both cases the device drivers where installed and I could see the device in the System Profiller. However when I run the SerialPortSample program, I only see the Bluetooth devices. The sample code has been modified to find any serial type device so both the PDA-Sync and Modem devices get reported, but I never see the USB serial devices.
I am running MAC OS X 10.5.3, with XCode 3.1. Shouldn't the USB serial devices enumerate just like the Bluetooth ones? What do I need to do?
I can't quite remember the details but doing an ls -la /dev/ should reveal the tty devices they will probably have a name that includes some sort of manufactuers signature.
If you can't find it that why do one ls -la without anything plugged in and the do another after plugging in the device compare and if there are addtions in the second one that is the serial device.
If I searched around I could give better advice but I figure at least this advice is a fast response and it may work for you.
Ben
TIA
- Allen
_______________________________________________
Do not post admin requests to the list. They will be ignored.
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden