Recent Posts

Pages: [1] 2 3 ... 10
1
USB / Re: Query Regarding interfacing USB Bluetooth adapter
« Last post by Jan Axelson on November 18, 2018, 07:52:41 pm »
If your microcontroller will connect as a USB host to the dongle, the microcontroller will need USB host hardware and drivers plus drivers for the bluetooth profiles you want to support.

See:

https://learn.sparkfun.com/tutorials/bluetooth-basics/all

http://www.hobbytronics.co.uk/usb-host-dip
2
USB / Query Regarding interfacing USB Bluetooth adapter
« Last post by sanjay on November 17, 2018, 12:24:14 am »
how to interface bluetooth usb dongle with microcontroller?
3
USB / Re: "USB Complete or USB Confusing"
« Last post by Jan Axelson on November 12, 2018, 07:50:39 pm »
I was not aware of this! Thank you for posting!
4
USB / "USB Complete or USB Confusing"
« Last post by bpaddock on November 12, 2018, 04:25:01 pm »
Jan, though you might find this of interest, in the plug they give for your books:

http://eecatalog.com/usb/2018/08/07/usb-complete-or-usb-confusing/

5
USB / Re: Class Specific Requests interface routing confusion...
« Last post by Jan Axelson on November 09, 2018, 09:50:16 pm »
Straightforward maybe, but not obvious!
6
USB / Re: Class Specific Requests interface routing confusion...
« Last post by anotherstevest on November 09, 2018, 12:42:51 pm »
Many thanks!  It's as straight forward as I thought it should be...
7
USB / Re: Class Specific Requests interface routing confusion...
« Last post by Jan Axelson on November 08, 2018, 06:33:27 pm »
In USB class specifications, the definitions for class-specific requests typically assign wIndex as the target interface number.
8
USB / Class Specific Requests interface routing confusion...
« Last post by anotherstevest on November 08, 2018, 05:31:48 pm »
I'm still jumping around the USB Complete (5th) and maybe I've just jumped over it... (or I'm just being thick which also happens...)  But from the perspective of the device firmware, how does it know to which interface-specific code/instance is appropriate to handle the Class Specific Requests it receives on EP0.  I'm thinking, for example, of a composite device with multiple Virtual Com ports which have class specific codes for setting control line state - all of which, it appears, come in to EP0 without referencing an interface number...  What have I missed?  Is the interface number buried in the data somewhere?  My Beagle Total Data Center decodes enough to find DTR and RTS but nothing else...

Thanks for the insight (here and in the book).

Steve.

9
USB / Re: USB for Windows-to-Windows communication
« Last post by Jan Axelson on October 30, 2018, 09:10:54 pm »
Every USB communication is between a USB host and a USB device. Two hosts can communicate by connecting two devices back-to-back with a shared buffer, in other words:

USB host
USB device
shared buffer
USB device
USB host

To communicate with a device, the host uses a driver for a defined USB class or a vendor-specific driver.

One option for your application is to use two USB/serial converters and cross-connect the serial ports (null modem connection).

If you need higher throughput, you could program devices that use networking protocols.

10
USB / USB for Windows-to-Windows communication
« Last post by mek363 on October 30, 2018, 06:23:35 pm »
I am writing software for a Windows 10 IoT Embedded device that has an available USB 3.0 xHCI port. I would like to write another program that would run on a laptop and securely connect to the first device via USB to exchange data. Something like TCP/IP over USB seems like the right way to go, but I'm not sure if that is possible. What are my options for achieving this? Thanks.
Pages: [1] 2 3 ... 10