I'm trying to figure out how to use a chinese RFID/NFC device (Euhoyan ER301) on my Kali Linux.
I have installed the libnfc and all the dependencies. But executing the command "NFC-LIST" theres no devices found.
Executing lsusb I can see the device:
"Bus 003 Device 012: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light"
Apparently the driver CP210x is installed too.
I'm not quite sure if it is the good way to communicate with the device and if it is compatible with the libnfc.
Does someone has more experience about this devices?
Thanks in advance.
Related
I have written an application using the FT232h with libftd2xx.so.1.4.24 for GPIO assess. I had it running on two machines, a Linux openSUSE desktop and an openSUSE laptop. Both run the same kernel and both are Windows 10 boxes running VMware to give me the virtual openSUSE machines. For some reason it suddenly stopped working on the desktop. I have been using the same FTDI FT232H device on both machines.
On the laptop, the FTDI chip is detected. dmesg | grep -i usb says:
usb 2-1: New USB device found, idVendor=0403, idProduct=6014, etc.
On the laptop, lsusb says:
Bus 002 Device 004” ID 0x0403:6014 Future Technology Devices International. Ltd: FT232H
Single HS USB-UART/FIFO IC
This information does not appear on the desktop. The desktop does not seem to detect the FT232H.
On the laptop I do sudo modprobe -r ftdi_sio usbserial and then perform an FT_Open(0, &fthandle) in libftd2xx.so.1.4.24.
On the desktop, ftdi_sio is not loaded. When I try to FT_Open(0, &fthandle) it fails with FT_DEVICE_NOT_FOUND. It dose the same thing when I run my app as root.
What do I need to do to get my desktop to run my app again? I haven’t blacklisted anything, to my knowledge.
I’m really stuck! Please advise.
VMware may assign the USB to the host or to the guest. If the FT232H is plugged in but lsusb doesn't show the FT232H, then select VM -> Removable Devices -> Future Devices USB Serial Converter -> Connect (Disconnect from Host)
lsusb should now show the FT232H device and you should be able to invoke FT_Open on it.
I'm hoping to use the newly released WebUSB API to communicate with a device i developed. This devices uses a FT230X USB to serial chip. The drivers of this chip are installed on most devices and communicating with it using minicom works smoothly. Now i want to try communicate with it through the browser. I started by downloading this example for arduino: webusb arduino. I set the filter to { 'vendorId': 0x0403, 'productId': 0x6015 } which shows the device. I'm able to find the device but when i try to connect i get the error: NotFoundError: Device unavailable.
Is there a way to find more specific errors? Should i set up a different interface or do i need to change some other configurations? I'm new to USB drivers so any help getting me on my way would be nice. I did read the (short) getting started documentation here. I use Ubuntu 16.04
The FT230X USB to serial chip does not provide an USB interface that Chrome can take control of. This is because, as you mention, the drivers for this chip are available with your operating system. With the serial driver attached Chrome cannot make the device available to your page through the WebUSB API.
The Arduino example programs the Atmel 32u4 chip on many Arduino and Arduino-compatible boards to add an additional USB interface which is not claimed by any system driver and is therefore available to Chrome.
Some developers have also had success either changing the vendor and product ID of their device so that the OS drivers do not claim it or by manually unbinding the driver.
Good day every body
I use MC7455 module in linux machine connected using PCI
but when i do : lspci , i didnt find it
and also with dmesg , it is not detected
Is this problem related to drivers missing ?
(For those wondering: This question is asking about the Sierra Wireless MC7455 LTE modem module)
Your modem card is a mini-PCI-e card, but that modem does not connect to the PCI bus. The mini-pci-e slot also connects to the USB bus. This modem card connects only to the USB bus, so it will not show up with lspci.
Instead is should show up as a USB device.
I have lots of experience with MC7304, assuming MC7455 works similar.
MC7455 has a miniPCIe interface, I assume your motherboard has such interface because you said the modem is connected. Have you installed SierraWireless driver? If not, Linux doesn't detect the modem. At least that's my case.
If you don't have a miniPCIe interface on the motherboard, you can use a miniPCIe to USB adaptor.
Once the modem is detected, for MC7304 at least, I can find modem in dmesg as well as by lspci.
Check this link: https://techship.com/faq/38/
I had exactly same issue with my Qotom Q355G4, the device was not detected at all. It was fixed by putting adhesive tape over pins #23, 25, 31, 33.
I am learning to program a USB device (iBall 3.5g USB Dongle) using libusb.h header library.
Until now I am able to identify my device using the Vendor ID and also open the device for operation.
As a next step I would like to know the available commands (or the controls) for example : command to scan the surroundings for available GSM networks.
Obviously I will have to talk to the devices' firmware to extract the necessary information.
I tried to search for the technical datasheet for the 3g dongle, but couldn't find any.
The dongle is powered by a Qualcomm chip
Do you know any of the methods in which I can get the control commands for a usb device ?
Thanks in advance.
There is no simple procedure for figuring out what commands a USB device has. You need to use a combination of looking at the descriptors reported by the device, seeing if the device supports any particular USB device class, reading the USB specification, and maybe doing some reverse engineering using a protocol analyzer.
A good first step would be for you to use lsusb -v to print human-readable descriptions of the device's USB descriptors.
I've built a Buildroot linux image for my PhidgetSBC and included bluetooth support unfortunately it appears my bluetooth USB dongle isn't working. Although I have not tested it with code it's internal LED does not illuminate when I plug it in.
When I issue lsmod I see this:
Module Size Used by Not tainted
usb_storage 33699 -
btusb 8560 -
bluetooth 50130 -
It appears bluetooth is in the kernel but how could I test my usb dongle?
This is definitely not Buildroot related, but rather hardware and kernel configuration rleated. Unfortunately, you're giving way too few details: which Bluetooth USB dongle you're talking about, what kernel version using, what is your kernel configuration, etc.
First of all, check if your USB device appears when running lsusb.