Hi I have been trying to connect a few boards to my computer. These boards depend on RNDIS driver to get into concole. So if I connect a board for the first time my Win7 Laptop properly detects it as a RNDIS ethernet adapter or device. But when I plug in the boards second time it just comes up as a unknown device in USB section of device manager. From searching the web I assume that something is RNDIS to fail. So I try to install the driver manually using http://www.sharpduino.com/en/articles/article/19 where it suggest to manually install a driver under Network Adapters > Microsoft Corporation > RNDIS. But here is the problem the entire Microsoft corporation folder in the driver setup is missing. I am getting no help on the web on why this is so.
And this problem is not just on one board but on others as well. Boards used so far Intel Edison, Arietta G25.
Related
I have an application that requires an Ethernet protocol through a USB cable to control some device. All works under Win 7 using MS supplied RNDIS driver. My application also works under Win 10 Home or Student editions using an ACER supplied RNDIS driver, but not under Win 10 Pro. This might be because this application uses another network link (wireless) to access a database, and its Ethernet link could be in conflict with the wireless network through RNDIS driver under Win 10 Pro. How? What particular aspect of Win 10 Pro can cause this behavior and can we fix it?
Solution: An updated and signed MS RNDIS driver can be obtained by contacting Keynote Electronics to resolve the issues mentioned.
I have an "off the shelf" commercial software using an ANT USB dongle to communicate with a cycling trainer.
My trainer is not compatible with the software because the protocol is slightly different (not a lot).
My goal is to write a protocol translator. The only thing I can think of is to write a UMDF virtual device driver (like Magic ISO Virtual DVD) looking like an ANT USB Device in the device manager (same PID\VID) while connecting itself to the physical ANT device. The virtual device driver will perform the protocol translation.
I looked at several examples from Microsoft here https://github.com/Microsoft/Windows-driver-samples but I was unable to find anything relevant. I thought this example would be a good start https://github.com/Microsoft/Windows-driver-samples-master/Sensors/CustomSensors but it is impossible to load the driver using the given procedure from the inf file.
BTW I am familiar with the content of INF files and the basics of KMDF & UMDF device drivers programming. My problem is to write something that will load in the device manager and present itself as a real USB device even if it is not enumerated by the USB bus subsystem.
Can anybody with driver development experience point me to some relevant code sample or documentation?
Best regards !
I am currently developing a UMDF CCID (smartcard reader) driver. This project helped me at the beginning because it compiles out of the box and creates virtual device nodes (smartcard readers) visible in the device manager.
I'm manufacturing a device that connects to my computer using Bluetooth and then a desktop Java app uses the Bluetooth connection to send serial data to the device which is then displayed.
When I try to connect my device to windows 7 it successfully finds and pairs with it creating a Bluetooth link on a COM port. This link can then be used by a serial prompt (used for testing) or my Java application. It works initially however soon after windows drops the connection and the only way to reconnect is to delete the device within devices and printers and then reconnect.
This seems to be a known problem with windows bluetooth so I decieded to use a third party Bluetooth application. I downloaded and tried Toshiba's Bluetooth Stack and it was able to add a Bluetooth device and keep a stable connection which works great however this only works for Toshiba computers without getting a cracked version.
This device is commercial and can't be sold with cracked versions of software. Has anybody experienced the same problems or not in other operating systems and has any solutions of advice as that would be a tremendous help.
This is not a good idea/method to use the COM ports generated by Windows, it's not working fine and not reliable in any scenario ; you should use Bluetooth Sockets instead.
Using Toshiba or Widcomm or BleuSoleil won't help: under Win7, all dongles are now trying to use the Microsoft Stack, not their own implementation.
I have a Win7/64 development machine configured (by someone else I can't contact) to develop/debug an embedded project using an ST-LINK/V2 dongle. The PC detects and installs the dongle Ok but no application can access the dongle, giving 'No ST-Link device detected' type errors.
What makes this so frustrating is I have another Win7/64 machine that works flawlessly using identical driver, software and dongle and I haven't been able to transfer the dev environment between machines.
I've found (using USBlyzer) that WinUSB returns IRP Status STATUS_ACCESS_DENIED to each dongle access request. I'm hoping someone has seen something like this before.
P.S. "STMicroelectronics STLink dongle driver" is dated 28/07/2010.
The difference is not with the development software but the USB driver installed in the OS for the class of the ST-LINK/V2 dongle. The original installation installs a custom driver to support the dongle. Note that there is a different USB driver for Windows 8 and for Windows 7. STM has a site for the appropriate custom Windows drivers as well as firmware updates for the processor in the dongle, itself.
I've been asked to help with some problems that a company are having with an Windows installer they have that includes some custom driver installation for some hardware they make.
I've got access to the source code to build the software and installer (which is an WIX/MSI one), but don't have access to the hardware, so can't actually test it properly.
Is it possible (either with a toolkit, or without) to trick windows into thinking that a specific device USB device has been attached to the computer in order to trigger Windows into trying to install the drivers? . I've got access to all the Vendoer Id, DeviceID, etc information.
Thanks
Tom
That should be possible. Take a look at WDK USBSamp and NDIS Virtual miniport (or virtual serial driver) samples. The first one is a USB driver sample and second one demonstrates how to build virtual driver. You should be able to combine the two to create a virtual USB driver.