resume by usb device

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature currently requires accessing the site using the built-in Safari browser.

• GAMING Motherboards (MEG / MPG / MAG)

Resume by USB Device

• Thread starter fadsarmy
• Start date Dec 30, 2018
• Dec 30, 2018

Hello, I have a question about "Resume by USB Device" under Bios/Settings/Advanced/Wake Up Event Setup . When enabled, I thought that the USB mouse/keyboard only wakes up the pc from sleep mode, but it also switches the pc on when it is off. Is this normal? My motherboard is Z270 Gaming Plus.  

Active member

• Dec 31, 2018
• Jan 1, 2019

Hello, Bios version is 7A75v16. I only have a USB keyboard and mouse connected. I quite like the fact that I can switch my pc on using the mouse and keyboard but just thought this was unusual. This is my first MSI board and non of my other boards have done this. Happy new year.  

Thanks for your prompt reply. Your assumption is absolutely correct. I just checked the bios and it says "enable usb to wake up system from s3, s4 and s5 sleep states". I didn't realise what s5 was. It appears that s5 means pc is off so it looks like this is normal behaviour. I was under the impression that usb only wakes up the pc from sleep state but it also wakes up the pc from s5 state which is not really a sleep state. Appreciate your help anyway. https://docs.microsoft.com/en-us/windows/desktop/power/system-power-states  

Attachments

I set ErP Ready to enabled and now my pc is behaving normally, many thanks for that, really appreciated. I don't use fast start up as it doesn't really make much difference with an ssd and also because it creates unnecessary writes. I have always disabled fast boot in bios and windows. I have also disabled hibernation so windows fast boot and hibernation options are no longer present in power management.  

yusufadam date=1546309472 said: I set ErP Ready to enabled and now my pc is behaving normally, many thanks for that, really appreciated. Click to expand...

thuanpacki154202d8

• May 23, 2022

I'm having the situation. ErP On: cannot wake my PC from sleep. ErP Off / Wake up Event Setup as below: Resume by USB device Enable: can wake my PC from sleep, but also power on my PC (from completing shutdown). Resume by USB device Disable: cannot wake my PC from sleep and does not power on (from completing shutdown). I have a Logitech wireless mouse and a USB keyboard. Unchecked Turn on fast start-up and Hibernate. I just only want my PC can wake up from the sleep (by moving mouse/keyboard), not power on my PC this way. Very annoying. Hope someone can help. Thanks.  

laurence1211

Well-known member.

thuanpacki154202d8 said: I'm having the situation. ErP On: cannot wake my PC from sleep. ErP Off / Wake up Event Setup as below: Resume by USB device Enable: can wake my PC from sleep, but also power on my PC (from completing shutdown). Resume by USB device Disable: cannot wake my PC from sleep and does not power on (from completing shutdown). I have a Logitech wireless mouse and a USB keyboard. Unchecked Turn on fast start-up and Hibernate. I just only want my PC can wake up from the sleep (by moving mouse/keyboard), not power on my PC this way. Very annoying. Hope someone can help. Thanks. Click to expand...

😈Demon God😈

• May 24, 2022

• Developer Help
• What's New

Reset, Suspend, and Resume Commands

In addition to the  control commands  sent to devices during operation, three unique signaling conditions can be issued by the host: reset, suspend, or restore a suspended device.

During the  enumeration process  the host issues a reset signal to the device. This USB reset is not to be confused with hardware or Power-on Reset (PoR). The purpose of the USB reset is to set the software state of the device so enumeration can proceed.

Devices recognize a reset condition when both D- and D+ are both held low (SE0) for 10 ms. In some cases, the device is able to detect the reset within 2.5 µs, however, the host will maintain the R=reset condition for the entire 10 ms.

To initiate a reset, D+ and D- are held low by the hub. Having the hub hold the data lines low allows the host to continually service the other devices and avoid having devices enter Suspend mode for lack of activity on D+ and D-. The host causes the hub to reset a device by issuing a SET_PORT_FEATURE(PORT_RESET) control command to the hub.

Back to Top

A device will enter the suspend state when no start-of-frame signal is received for three consecutive frames. The application software running in the device is usually notified when a suspend occurs and may take action to reduce power consumption. When in Suspend mode, the device will draw no more than 50 ma. Suspended devices are able to respond to reset and resume commands.

The host can cause one enumerated devices to be suspended by issuing a SET_PORT_FEATURE(PORT_SUSPEND) control command to the hub attached to the device to be suspended.

The sequence to resume a device's operation is to assert a K-state on D+ and D- for 20 ms.  The K-state is defined in the USB specification and is determined by the USB speed .

A suspended device may be returned to an operating state (i.e., resumed) in one of two ways:

• If the device has the remote resume feature set after at least 5 ms in the Suspend state, the device can initiate the process of resuming normal operation. To begin resumption, the device asserts the K-state on D+ and D- for between 1 and 15 ms. The host (i.e., hub) will detect this state and take over controlling D+ and D- in 1 ms for the remainder of the 20 ms. After 20 ms the device will resume normal operation.
• The Host can resume a device by sending a CLEAR_PORT_FEATURE( PORT_SUSPSEND) to the hub connected to the device. This will cause the hub to drive the K-state on D+ and D- for 20 ms.
• USB Enumeration
• USB Type-C ®  Nomenclature and Features
• USB Speeds and Specifications
• Developing USB Applications with Microchip

On This Page

Microchip support.

Query Microchip Forums and get your questions answered by our community:

    Microchip Forums   AVR Freaks Forums

If you need to work with Microchip Support staff directly, you can submit a technical support case. Keep in mind that many questions can be answered through our self-help resources, so this may not be your speediest option.

    Technical Support Portal

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Turn on computer with USB keyboard through PS/2 adapter

I want to wake-up my PC by USB keyboard connected through PS/2 adapter. According to BIOS settings:

Resume From S3/S4/S5 by PS/2 keyboard ... [Any Key]

it should be working, but doesn't.

If I connect USB mouse as I did for keyboard & set up in BIOS:

Resume From S3/S4/S5 by PS/2 Mouse ... [Enabled]

it works - PC wakes-up when I pressed a mouse button.

Is it possible to wake up my PC with my keyboard?

• 1 Check PS/2 standby power jumpers on the motherboard. Try another keyboard. Try to light some of the Caps/Num/Scroll-Lock lights and get you PC into standby - if the lights go off then either your motherboard or your keyboard does not support this mode. Your keyboard may require more power than your motherboard supplies in standby mode. It is also possible that your motherboard resets your keyboard before turning it off, so the keyboard cannot properly detect if it is connected to PS/2 or USB port. –  Jack White Jul 19, 2016 at 16:09

2 Answers 2

Might be you are missing Chipset Driver, Try installing latest chipset drivers of your motherboard and check it.

Also if your mother board is of Biostar you can check the following question

How to use keyboard or mouse to power on or resume the motherboard? If use USB keyboard or mouse, press Delete key in POST screen to go CMOS> Advanced> Power Configuration> USB wakeup From S3/S4 set this function Enabled. Also need to set JSUBV1 and JUSBV2 to pin 2-3 for motherboard to provide 5V stand-by power to USB devices for resume. If need to power on motherboard through PS2 keyboard or mouse, press Delete key in POST screen to go CMOS> Advanced> SuperIO Configuration> Keyboard PowerOn / Mouse PowerOn. Set these two functions to Enabled. Save the CMOS setting and make sure system reboot once to POST screen then use power switch to turn off system power. It will be able to use keyboard or mouse for power on at S4 or S5 condition. Note: Turn off PSU power source or unplug the power cord will cause PS2 keyboard or mouse power on function fail. This function will be able to use again after system reboot once. src= http://www.biostar.com.tw/app/en/support/faq_content.php?S_ID=459

• 1 This does not answer the question. OP has a MSI mobo. You didn't even read the question. –  guest Jul 20, 2016 at 7:30
• @guest, Yes you are correct I didn't notice that he has added his PC config details, But I also has asked him to install his chipset driver and check it OP has to comment for this. –  smali Jul 20, 2016 at 8:29
• Windows is already shipped with generic drivers. What specific chipset driver do you think is missing? And what does it has to do with the question at hand? –  guest Jul 20, 2016 at 8:54
• that is what sometimes generic drivers wouldn't work as expected and not enable critical functionality, with each motherboard will get vendor specific drivers included in the package. I'm asking him to try once installing that I'm just guessing that it will work if he install that. –  smali Jul 20, 2016 at 8:56

If you are using a USB-PS/2 adapter then the computer sees the attached keyboard and mouse as USB devices, not PS/2 devices. Pressing a mouse button to wake the machine likely works and the keyboard does not because of some other setting elsewhere, as in the USB keyboard and mouse settings. Change the USB settings to match your desired behavior or use the PS/2 ports on the computer, as opposed to ones on a USB adapter.

• Re "If you are using a USB-PS/2 adapter then the computer sees the attached keyboard and mouse as USB devices, not PS/2 devices." : That seems unlikely. Does a PS/2 port carry USB signals? Do you have a source? –  Peter Mortensen Jan 28, 2023 at 3:06

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged usb keyboard bios wake-up ..

• The Overflow Blog
• Supporting the world’s most-used database engine through 2050
• What language should beginning programmers choose?

Hot Network Questions

• How to view operator norms on open-system representation of quantum channels
• FX Strangle Market Conventions
• How to solve this kernel-panic on a Debian 12 system?
• Can copy-pasting a word definition from a dictionary site cause a copyright issue?
• Angle between 3 points defined with coordinate
• Logic to check if app was launched for the first time using DataStore
• Book series about a guy who wins the lottery and builds an elaborate post-apocalyptic bunker
• Poisson equation and gravitational potential
• "You'll set me off"
• Why is recovery mode not read-only?
• Top of the World
• Why use a special "Name" class (instead of just a string) for representing object names in C++?
• Meaning of "too silver for a seam" in "A Bird, came down the Walk"
• Are there any languages where conditions are not first-class expressions?
• How are Gimli's athletic abilities in the books?
• Is there a different way to measure speed, other than with time?
• Using DeleteDuplicates with choosing which item of the pair should be deleted
• When or where did Gustave Flaubert say that Alexander Pushkin's work was "dull"?
• Relativity of Time from an Observer Perspective
• My paper has been rejected for accusations of "gift authorship", what now?
• Ubuntu 24.04 getting error You must put some 'deb-src' URIs in your sources.list when issuing apt-get build-dep
• Problem 5C.3 Isaacs' Finite Group Theory
• A simple cross-number puzzle
• Finding a more efficient solution to a trigonometric identity problem.

Contribute to the Windows forum! Click  here  to learn more  💡

April 9, 2024

Contribute to the Windows forum!

Click  here  to learn more  💡

Windows 8.1 Top Forum Contributors: Bill Smithers 👍✅

April 17, 2024

Windows 8.1 Top Forum Contributors:

Bill Smithers 👍✅

• Search the community and support articles
• Windows 8.1
• Search Community member

Ask a new question

How to reactive USB devices when resume from sleep?

After resume from sleep, all usb devices are lost response, include usb mouse and usb harddisk. 

I tried disabled usb selective suspend setting in power options and unchecked allow computer turn off this device to save power, but it still not working.

Btw： I have 3 usb ports on my laptop,  one is power station, means this port always working even laptop power off. The power station is not effect by sleep.

Report abuse

Was this reply helpful? Yes No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

Thanks for your feedback.

Replies (6) 

Question info.

• Devices & drivers
• Norsk Bokmål
• Ελληνικά
• Русский
• עברית
• العربية
• ไทย
• 한국어
• 中文(简体)
• 中文(繁體)
• 日本語

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

How to implement function suspend in a composite driver

• 2 contributors

This article provides an overview of function suspend and function remote wake-up features for Universal Serial Bus (USB) 3.0 multi-function devices (composite devices). In this article, you'll learn about implementing those features in a driver that controls a composite device. The article applies to composite drivers that replace Usbccgp.sys.

The Universal Serial Bus (USB) 3.0 specification defines a new feature called function suspend . The feature enables an individual function of a composite device to enter a low-power state, independently of other functions. Consider a composite device that defines a function for keyboard and another function for mouse. The user keeps the keyboard function in working state but doesn't move the mouse for a period of time. The client driver for the mouse can detect the idle state of the function and send the function to suspend state while the keyboard function stays in working state.

The entire device can transition to suspend state regardless of the power state of any function within the device. If a particular function and the entire device enter suspend state, the suspend state of the function is retained while the device is in suspend state, and throughout the device's suspend entry and exit processes.

Similar to a USB 2.0 device's remote wake-up feature (see Remote Wake-up of USB Devices ), an individual function in a USB 3.0 composite device can wake up from a low-power state without impacting the power states of other functions. This feature is called function remote wake-up . The feature is explicitly enabled by the host by sending a protocol request that sets the remote wake-up bits in the device's firmware. This process is called arming the function for remote wake-up . For information about the remote wake-related bits, see Figure 9-6 in the official USB specification.

If a function is armed for remote wake-up, the function (when in suspend state) retains enough power to generate a wake-up resume signal when a user event occurs on the physical device. As a result of that resume signal, the client driver can then exit the suspend state of the associated function. In the example for the mouse function in the composite device, when the user wiggles the mouse that is in idle state, the mouse function sends a resume signal to the host. On the host, the USB driver stack detects which function woke up and propagates the notification to the client driver of the corresponding function. The client driver can then wake up the function and enter working state.

For the client driver, the steps for sending a function to suspend state and waking up the function is similar to a single-function device driver sending the entire device to suspend state. The following procedure summarizes those steps.

• Detect when the associated function is in idle state.
• Send an idle I/O request packet (IRP).
• Submit a request to arm its function for remote wake-up by sending a wait-wake I/O request packet (IRP).
• Transition the function to a low power state by sending Dx power IRPs ( D2 or D3 ).

For more information about the preceding steps, see "Sending a USB Idle Request IRP" in USB Selective Suspend . A composite driver creates a physical device object (PDO) for each function in the composite device and handles power requests sent by the client driver (the FDO of the function device stack). In order for a client driver to successfully enter and exit suspend state for its function, the composite driver must support function suspend and remote wake-up features, and process the received power requests.

In Windows 8, the USB driver stack for USB 3.0 devices supports those features. In addition, function suspend and function remote wake-up implementation has been added to the Microsoft-provided USB generic parent driver (Usbccgp.sys), which is the Windows default composite driver. If you're writing a custom composite driver, your driver must handle requests related to function suspend and remote wake-up requests, as per the following procedure.

Step 1: Determine whether the USB driver stack supports function suspend

In the start-device routine ( IRP_MN_START_DEVICE ) of your composite driver, perform the following steps:

• Call the USBD_QueryUsbCapability routine to determine whether the underlying USB driver stack supports the function suspend capability. The call requires a valid USBD handle that you obtained in your previous call to the USBD_CreateHandle routine.

A successful call to USBD_QueryUsbCapability determines whether the underlying USB driver stack supports function suspend. The call can return an error code indicating that the USB driver stack doesn't support function suspend or the attached device isn't a USB 3.0 multi-function device.

• If the USBD_QueryUsbCapability call indicates that function suspend is supported, register the composite device with the underlying USB driver stack. To register the composite device, you must send an IOCTL_INTERNAL_USB_REGISTER_COMPOSITE_DEVICE I/O control request. For more information about this request, see How to Register a Composite Device .

The registration request uses the REGISTER_COMPOSITE_DEVICE structure to specify that information about the composite driver. Make sure you set CapabilityFunctionSuspend to 1 to indicate that the composite driver supports function suspend.

For code example that shows how to determine whether the USB driver stack supports function suspend, see USBD_QueryUsbCapability .

Step 2: Handle the idle IRP

The client driver can send an idle IRP (see IOCTL_INTERNAL_USB_SUBMIT_IDLE_NOTIFICATION ). The request is sent after the client driver has detected an idle state for the function. The IRP contains a pointer to callback completion routine (called idle callback ) that is implemented by the client driver. Within the idle callback, the client performs tasks, such as canceling pending I/O transfers, just before sending the function to suspend state.

The idle IRP mechanism is optional for client drivers of USB 3.0 devices. However, most client drivers are written to support both USB 2.0 and USB 3.0 devices. To support USB 2.0 devices, the driver must send the idle IRP, because the composite driver relies on that IRP to track the power state of each function. If all functions are idle, the composite driver sends the entire device to suspend state.

Upon receiving the idle IRP from the client driver, the composite driver must immediately invoke the idle callback to notify the client driver that the client driver may send the function to suspend state.

Step 3: Send a request for remote wake-up notification

The client driver can submit a request to arm its function for remote wake-up by submitting an IRP_MJ_POWER IRP with minor function code set to IRP_MN_WAIT_WAKE (wait-wake IRP). The client driver submits this request only if the driver wants to enter working state as a result of a user event.

Upon receiving the wait-wake IRP, the composite driver must send the IOCTL_INTERNAL_USB_REQUEST_REMOTE_WAKE_NOTIFICATION I/O control request to the USB driver stack. The request enables the USB driver stack to notify the composite driver when the stack receives the notification about the resume signal. The IOCTL_INTERNAL_USB_REQUEST_REMOTE_WAKE_NOTIFICATION uses the REQUEST_REMOTE_WAKE_NOTIFICATION structure to specify the request parameters. One of the values that the composite driver must specify is the function handle for the function that is armed for remote wake-up. The composite driver obtained that handle in a previous request to register the composite device with the USB driver stack. For more information about composite driver registration requests, see How to Register a Composite Device .

In the IRP for the request, the composite driver supplies a pointer to a (remote wake-up) completion routine, which is implemented by the composite driver.

The following example code shows how to send a remote wake-up request.

The IOCTL_INTERNAL_USB_REQUEST_REMOTE_WAKE_NOTIFICATION request is completed by the USB driver stack during the wake-up process when it receives notification about the resume signal. During that time, the USB driver stack also invokes the remote wake-up completion routine.

The composite driver must keep the wait-wake IRP pending and queue it for later processing. The composite driver must complete that IRP when the driver's remote wake-up completion routine gets invoked by the USB driver stack.

Step 4: Send a request to arm the function for remote wake-up

To send the function to a low-power state, the client driver submits an IRP_MN_SET_POWER IRP with the request to change the Windows Driver Model (WDM) device power state to D2 or D3 . Typically, the client driver sends D2 IRP if the driver sent a wait-wake IRP earlier to request remote wake-up. Otherwise, the client driver sends D3 IRP.

Upon receiving the D2 IRP, the composite driver must first determine whether a wait-wake IRP is pending from a previous request sent by the client driver. If that IRP is pending, the composite driver must arm the function for remote wake-up. To do so, the composite driver must send a SET_FEATURE control request to the first interface of the function, to enable the device to send a resume signal. To send the control request, allocate a URB structure by calling the USBD_UrbAllocate routine and call the UsbBuildFeatureRequest macro to format the URB for a SET_FEATURE request. In the call, specify URB_FUNCTION_SET_FEATURE_TO_INTERFACE as the operation code and the USB_FEATURE_FUNCTION_SUSPEND as the feature selector. In the Index parameter, set Bit 1 of the most significant byte. That value is copied to the wIndex field in the setup packet of the transfer.

The following example shows how to send a SET_FEATURE control request.

The composite driver then sends the D2 IRP down to the USB driver stack. If all other functions are in suspend state, the USB driver stack suspends the port by manipulating certain port registers on the controller.

In the mouse function example, because the remote wake-up feature is enabled (see step 4), the mouse function generates a resume signal on the wire upstream to the host controller when the user wiggles the mouse. The controller then notifies the USB driver stack by sending a notification packet that contains information about the function that woke up. For information about the Function Wake Notification, see Figure 8-17 in the USB 3.0 specification.

Upon receiving the notification packet, the USB driver stack completes the pending IOCTL_INTERNAL_USB_REQUEST_REMOTE_WAKE_NOTIFICATION request (see step 3) and invokes the (remote wake-up) completion callback routine that was specified in the request and implemented by the composite driver. When the notification reaches the composite driver, it notifies the corresponding client driver that the function has entered working state by completing the wait-wake IRP that the client driver had sent earlier.

In the (remote wake-up) completion routine, the composite driver should queue a work item to complete the pending wait-wake IRP. For USB 3.0 devices, the composite driver wakes up only the function that sends the resume signal and leaves other functions in suspend state. Queuing the work item ensures compatibility with existing implementation for function drivers of USB 2.0 devices. For information about queuing a work item, see IoQueueWorkItem .

The worker thread completes the wait-wake IRP and invokes the client driver's completion routine. The completion routine then sends a D0 IRP to enter the function in working state. Before completing the wait-wake IRP, the composite driver should call PoSetSystemWake to mark the wait-wake IRP as the one that contributed to waking up the system from suspend state. The power manager logs an Event Tracing for Windows (ETW) event (viewable in the global system channel) that includes information about devices that woke up the system.

Related topics

• USB Power Management
• USB Selective Suspend

Was this page helpful?

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback .

Submit and view feedback for

Additional resources

The computer stops responding when an USB device resumes from the USB Selective Suspend state in Windows 7 or in Windows Server 2008 R2

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.

You enable the USB Selective Suspend feature on a computer that is running Windows 7 or Windows Server 2008 R2. Then, the computer stops responding when one or more of the following conditions are true:

The computer enters the Sleep or Hibernate state.

One or more USB devices resumes from an idle state after a period of inactivity.

Note You can restart the computer to recover from this issue.

This issue occurs when an attached USB device resumes from the USB Selective Suspend state, and the USB hub incorrectly reports that the device is disconnected from the USB hub port. This incorrect status report may be caused by a hardware error in the USB hub or in the attached USB device. Then, the Microsoft USB hub driver (Usbhub.sys) incorrectly tries to obtain a spinlock that has already been obtained in the same thread. This causes a kernel-mode deadlock. Therefore, the computer stops responding.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

This hotfix can be applied on computers that are running Windows 7 or Windows Server 2008 R2.

Restart requirement

You have to restart the computer after you apply this hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows 7 and Windows Server 2008 R2 file information notes

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately . MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

For all supported x64-based versions of windows 7 and of windows server 2008 r2, for all supported itanium-based versions of windows server 2008 r2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

After you apply this hotfix, the issue described in the "Symptoms" section will not occur. However, the following issues may occur:

An attached USB device resumes from the USB Selective Suspend state when the computer is running. Then, Windows may report that the USB device is disconnected from the computer, or that the USB device is reconnected to the computer. Additionally, the affected USB device is unresponsive for several seconds to less than one minute.

When the computer tries to enter a Sleep or Hibernate state, there is no visible indication that an attached USB device is disconnected. When the computer resumes from the Sleep or Hibernate state, Windows reports that the USB device is disconnected from and reconnected to the computer.

To work around this issue, clear the Allow the computer to turn off this device to save power check box for the affected USB device or USB Root Hub:

Click Start , type device manager in the Start Search box, and then press ENTER. Note If you are prompted for an administrator password or confirmation, type your password and then click Continue .

On the View menu, click Devices by connection .

Expand the ACPI node, expand Microsoft ACPI-Compliant System , and then expand PCI bus .

Several USB universal host controllers will be listed.

Expand each USB universal host controller node, and then expand successive subnodes until you find the name of the USB device.

When you locate the affected device, right-click the device, and then click Properties .

If there is a Power Management tab, click the Power Management tab, and clear the Allow the computer to turn off this device to save power check box, then click OK .

If there is no Power Management tab, click Cancel , then double-click the associated USB Root Hub, click the Power Management tab, clear the Allow the computer to turn off this device to save power check box, then click OK .

Note You may have more than one attached USB device or USB hub. You can apply these steps to each USB device or USB Root Hub in turn to identify which one causes the issues. If the issue does not occur after you apply these steps to a particular device or USB Root Hub, then that device or USB Root Hub causes the issue. For more information about USB Selective Suspend, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/en-us/library/ms793200.aspx For more information about System Sleeping States, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/en-us/library/ms798270.aspx

Additional file information for Windows Server 2008 R2 and for Windows 7

Additional files for all supported x86-based versions of windows 7, additional files for all supported x64-based versions of windows server 2008 r2 and of windows 7, additional files for all supported itanium-based versions of windows server 2008 r2.

Need more help?

Want more options.

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders

Was this information helpful?

Thank you for your feedback.

Driver Engineer Resume Sample

The resume builder.

Create a Resume in Minutes with Professional Resume Templates

Work Experience

• Experience developing low level software in C++ or C
• Expertise in driver development and debugging
• Professional experience with USB technology and analyzers
• Experience with USB and driver development on Windows and Linux
• Familiarity with firmware and driver development on ARM SoCs
• Five years of experience with driver airbag and steering wheel interface design
• Knowledge of compiler architecture and optimizations
• Root cause analysis and resolution of U-Boot, kernel, driver related issues
• Develop Linux OS Install/Upgrade/Diagnostic tools, test shell/python scripts
• Attractive compensation and benefits
• Company pension with retirement benefits
• Lead the feature design, development and model development of new Radar, Ultrasonic, or Camera based driver assistance features
• Own Feature interfaces and develop interface requirements through all affective parties (Vehicle engineering, core and D&R engineering) of affected subsystems/components. Own feature description and communicate to vehicle teams /feature planning and marketing. Lead feature development
• Lead HMI strategy development with HMI and Ergonomics; Verify and confirm through customer clinics, surveys, TGW/GQRS feedback and refine as required
• Drive HMI strategy into implementing components (Switches/Instrument cluster displays, Center Stack displays, haptic feedbacks, other indicators) and lead approval process through appropriate governing bodies
• Understand the performance requirements for the sensors, establish feature model to operate within the sensor performance envelope, and establish procedures to verify performance both quantitatively and subjectively
• Oversee/Sign off of Feature Level performance per a given vehicle
• Own Feature interfaces and develop interface requirements through all effective parties (Vehicle engineering, core and D&R engineering) of affected subsystems/components. Own feature description and communicate to vehicle teams /feature planning and marketing. Lead feature development
• Collaborate with FPGA engineers for board bring-up, low-level kernel/driver
• Design, develop and evolve Imagination's WDDM graphics drivers
• A good view of systems architecture issues
• In software development desirable but not mandatory
• Linux device driver development and testing desirable but not mandatory
• Experience working with hardware systems in various states of design, development, and reliability is required
• Experience with software performance analysis, optimizations and low- level
• Experience in product development in the automotive industry
• Advancement and rapid career path for high achievers

Professional Skills

• Excellent troubleshooting and problem solving skills-Excellent verbal and written communication skills
• Strong written and verbal communication skillsExperience with logic analyzers and oscilloscopes
• Good problem solving skills coupled with a strong aptitude to learn and innovate
• Excellent communication skills
• Experience in device driver development in C/C++ -Experience with internals of Linux and/or Windows operating systems
• Experience as a proven driver information/infotainment tester with an OEM,
• Great self-management skills

How to write Driver Engineer Resume

Driver Engineer role is responsible for software, engineering, wireless, security, troubleshooting, architecture, integration, compensation, design, events. To write great resume for driver engineer job, your resume must include:

• Your contact information
• Work experience
• Skill listing

Contact Information For Driver Engineer Resume

The section contact information is important in your driver engineer resume. The recruiter has to be able to contact you ASAP if they like to offer you the job. This is why you need to provide your:

• First and last name
• Telephone number

Work Experience in Your Driver Engineer Resume

The section work experience is an essential part of your driver engineer resume. It’s the one thing the recruiter really cares about and pays the most attention to. This section, however, is not just a list of your previous driver engineer responsibilities. It's meant to present you as a wholesome candidate by showcasing your relevant accomplishments and should be tailored specifically to the particular driver engineer position you're applying to. The work experience section should be the detailed summary of your latest 3 or 4 positions.

Representative Driver Engineer resume experience can include:

• Strong C/C++ experience
• Experience working with automotive electronics
• Experience Control algorithm development using Matlab or Simulink
• Or longer academic or professional experience on the following areas
• Solid understanding of computer architecture and server platform hardware
• Self-motivated, ability to work in team environment, and excellent communication

Education on a Driver Engineer Resume

Make sure to make education a priority on your driver engineer resume. If you’ve been working for a few years and have a few solid positions to show, put your education after your driver engineer experience. For example, if you have a Ph.D in Neuroscience and a Master's in the same sphere, just list your Ph.D. Besides the doctorate, Master’s degrees go next, followed by Bachelor’s and finally, Associate’s degree.

Additional details to include:

• School you graduated from
• Major/ minor
• Year of graduation
• Location of school

These are the four additional pieces of information you should mention when listing your education on your resume.

Professional Skills in Driver Engineer Resume

When listing skills on your driver engineer resume, remember always to be honest about your level of ability. Include the Skills section after experience.

Present the most important skills in your resume, there's a list of typical driver engineer skills:

• Able to communicate effectively and work well in a team
• Experience developing/product improving the driver information/infotainment systems for a NAR OEM,
• Experience of testing and driving high quality/luxury vehicles,
• Software integration, debugging and testing experience
• Experience working with automotive electronics or in a similar area
• Experience Control algorithm development using Matlab, Simulink or equivalent

List of Typical Skills For a Driver Engineer Resume

Skills for driver development engineer resume.

• Experiences of embedded connectivity system (WLAN/LTE/UMTS) software development
• Experience with device driver development
• Experience in software optimization and Linux Driver (Kernel/User Space) code development
• Experience in development Linux environment
• Experience with performance benchmarks: analysis
• Experience in device driver development in C/C++

Skills For Driver Mode Control Calibration Engineer Resume

• Experience with performance benchmarks: analysis and optimization
• Experience with hardware / software partitioning is an advantage
• Linux network driver development experience is an advantage
• Confident in expressing one's ideas in a peer group and accepting if they're not adopted
• Develops and evaluates engineering designs (including subsystems)
• Motivated self-starter and hard working

Skills For Project Engineer Driver Information Resume

• Leads overall communication, coordination, and consultation with engineering departments and customers
• Linux device driver development and testing
• Deep knowledge of C, familiarity with C++, exposure to Shell/Python scripting
• An understanding of bus interfaces: I2C, SPI, UART, AXI, AHB, PCI/PCIe, etc
• Exposure to and understanding of ARM/Intel processor architectures
• Run benchmarks to understand system performance using tools like emon/perfmon/VTune
• Embedded Linux software development of WLAN communication system, including kernel level driver development and applications development
• New features implementation, unit testing and integration

Skills For Device Driver Development Engineer Resume

• Likes to take ownership and runs with issues to completion
• Understands complex ideas and communicates them clearly
• Able to understand and communicate complex ideas
• Lead the feature design, development and model development of new sensor and camera based driver assistance features
• Lead the development of Feature specifications, FMEAs, robustness disciplines and Design Verification Plans for advanced sensor and camera features
• Own feature interfaces and develop interface requirements through all affected parties (Vehicle engineering, core and D&R engineering) of affected subsystems/components. Own feature description and communicate to vehicle teams /feature planning and marketing. Lead feature development
• Understand the performance requirements for the sensors or cameras (both as a visual image and as a sensor), and establish procedures to verify performance both quantitatively and subjectively
• Understand system interactions in terms of vehicle dynamics to identify possible improvements and trade-offs. Identify changes needed to improve performance and meet objectives
• Provide technical leadership to cross-functionally drive Active Safety needs into HMI designs through the Infotainment and User Experience team

Skills For Ray Tracing Driver Software Engineer Resume

• Champion Driver Performance Studies & Requirements Development for Active Safety and Driving Automation Systems
• Generates technical solutions for current, new and major architectures
• Develops and performs complex design analysis
• Creates and balances requirements across systems
• Collaborate and thrive in a fast-paced high-performance environment
• Exposure to SW development in FPGA environment

Skills For Remote Micr Engineer / Driver Resume

• Familiarity with Source code management (GIT, SVN, CVS)
• Work and deliver under tight schedules
• Worked with VMM technologies like VMware/Xen/KVM/Hyper-V
• Experience with storage and networking protocols -Knowledgeable about FPGA, SR-IOV, DMA, PCIe, Graphics, and/or FPGA-Run benchmarks to understand system performance using tools like emon/perfmon/VTune
• Experience with internals of Linux and/or Windows operating systems
• Experience with storage and networking protocols
• Expertise with internals of Linux and/or Windows operating systems

Skills For Project Engineer for Advanced Driver Assistance Systems Resume

• Expertise in device driver development in C/C++
• Knowledgeable about FPGA, SR-IOV, DMA, PCIe, Graphics, and/or FPGA
• Mentor a team of engineers
• Experience in Linux embedded systems development, Linux OS internals, with real time schedulers, multi-threaded programming and inter-process communications in Linux OS environment is an advantage
• Embedded Linux software design aspects of WLAN communication system
• Deep knowledge of GPU and CPU architectures - Knowledge of compiler architecture and optimizations - Experience analyzing the performance of 3D applications - Experience with parallel and asynchronous processing
• Communication standards understanding
• Design documents maintenance
• Business travel

Related to Driver Engineer Resume Samples

Cdl driver resume sample, driver technician resume sample, van driver resume sample, delivery manager senior resume sample, delivery operations resume sample, fleet sales resume sample, resume builder.

• STMicroelectronics Community
• STM32 MCUs products

USB Suspend/resume in STM32F7

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Printer Friendly Page

• Mark as New
• Email to a Friend
• Report Inappropriate Content

‎2024-02-07 12:20 AM

• STM32F7 Series
• All forum topics
• Previous Topic

‎2024-02-07 01:58 AM

• STM32F7 Ethernet (Without FreeRTOS): Not Working (No Ping) in STM32 MCUs products 2024-04-25
• STM32Cubeprogrammer no target found in STM32CubeProgrammer (MCUs) 2024-04-24
• STM32F7 reads 4095 on all ADCs for the first 2.3 seconds after power on but not after reset in STM32 MCUs products 2024-04-20
• STM32F7 crash on HAL_UART_Transmit in STM32 MCUs products 2024-04-18
• How to get the value of the program counter ? in STM32 MCUs products 2024-04-17