How to implement a bluetooth to a pen drive?
You can't. A USB memory stick doesn't have any bluetooth hardware.
Related
We are trying to make an USB HID enumeration to simulate a keyboard device on a BLED 112 (with MCU C8051): http://www.silabs.com/products/wireless/bluetooth/bluetooth-low-energy-modules/ble121lr-bluetooth-smart-long-range-module1
We read in the BLUETOOTH SMART MODULE (last version : 12/20/2016) that : "There is no support in the current BLE stack for other types of USB enumeration such as USB HID or other protocols".
But we found examples to make HID keyboard, but only in one way : computer to usb dongle.
So we would like to know if it is possible to make an HID usb enumeration where the dongle send keyboard event to the computer.
If someone have clues, example, or other, it will be great
thanks for your help.
just for information, this is the response given by the silicon labs technical team :
"Unfortunately that is not possible, the BLED112 enumerates as a USB CDC device only. It communicates with the PC using BGAPI messages which is our proprietary protocol to interface with our modules."
As I know, on PPC460GT doesn't support for USB functions. But I saw in my PPC460GT, it has a FT313H Chip, a USB 2.0 Host Controller Device. Can anyone tell me what can I do to enable USB 2.0 function based on FT3131H Chip on my PPC460GT.
You have to know how you can communicate with this controller. If you have it on board then it has to be accessible somehow from CPU point of view - at some address. If you have address you can remap it for linux kernel and then you have access to it EHCI registers.
I bought one of those tiny bluetooth USB dongles that you can plug on a PC and make bluetooth communications. I am wondering if I just plug this dongle to a USB power source, like the USB charger that comes with iPad, can the bluetooth dongle power up, and be discovered as a bluetooth device? This sounds reasonable, since the bluetooth dongle should be able to broadcast itself, at least using some low-level protocol, i.e. showing its Mac address.
However, I tried to do the following:
1.Plug the bluetooth dongle on my iPad's usb charger
2.Search bluetooth devices on my laptop
and I could not find it. Is it because the bluetooth dongle needs the PC to initialize it, so that it can be discovered? Or I am not doing it right?
Thanks
It depend on the dongle
Typical PC dongles depends on the host (pc) to initialize and start any bluetooth activity - including scanning etc
It is practically possible to make dongles that can start becoming discoverable without waiting for host initialization. This has to be a custom build
I want to control television through pen drive. What should I do with pen drive means at hardware and software level?
What type of kernel should I load and how I load the kernel and bootloader in pen driver?
A pen drive has no CPU so it's not clear how this could ever work. A pen drive is just some memory and a USB interface. To control a TV you need some kind of processor and a suitable interface (e.g. infra red).
I am wondering, do you need a specific device driver to read a usb device in Linux, or should it just be able to be read. If I connect my cell phone or iPod touch to my linux box, it is not found is /proc/partitions and thus is not a mountable device by fdisks standards, though gnomes nautilus does in fact mount the iPod but not the windows mobile touch pro cell phone.
So I am interested, If I just wanted to read a device(iPod touch) in linux, how can I do so. How can I get a hold of a descriptor of a set usb device so I can read it.
Thanks all.
You can access raw USB endpoints under /dev/usbdev. There is user-space libusb that makes it easier.
Unfortunately there is no simple concept of "just read it" for USB devices (I am assuming that you are not referring to reading and writing the data on the USB bus that make up the USB protocol). In short, you always need a device driver for accessing a USB device and it is up to the driver to implement "the abstraction" of the device used by the system (disk, serial device, etc).