Legacy download files. Legacy PROWIN32 and PROWIN64 download packages provide PROSet, driver, ANS, FCoE, and DCB support for Windows 7. and Windows Server 2008 R2. How to find and download network driver. Data Center Mobile: Lenovo. Drivers & Software. On Windows 10, a device driver is an essential piece of code, which allows the system to interact with a specific hardware (such as graphics card, storage driver, network adapter, Bluetooth, etc.

• Drivers Rs-cv0c Data Device Network & Wireless Cards Free
• Drivers Rs-cv0c Data Device Network & Wireless Cards Using

Last updated on February 9th, 2016

Network Adapter Code 31 error in Device Manager may occur in a Windows based computer (Windows 10, 8, 7 or Vista) if the appropriate driver for the Network (Ethernet/LAN) controller is not installed properly or is corrupted. The full description of the 'code 31' error in 'Device status' information box is:

'This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)'.

When the Code 31 error occurs in one (or more) device(s), then the corresponding device appears with a yellow exclamation mark sign, next to it, in Device Manager.

In several cases the Ethernet 'Code 31' error, can occur despite the fact that the correct driver of the Ethernet controller is already installed. At these cases you have to perform some additional steps to resolve the error code 31 in your Network Adapter.

This tutorial contains detailed steps and instructions on how to resolve Ethernet Controller Code 31 error in Device Manager.

How to Fix the Network Controller Code 31 error in Device Manager.

Solution 1. Install the latest driver for Network Controller to fix the Network Adapter Code 31 error.

Step 1. Download the latest Network Adapter Drivers.

1. From another computer, navigate to your computer's manufacturer support site (if you own a branded PC or laptop) or to the motherboard's support site (for onboard network adapters) and download the latest driver version for the Network Controller. After the download, copy the driver to a USB drive and then transfer the downloaded driver to the problematic computer.

Step 2. Install Ethernet Adapter Drivers.

1. Follow the manufacturer's instructions to install the downloaded Ethernet adapter driver on your computer.

2. Check if your Ethernet Controller is working properly. If Code 31 error is still displayed in Device Manager, then proceed to Solution 2.

Solution 2. Remove Invalid Registry keys & re-install LAN Adapter drivers to resolve the Code 31 error in Network Adapter.

Step 1. Open Registry Editor & Backup Registry.

Open Registry editor. To do that:

1. Simultaneously press the “Win” + “R” keys to load the Run dialog box.

2. Type regedit and press Enter to open Registry Editor.

IMPORTANT:Before you continue, first take a backup of your registry. To do that:

• From the main menu, go to File & select Export.

Specify a destination location (e.g. your Desktop), give a filename to the exported registry file (e.g. “RegistryUntouched”), select at Export range: All and press Save.

Step 2. Delete invalid registry keys.

1. After you have backed up your registry, navigate (from the left pane) to this key:

• HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetwork

2. Now look at the right pane to find and delete the following (REG_BINARY) value:

• config

(HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetworkConfig)

3. Close Registry Editor.

Step 2. Uninstall the Network Adapter from Device Manager.

1. Open Device Manager. To do that:

1. Press “Windows” + “R” keys to load the Run dialog box.
2. Type “devmgmt.msc” and press Enter.

2. Expand Network Adapters.

3. Right-Click at the yellow-marked Ethernet Adapter and select Uninstall. *

* Note: If asked, do not remove the driver files from the system. It is not necessary.

4. Restart you computer and let Windows install the Ethernet drivers automatically. *

* Note: If Windows cannot find the appropriate driver for the Ethernet Controller or if you have deleted the driver during uninstall then you have to download and install the latest driver version for your Network Adapter from the manufacturer's support site.

That's it!

This article explains how to enable the CAN bus using as examples the AM35x EVM and OMAP35x, but can be applied to other platforms as well. In addition, steps to exchange data with a MCP2515 Bus Monitor board is also documented.

If you are new to CAN, please spend 15 minutes reading the CAN bus protocol technical overview.

• 2Enable the CAN controller kernel driver
• 5Verifying CAN support configuration
  • 5.2sysfs entries
• 10MCP251x interrupt signal
• 11Problems and how to resolve them
• 12System files and command

Drivers Rs-cv0c Data Device Network & Wireless Cards Free

References

Enable the CAN controller kernel driver

AM35x kernel

In the case of the AM35x platform the configuration is:

OMAP3x kernel

In the case of the OMAP3x platform with a MCP2515 chip the configuration is:

Enable socketcan and ip tools

Working with the CAN bus requires enabling the 'ip' tools from iproute2 package (the 'ip' tool from busybox won't work). The socketcan package is optional and provide you with tools to debug your can bus.

These packages are available for selection from the RidgeRun SDK in the configuration menu.

Setup the networking rules

Edit your /etc/networking/interfaces on the target file system and add the following rules (required to setup the bit-rate of the bus):

Verifying CAN support configuration

Linux boot

Look for the following in the Linux boot output

Run

Expected output:

Run

Expected output:

sysfs entries

Verify the CAN host driver is registered correctly (meaning properly added to kernel arch/arm/mach-*/board-*.c file).

MC2515

Run:

Expect:

Power on CAN hardware

Send simple test packet

The socket-CAN tools include the cansend utility:

where the device is the network interface name, typically can0, and a CAN frame is in the format:

with the can_id having 3 (SFF) or 8 (EFF) hex chars. and data in the format of zero to eight 8-bit hex-values that can optionally be separated by a period ('.') or use R for remote transmission request.

To send a CAN data frame message, with a can_id arbitration field value of 0x5A1 and a data field value 0x1122334455667788:

If you are using a CAN bus monitor, like the MCP2515 bus monitor, You will see (packet sent 3 times):

Dump received packets

The socket-CAN tools include the candump utility, which dumps all messages being exchanged on the CAN bus. To run candump, just specify the CAN interface:

If a device on the CAN bus sends a packet with ID 0x456 and data 0x122345, the output would be

The MCP2515 bus monitor allows you to send CAN bus packet. You can also telnet into the target hardware and use cansend to put a packet on the bus that can be monitiored with candump.

creates the following cumulative candump output

CAN protocol stack information

The CAN protocol implementation version:

The CAN bus statistics:

MCP251x interrupt signal

MCP251x Platform Bus Data

In the architecture specific board file, such as arch/arm/mach-omap2/board-overo.c, first define the platform data:

Add the SPI information to the SPI board info array:

Finally call the GPIO interrupt initialization function right before registering SPI board info:

GPIO MCP251x interrupt verification

You can use debugfs to monitor the GPIO used for the MCP251x interrupt signal.

Configure the kernel to enable debugfs:

Boot the target hardware and mount debugfs:

Check the current value and configuration for the GPIO of interest (for example GPIO 147):

with example output being:

Which indicates GPIO 147 is configure as an input, currently has a high logic level, is mapped to IRQ 307, and causes an interrupt on the falling edge.

You can see if any interrupts have occurred using (for example GPIO 147 being mapped to IRQ 307):

with example output being:

which indicates 60 interrupts have been occurred.

With OMAP3, you also need to verify the pad where the signal leaves the chip is configured properly. For the OMAP3 in the CBB package (used on Gumstix Overo Water board) GPIO147 uses the uart2_rx pad.

with example output being:

Problems and how to resolve them

The titles of the following sections are text that gets displayed when a problem occurs. Each section describes how to resolve the issue.

No can0 interface

If you have problems with network interface can0 not being created, enable

and

kernel -> Networking support -> CAN bus subsystem support -> CAN Device Drivers -> CAN devices debugging messages

bit-timing calculation not available

Enable CAN bit-timing calculation in the Linux kernel.

Drivers Rs-cv0c Data Device Network & Wireless Cards Using

bit-timing not yet defined

First run

then run

MCP251x didn't wake-up

If the response to ifconfig can0 up is

Then there is a problem with the interrupt signal from the MCP251x chip back to the driver. Check the arch/arm/mach-*/board-*.c file for your hardware along with any jumpers on your hardware design.

ip command says link/[280] instead of link/can

You need to enable and build iproute2 to get an up-to-date ip command that supports the can bus.

NOHZ: local_softirq_pending 08

You are using an older version of the mcp2515 driver. The driver should call netif_rx() only from interrupt context. Update to a newer version of the driver and the warning will go away.

System files and command

Files

Commands Examples

References