At 3:52 PM +0530 10/14/04, Arun Kumar wrote:
thanks for the prompt reply.
I am developing driver for a USB CDC Device(ADSL Modem),and I am
trying to use the sample driver posted in Apple's website.
I am using USBEnet Sample inside the Examples folder in the USBDDK1.5 f 3.
Can you tell the difference between the USBEnet and USBModem
inside the USBDDK for MAC OS 9.
I have used the USBCDCEthernet sample for the same modem in MAC OS
10.X pretty successfully.
I am able to compile the program(using USBEnet example) and the
extension is copied to the Extensions folder there after.I edited the
source code to include the product and vendor id of the device and
the id is getting displayed in the Devices and Volumes pane under
Apple System Profiler in the control panel abd also in the USB Probe
But the problem I am facing is the device is not showing as a new
interface under the TCP/IP panel in the control panel.I want to
assign IP address so that I could do some tests like PING etc.
Can you give some idea of how to get the device to be shown under the
interfaces in TCP/IP panel in control panel so that I will be able
to configure the device ?
Please suggest some help regarding this.
You want to use the USBEnet sample. The modem sample is like it's
name implies - for a USB modem. The USBEnet sample works in
conjunction with the EnetShimLib. Is this extension installed.
Assuming that the extension is present, then you will need to do some
debugging to provide better clues as to where the problem is.
Unfortunately, there is no terminal window to send printf statement
You could insert USBLog messages in the driver and use USBProber to
view the messages. I prefer to use Macsbug, but Macsbug is
considerably more difficult to use, if you have never used it before.
OTOH, Macsbug is a far more powerful tool.
I'd start with inserting USBLog messages to see what error values are
returned and to see how far into the ConfigurationHandler routine,
the code is getting. I'd output (using USBLog), all return values.
You want to see whether the InstallShimDrvr call ever gets made. When
the driver code reaches this point, the driver has been successfully
configured and the driver is now trying to call the EnetShimLib to
register itself with Open Transport. Once this happens succesfully,
then the device will appear in the TCP/IP Control Panel. You need to
concern yourself with the actions of the driver code since they will
determine if the device appears in the Control Panel. There are no
modifications to the Control Panel to get the device to appear in the
device pop up list. Either the device is successfully registered by
the driver, or it is not.
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden