Rndis Ethernet Gadget Driver Windows 7

[Donat Ruel]

Imight just be an idiot but why can i not find any info anywhere about installing this MFP as a USB device? I tried installing the software first like any good user would when dealing with USB but it asks for a networked device right off the bat. I tried plugging it in to the USB type b port on the back of the printer but all it did was install some RNDIS Ethernet usb adapter.

you would think. Im worried about the port i plugged in to tho. The type B connector is possibly a piggyback on the network jack, I brought a type A to type A cable in today to try to pug into those jacks on the back of the printer.

This attached collage is what im working with. The top left pic shows what happens when I plug the printer into the PC using the TYPE B connector on the back of the printer (number 5 on the top right image). NOTHING happens when i plug into the TYPE A connector (number 4 on the top right image - either one).

ps. I had an older xp machine that i used first. When i plugged the printer in to the type b, i was able to use the windows update catalog to find a driver for the ethernet bumbo-jumbo. That still didnt do anything near what I needed. This is a win7 machine now. I wanted to take the machine out of the equation. I believe this is now an issue with the printer.

This is not my first rodeo with printer installs. that is why im banging my head against the wall here. I actually need the scanning capabilities of it. I dont care if it prints. Its on loaner while the other scanner (flatbed) is being fixed. The program that needs this can only scan from a usb port. This is the reason for the hoop jumping.

Do RNDIS driver exists for Windows ARM?

Did someone already tried what i'm are trying to doand got it to work ?

Is there a way to install the drivers i have for AMD64 and x86 on the ARM64 version?

Unfortunately RNDIS/Ethernet Gadget is not a compatible hardware for Windows IoT (ARM), there for the driver is not available. You can check the hardware type compatibility list here: -us/windows/iot-core/learn-about-hardware/hardwarecompatlist

I noticed when connecting via USB Ethernet gadget/RNDIS on a Windows 7 Professional 64 bit OS that wired Ethernet becomes disconnected. Upon removing the USB cable connected to the Linux target, thus disconnecting the USB Ethernet gadget/RNDIS, wired Ethernet activity will resume. I have witness this on multiple PCs.

I have an AM1808 EVM connected to a Windows XP laptop via the USB RNDIS driver. I have pinged and telneted to the board with no problems. And the Ethernet connection is working, too. I do not have Windows 7 to test.

We are using SDK version 05.05 which contains kernel version 2.6.37. We noticed that the Ethernet drop when using USB RNDIS is not always immediate. Usually within 10 minutes the Ethernet of the host machine will drop out. I have also seen USB connections on the host machine, other then the USB RNDIS connection drop out as well. This happens on Windows 7 Professional 64 bit. We have seen the Ethernet drop out on the following host machines Fedora, Windows XP, and Windows 7 machines. Once the RNDIS connection is terminated USB and Ethernet activity in the host machine will resume.

I took a look at the kernel that ships with the AM335x EZSDK (3.2.0) and it seems to have incorporated the fixes from the above link. I did not do an exhaustive compare of the four sources modified by the patch, but I did do a diff of cppi41_dma.c between 2.6.37 and 3.2.0 against the patch log and saw the changes were incorporated into the newer kernel.

I am running a continuous ping test from my Win7 64-bit machine over RNDIS with a 65500 byte payload. It has been running for a little over an hour now. This is without any kernel patches, BTW. I do get the occasional single timeout.

Curiously, while Todd has experienced the USB Ethernet Gadget causing his wired network to stop functioning on his Laptop running Windows 7 64-bit, I have not reproduced that problem even though my Laptop is the same make and model and I am also running Windows 7 64-bit.

While Mellissa may not have experienced the USB Ethernet Gadget issue on her system, the issue has been noted on multiple systems throughout the department. I have experienced the issue on two different systems operation with Windows 7. Others within the department have noted the issue on Windows XP and Fedora systems.

I'm curious, does the wired Ethernet connection die on Todd's machine and not yours using the same board? Have you two compared Win7 RNDIS drivers? I've pasted mine below as a reference. Let me know if either of you are using a different driver, and perhaps I can try testing with that driver.

Last week I received a new laptop. The laptop is operating with Windows 7 64bit. I will also compare the drivers of the new machine and test to see if the issue is present with the new machine as well.

If you have a moment to uninstall the current RNDIS drivers and give these a try on a machine that you've been having these problems, it would be a big help. I've ran these drivers on Win7 32 & 64-bit machines with success (trying to hunt down an XP machine). I will run another longevity test today, but everything is behaving for the time-frame you're seeing problems. I'll update if/ when I do see a disconnection.

A lot of throughput is required to cause the host PC's Ethernet to lock-up. We only host a few configuration and status web pages via RNDIS/Ethernet Gadget. 5Gb far exceeds the throughput during the time it takes to cause the Ethernet to lock-up. The host PC Ethernet does not require a lot of traffic to aggravate the issue. Usually the host PC's Ethernet is pretty idle when the issue occurs.

As of early last night I was able to connect the BBB via USB to my desktop PC and see the BBB mounted to my PC. There were entries in the device manager for the Beaglebone (under Portable Devices), the Gadget Serial (under Ports COM & LPT), and the Linux RNDIS Ethernet gadget (under Network Adapters and shows up as Linux USB Ethernet/RNDIS Gadget #2 for some reason). The RNDIS entry showed device error 10 saying that the device was not able to start. I have installed the drivers through the BONE_D64 executable as well as by trying to manually update the driver and point it to the RNDIS driver located at F:\Drivers\Windows\src\files\RNDIS. Later last night I tried uninstalling all of the BBB entries I could find within the device manager (the three I listed above) and used bcdedit to allow the installation of digitally unsigned drivers thinking that perhaps Windows was blocking the install somehow. I restarted my PC, installed the drivers, re-enabled driver integrity checks with bcdedit and restarted my PC once again. This was unsuccessful and I was still unable to get the Linux USB Ethernet/RNDIS Gadget to start properly.

I have personally experienced similar issues with the same version of Windows, and my own recourse is just to reinstall. One thing you can do to help facilitate this is to keep the OS separate from your data ( e.g. two partitions, 1 for OS, one for data ). It wont keep the OS from eventually loosing its mind, but it should keep your data safe, and make it very simple to reinstall.

I faced similar problem for the BBB that I bought couple of days back. I was using Windows XP and Windows 7, but could not identify the exact issue. I did reinstalling all the drivers as suggested but did not work.

I have borrow BBW from element14,

Since last 4 months I am doing hands on experience on this devices and goiung good,

But since lase two days this board hase stopped detecting on desktop and Iam unable to solve it ,

Please help on this to solve it.

An Ethernet controller can add lots of complexity and cost to an embedded board, and consume a large amount of PCB real-estate. Most consumer embedded systems omit an Ethernet port completely, as do some development boards (such as the Atmel AT91SAM9RL-EK board). While testing a product or designing a system, it may be desirable to use Ethernet to transmit data to and from the device. Fortunately, the Linux USB gadget subsystem provides a way to leverage existing hardware (many devices have a USB device port) to use utilities such as NFS, SSH, and FTP. This is accomplished by using the g_ether driver.

The g_ether driver can be built into the kernel, or loaded as a module. Once the driver is loaded, it creates an interface called usb0 on the target. Once the USB cable is connected to the host, it creates an interface known as usb0 on the host machine. The host can be either Windows or Linux, but an extra driver is required to see the device on a Windows host. Once the interfaces exist, they can be treated as if they were normal Ethernet interfaces.

with TorizonCore 5.4.0 and a configuration file to enable Ethernet-over-USB via gadget/sysfs very similar to the one in this other post, I am able to communicate with a Windows host using RNDIS driver, but I still have to select it manually on the Windows PC (Device Manager > Unknown device > Update driver > Browse manually > Network adapters > Microsoft > Remote NDIS compatible device).

On the other hand, I know Toradex Easy Installer is configured well enough so that Windows is able to select automatically the driver and the Ethernet-over-USB interface goes up without manual driver selection on each board-PC pair.

I had a look at and compared the /sys/kernel/config/usb_gadget/ folders on my setup and TEZI, but I have not understood which settings is critical for that Win driver mechanism. Mine is very similar to the one in the post linked above.

On the other hand, the Toradex Easy Installer was always inducing the correct driver to be picked automatically by Windows. I have tried to reconstruct the configuration steps by TEZI v2.0b6 but I think they are hardcoded in this executable:

Hi @henrique.tx !

Thanks for the answer and the links. Yes of course, you can find my configuration below the signature. It is quite similar to the post you have mentioned. I also had a look at the kernel documentation, as a next step I will dive into it if you cannot find a difference between your closed-source TEZI configuration and mine.

Bests,

ldvp

3a8082e126