Wi-Fi driver through USB host interface

Hi,
We are trying to develop Wifi driver for Windows CE OS connected to Freescale based i.Mx6 device through USB host interface.
I am planning to communicate with the Wifi driver through AT commands and so I want to make USB host driver detected 
as virtual com port (USB serial client driver). What registry settings I need to make to do so.
Thanks in advance,
Seeth

I'm a bit confused. You'll want NDIS to talk to the device, right? Don't you need to make it appear to USB as a network driver, then? The network driver can, of course, use whatever it wants to talk to the hardware (at the USB level), but I don't see how
creating a COM4: device gets you anywhere.
You're going to install two drivers, one for the hardware making it look like a serial port, and a second for NDIS interface? You're then going to open the serial port in your NDIS driver (you'll have to detect which of several ports is the right one), and
implement the NDIS interface by making ReadFile, WriteFile, and DeviceIoControl calls to the serial port driver? Won't that be problematic for network adapter interrupt handling (among other things)?
Paul T.

Similar Messages

  • My IMac shuts down when transfering files to a Hard Drive through USB

    Hi all,
    I have been having trouble with my IMac. It's over 3 years old and I didn't actualized the operative system. Everytime I try to transfer files from the computer to a hard drive or pen drive (through USB), the computer shuts down. Sometimes it restarts, sometimes it gets shut. I wonder what's the issue and if getting a newer operate system (Snow Leopard maybe) will help.
    Thanks

    Starting up in Safe Mode
    http://support.apple.com/kb/HT1455
    Macs: Resetting the System Management Controller (SMC)
    http://support.apple.com/kb/HT3964
    Resetting your Mac's PRAM and NVRAM
    http://support.apple.com/kb/HT1379

  • Can I boot an internal hard drive through USB?

    I have an old 2008 Mac Pro running Snow Leopard 10.6.8 that just quit on me. When I boot up, I get to the apple logo and then the screen turns white and stays that way until I power off my machine. I have a few hard drives with operating systems installed and a boot partition. When I hold option on start up, I'm able to pick a hard drive to boot from, but I get the same problem. This leads me to believe that the issue lies with my computer, not the disks.
    I've also tried booting in safe mode and get the same problem.
    So I'm looking at purchasing one of these bad boys:
    http://www.amazon.com/dp/B0099TX7O4/ref=wl_it_dp_o_pd_nS_ttl?_encoding=UTF8&coli d=169XE2BWHBJ2P&coliid=I1JKOUV0BWEUFR
    So here's my question:
    I have an early 2013 Macbook Pro running Yosemite 10.10 that I want to use to boot my Mac Pro internal hard drives from. Is it possible to do so? I figure I can access it through pressing the option key during start up.
    Thanks!
    Jon

    I'm sorry, but that won't work because your MP only has Firewire ports and no Thunderbolt ports while your new MBP has Thunderbolt ports but no Firewire ports. Therefore, you cannot connect the two together except using Ethernet or Wi-Fi from which neither can be booted. If you use the device from Amazon, then you need to remove one of the drives to insert in it. Then you could boot from it provided the drive is actually bootable in the other machine. Snow Leopard is not capable of booting a 2013 MBP.

  • Scale driver through USB

    We are going to use a Mettler Toledo MS303S USB scale.  Ohaus was recently bought by Mettler Toledo and I think that the product that we are using is a re-branded Ohaus scale.  I am looking for an available driver. Any help?

    There was a recent discussion on using a USB scale with LabVIEW. You should read that over to see if any of it applies to your device.
    Otherwise, you're going to need to find out what type of USB driver is being used. Do they have a custom USB driver? Are they using HID?

  • GPIB instruments connected through Agilent USB/GPIB Interface can bee seen in MAX but can't communicate in labview

    I have an Agilent 82357B USB/GPIB Interface connected to my computer. 
    Attached to that, I have two lock-in amplifiers (an SR830, and an SR
    850).  I would like to be able to communicate with them through GPIB.
    I have downloaded and installed the software for the Agilent device
    (Agilent IO Control), and I can see the interface and the two devices
    in that software.  Here's what is configured in this software, that I
    can see:
    The VISA interface ID is GPIB0, and its address is 0
    The VISA addresses of the devices are GPIB0::4::INSTR and GPIB::12::INSTR, and the GPIB addresses are 4 and 12
    In Measerment and Automation Explorer (MAX), I made sure that the
    Passport for Tulip box was checked.  Once it was, I could see the
    devices in the Configuration window under Devices and Interfaces ->
    Miscellaneous VISA Resources.  There, I see GPIB0::INTFC, GPIB0::4::INSTR and GPIB::12::INSTR.
    I can right click on either of the instruments, and "Open VISA Test
    Panel" where I am successfully able to send commands and read from both
    devices.
    HOWEVER, when I am running an actual LabView program, I am unable to communicate with the devices. 
    For example, when I try to communicate to the devices through VISA,
    using the 'Basic Serial Write and Read.vi' (while VISA Resource Name is
    GPIB0::12::INSTR), I get an error:
    Error -1073807331 occurred at Property Node (arg 2) in VISA Configure Serial Port (Instr).vi->Basic Serial Write and Read.vi
    Possible reason(s):
    VISA:  (Hex 0xBFFF001D) The specified attribute is not defined or supported by the referenced resource.
    When trying to communicate with them through GPIB (which is what I want
    to do in the end), using 'GPIB.vi' I also get an error.  Here, GPIB
    address is 12, and I am just trying to give it the command *IDN?
    GPIB Write returned error code:
    EDVR: Error connecting to driver or device
    What's going on?

    You can use VISA Write and VISA Read. You just can't use the example called Basic Serial Write and Read because that is specifically for the RS-232 port. The GPIB-VISA is one of the shipping examples. Start the example finder and go to the search tab. Search for VISA.
    Again, no you cannot use the GPIB functions with a non-NI controller. The low level functions for an NI board and an Agilent one are completely different. You can rewrite the driver to use VISA or you can rewrite it to use the low level functions that Agilent provides. You use the Call Library Function Node, I believe to access their GPIB driver.
    I hate to say it but the $20 difference between the Agilent and the NI controller does not seem like much of a saving.

  • I have a Leopard DL disk & bought an external CD drive, but I read that I can't install through USB?

    I also have a Leopard DL disk and having the same problem with my eMac. I bought an external CD drive, but I read that I can't install through USB. Why is that? Would a USB A female to FireWire IEEE 1394 6P converter work? Or do I have to buy another CD drive with a FireWire? Please help.
    PS
    Can you also please explain how to boot from an external drive? (CD drive and storage device). Is there even a way to save the disks content to an external memory device and install it from there?
    Message was edited by: Edz2
    <Re-Titled By Host>

    Hi,
    Very few PPC Macs can boot from USB, most require Firewire... BUT, all 3 of my eMacs can & do boot from USB, try holding the alt or option key at bootup.
    A USB<->FW converter will not work.

  • Hard Drive not detected through SATA, but it is through USB.

    This week my hard drive seemed to crash, I got the file with the question mark and it wouldn't show up in disk utility. I went out and bought a new hard drive, popped it in and it too doesn't show up. I put my old hard drive in an enclosure and plugged it in through USB, and my macbook starts up just fine that way. What could be the problem?

    dcbaros wrote:
    Well I know the drive is fine because I can run it from the usb enclosure, but is the sata cable going bad a common problem?
    Not common but I've seen it happen more than once so I wouldn't be surprised if that is what's going on with your computer.

  • Can I install os on a hard drive conected through usb

    Can I install a OS on a hard drive conected through usb On my macbook pro?
    Thanks:)

    Will not work.
    Mac is not capable of running older version then it shipped with originally.
    Allan

  • How to achieve image using digital camera of USB-type interface through IMAQ PCI-1424 board.

    1.Is it doable?
    2.How to connect USB-type interface with IMAQ PCI-1424 board.
    Thanks!

    See the Developer's Zone (www.ni.com/zone) for specifics on USB (search for "USB").
    "1.Is it doable?"
    - In short "no".
    - USB is similar to FireWire (IEEE 1394), and no framegrabber is required. We offer an IEEE 1394 IMAQ driver to interface FireWire cameras with LabVIEW & CVI.
    "2.How to connect USB-type interface with IMAQ PCI-1424 board."
    - You will need a USB driver for the camera. The 1424 is not required.

  • Interface with hardware through USB,not NI hardware

    Hi All,
    I wish to interface my hardware through USB using LabView. However,my hardware is not from National Instruments and I wish to know whether LabView can still interface with it. I need it urgently for my project. Hope someone can help. Thanks a lot in advance.
    Cheers =)

    Hi,I think I only have the nxnusb.ini & nxnusb.dll file. I'm not very sure what is the usage for it. I've asked the vendor about the interfacing. He said its possible but its only for experienced programmer. Haha,well,i'm not so sure what he means but thats all he suggested. So I hope someone can help me with this device interface. Thanks a lot.
    Attachments:
    nxnusb.ini ‏1 KB

  • Recording with guitar to computer through USB X-Fi

    I am having a problem trying to record with my guitar through my USB X-Fi 5.. I am using a program called Audacity to capture the recording. I have my guitar hooked up to a Line 6 POD 2.0 effects device that has a left/right output. Then I plugged the /8th male end running from that into the Line-In port on the USB X-Fi 5. and then to my computer via USB. But I cannot hear my guitar when playing and it will not capture the recording. I basically bought the USB X-Fi 5. because when recording with my guitar I thought that my laptops sound card was making the recording of low quality. So I got the USB X-Fi 5. to help that. Any help would be greatly appreciated!Message Edited by BulletFMV on 2-06-2008 03:42 PMMessage Edited by BulletFMV on 2-06-2008 03:43 PM

    That USB audio interface isn't any better for recording from onboard sound. You should have bought least the Creative E-MU 0202 USB (if you prefer Creative products/USB audio interfaces).
    With your current setup, instead of using Audacity, you could try, say, Cockos Reaper + Asio4All driver.
    - http://www.reaper.fm/
    - http://www.asio4all.com
    In any case, remember also read the software documentation as well ... all needed information for recording task is normally guided there in user manual(s).
    jutapa

  • M-Audio Mobile Pre USB audio interface compatibility w/ FCP

    I am trying to do voiceovers in FCP with my mic connected to the XLR input on a M-Audio Mobile Pre USB audio interface.
    The first time I did this, even though I got a signal in System Preferences audio input, I would get no signal in the Voiceover Tool window in FCP. I know I chose the correct source, input and rate for the device. I rebooted and it worked. Then on another day a reboot would not make it work. Now I can’t make it work again. Upon opening FCP with the USB interface connected OSX crashed. This almost never happens ether with the system in general or since I installed FCP 5.1. This has happened twice. I also started this whole process by updating to the newest driver for the M-Audio device. I liked the sound I got when it worked so any help with this problem would be appreciated.

    Thanks for that link...that's what I saw months ago, and I realize I got a few of the specifics mixed up. UNFORTUNATELY, I tried those tips and I still have the exact same problem. I also went to M-Audio and downloaded the most recent driver. I did a variety of starts and re-starts where the unit was connected or not upon start up...whether phantom power was on or off at start up, etc etc. And by start up I mean both starting GB only, and/or starting up my Mac. I tested using the interface through both of the USB ports. All yield the same result. The only thing I didn't test yet is changing the USB cable itself.
    Any more thoughts? You think the interface is bad?

  • Adobe audition 1.5 - USB recording interface?

    I want to get a USB Recording Interface for my computer but am unsure if Adobe Audition 1.5 has USB options.  When I select a track input I see no USB option.
    I guess my computer's audio default program is Santa Cruz and I see no USB option there either.  Also, can Adobe Audition 1.5, if it does have a USB option, separate multiple signals (instruments) coming through
    one USB input and put them onto different tracks simultaneously?  Basically what I am asking is if a USB recording Interface works with Adobe Audition 1.5.
    Thank you!

    You will only be able to record multiple instruments on to different tracks if you get a USB audio interface that accepts multichannel input/output. USB 2 audio devices can support a pretty high number of simultaneous channels. Although, as Bob mentions, you really need a ASIO driver supporting audio interface to get more than a couple of audio channels going at once.
    But having said all that I have had up to 8 channels working OK with AA 1.5 if the device has good support for Windows WDM audio drivers which 1.5 does support.

  • Core 1 usb audio interface not supported by OS x 10.10?

    Today I bought a Alesis Core 1 USB audio interface in order to connect my guitar to my mac and garageband.
    My mac Book pro (with Yosemite) does not pass through any signal from my guitar.
    Is this a known problem? Do I need to install another driver, and where can I get this?

    The photos are located in your iPhoto Library package which, by default, is located in your Pictures folder and is independent of the application. 
    What system are you running?  If it's anything earlier than Yosemite you won't be able to download iPhoto as the only version available from the App Store is 9.6 which only works with Yosemite.

  • Mount HDs through USB

    Hey people,
    I want to access a HD through USB, and I have a small device/adaptor for this: you can plug your HD in it, and then you can connect it to the USB plug of your computer. But unfortunately, it doesn.t work... the device is recognized, and the usbstorage driver seems to be attached to it, but I dont know what goes wrong. there is nothing added in /dev (like sda or something)
    this is the output of /proc/bus/usr/devices on the device:
    T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
    D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
    P: Vendor=04ce ProdID=0002 Rev= 2.60
    S: Manufacturer=ViPower
    S: Product=ViPower
    C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
    I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
    E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    and this is the output of dmesg on the device and on usbstorage:
    usb 3-1: new full speed USB device using uhci_hcd and address 2
    usb 3-1: configuration #1 chosen from 1 choice
    usb-storage: USB Mass Storage device detected
    usb-storage: -- associate_dev
    usb-storage: Vendor: 0x04ce, Product: 0x0002, Revision: 0x0260
    usb-storage: Interface Subclass: 0x06, Protocol: 0x50
    usb-storage: Transport: Bulk
    usb-storage: Protocol: Transparent SCSI
    usb-storage: *** thread sleeping.
    scsi0 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 2
    usb-storage: waiting for device to settle before scanning
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00 len=1
    usb-storage: GetMaxLUN command result is 1, data is 0
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Command INQUIRY (6 bytes)
    usb-storage: 12 00 00 00 24 00
    usb-storage: Bulk Command S 0x43425355 T 0x1 L 36 F 128 Trg 0 LUN 0 CL 6
    usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
    usb-storage: Status code 0; transferred 31/31
    usb-storage: -- transfer complete
    usb-storage: Bulk command transfer result=0
    usb-storage: usb_stor_bulk_transfer_sglist: xfer 36 bytes, 1 entries
    usb-storage: Status code 0; transferred 36/36
    usb-storage: -- transfer complete
    usb-storage: Bulk data transfer result 0x0
    usb-storage: Attempting to get CSW...
    usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
    usb-storage: Status code 0; transferred 13/13
    usb-storage: -- transfer complete
    usb-storage: Bulk status result = 0
    usb-storage: Bulk Status S 0x53425355 T 0x240058 R 0 Stat 0x0
    usb-storage: Bulk logical error
    usb-storage: -- transport indicates error, resetting
    usb 3-1: reset full speed USB device using uhci_hcd and address 2
    usb-storage: usb_reset_device returns 0
    usb-storage: scsi cmd done, result=0x70000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Command INQUIRY (6 bytes)
    usb-storage: 12 00 00 00 24 00
    usb-storage: Bulk Command S 0x43425355 T 0x2 L 36 F 128 Trg 0 LUN 0 CL 6
    usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
    usb-storage: Status code 0; transferred 31/31
    usb-storage: -- transfer complete
    usb-storage: Bulk command transfer result=0
    usb-storage: usb_stor_bulk_transfer_sglist: xfer 36 bytes, 1 entries
    usb-storage: Status code 0; transferred 36/36
    usb-storage: -- transfer complete
    usb-storage: Bulk data transfer result 0x0
    usb-storage: Attempting to get CSW...
    usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
    usb-storage: Status code 0; transferred 13/13
    usb-storage: -- transfer complete
    usb-storage: Bulk status result = 0
    usb-storage: Bulk Status S 0x53425355 T 0x240058 R 0 Stat 0x0
    usb-storage: Bulk logical error
    usb-storage: -- transport indicates error, resetting
    usb 3-1: reset full speed USB device using uhci_hcd and address 2
    usb-storage: usb_reset_device returns 0
    usb-storage: scsi cmd done, result=0x70000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Command INQUIRY (6 bytes)
    usb-storage: 12 00 00 00 24 00
    usb-storage: Bulk Command S 0x43425355 T 0x3 L 36 F 128 Trg 0 LUN 0 CL 6
    usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
    usb-storage: Status code 0; transferred 31/31
    usb-storage: -- transfer complete
    usb-storage: Bulk command transfer result=0
    usb-storage: usb_stor_bulk_transfer_sglist: xfer 36 bytes, 1 entries
    usb-storage: Status code 0; transferred 36/36
    usb-storage: -- transfer complete
    usb-storage: Bulk data transfer result 0x0
    usb-storage: Attempting to get CSW...
    usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
    usb-storage: Status code 0; transferred 13/13
    usb-storage: -- transfer complete
    usb-storage: Bulk status result = 0
    usb-storage: Bulk Status S 0x53425355 T 0x240058 R 0 Stat 0x0
    usb-storage: Bulk logical error
    usb-storage: -- transport indicates error, resetting
    usb 3-1: reset full speed USB device using uhci_hcd and address 2
    usb-storage: usb_reset_device returns 0
    usb-storage: scsi cmd done, result=0x70000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Command INQUIRY (6 bytes)
    usb-storage: 12 00 00 00 24 00
    usb-storage: Bulk Command S 0x43425355 T 0x4 L 36 F 128 Trg 0 LUN 0 CL 6
    usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
    usb-storage: Status code 0; transferred 31/31
    usb-storage: -- transfer complete
    usb-storage: Bulk command transfer result=0
    usb-storage: usb_stor_bulk_transfer_sglist: xfer 36 bytes, 1 entries
    usb-storage: Status code 0; transferred 36/36
    usb-storage: -- transfer complete
    usb-storage: Bulk data transfer result 0x0
    usb-storage: Attempting to get CSW...
    usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
    usb-storage: Status code 0; transferred 13/13
    usb-storage: -- transfer complete
    usb-storage: Bulk status result = 0
    usb-storage: Bulk Status S 0x53425355 T 0x240058 R 0 Stat 0x0
    usb-storage: Bulk logical error
    usb-storage: -- transport indicates error, resetting
    usb 3-1: reset full speed USB device using uhci_hcd and address 2
    usb-storage: usb_reset_device returns 0
    usb-storage: scsi cmd done, result=0x70000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Bad target number (1:0)
    usb-storage: scsi cmd done, result=0x40000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Bad target number (2:0)
    usb-storage: scsi cmd done, result=0x40000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Bad target number (3:0)
    usb-storage: scsi cmd done, result=0x40000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Bad target number (4:0)
    usb-storage: scsi cmd done, result=0x40000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Bad target number (5:0)
    usb-storage: scsi cmd done, result=0x40000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Bad target number (6:0)
    usb-storage: scsi cmd done, result=0x40000
    usb-storage: *** thread sleeping.
    usb-storage: queuecommand called
    usb-storage: *** thread awakened.
    usb-storage: Bad target number (7:0)
    usb-storage: scsi cmd done, result=0x40000
    usb-storage: *** thread sleeping.
    usb-storage: device scan complete
    Does anybody know how to get this device recognized, and secondly, how to mount the HD?
    thanks!
    rogier

    I got a bit further! whohoo! and how:
    1) I read somewhere that I had to upload new firmware to the device, after that, Linux would be able to acces the HD through the USB.
    2) flashing theh firmware was only possible on a win98 or me computer (xp didnt work). So I had to find a win98 comp (impossible), or install windows 98.
    3) better install win98 then. but then I needed to have an empty HD, which I didnt have... so
    4) I backup a small old HD to another HD, and then to format it
    5) copied all the files from the win98 cd using 2 different readers, since the cd was too scratched
    6) finally installed win98, and flashed the firmware...
    That took me about 3 hours...
    and now I am a bit closer to my goal: accessing my old HD through usb.
    after the flashing, my device just became something else: output of /proc/bus/usb/devices:
    T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
    D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
    P: Vendor=04ce ProdID=0002 Rev= 2.6c
    S: Manufacturer=SL IDE
    S: Product=SL IDE
    S: SerialNumber=11204EC
    C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
    I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
    E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    anyhoo, I have /dev nods now: /dev/sdaX (X are the exact partitions that are present on the HD in question), but when I try to mount them, it gives an error:
    [root@anadyr usb]# mount /dev/sda5 -t ext3 /mnt/backup
    mount: wrong fs type, bad option, bad superblock on /dev/sda5,
    missing codepage or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so
    the output of dmesg | tail is:
    [root@anadyr usb]# dmesg | tail
    usb-storage: Bulk status result = 0
    usb-storage: Bulk Status S 0x53425355 T 0x274 R 0 Stat 0x0
    usb-storage: -- Result from auto-sense is 0
    usb-storage: -- code: 0x70, key: 0x2, ASC: 0x2, ASCQ: 0x0
    usb-storage: (Unknown Key): (unknown ASC/ASCQ)
    usb-storage: scsi cmd done, result=0x2
    usb-storage: *** thread sleeping.
    sd 0:0:0:0: Device not ready.
    end_request: I/O error, dev sda, sector 48260
    EXT3-fs: unable to read superblock
    So the problem I am facing right now is: unable to read superblock... any ideas?

Maybe you are looking for