Restart USB plugged device without restarting a computer - windows-xp

I am dealing with an issue that USB GSM modem throws an exception and is in the failed state until you SHUT DOWN and turn on the PC again.
The "restart" does not help, because it only flushes the memory (running on Windows XP, SP3 Pro.)
As I suspect, the problem might be solved when the USB's power goes off and on again.
But is there a way how to do it without shuting the whole PC down (Like remove and add the device in device manager)?
Also do you know how can I simulate this state? It happends randomely and I am unable to do it at my will.
Thanks

You say it is a USB device (i.e. not integrated). The only reliable way to re-power the device, apart from re-booting the PC, is to unplug and re-plug the device (which is quicker anyway).
There's a discussion here: http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/326d26e7-baa9-45b4-8234-321c9e5f8ffa/
The exception is happening in the device, and without knowing what causes it, you can't reliably reproduce it. Maybe the device vendor has some software that would help you collect its logs.

Related

Device descriptor request failed

I tried working with my RPi Pico today and my computer doesn't recognize the usb I triple checked the cable is power and data. And yes I'm holding the button
I've also had this annoying issue. Seems to happen even more often on the Pi Pico W.
Use my laptop USB-C port to connect via a USB-C to USB 3.0 hub and this happens every so often.
Bought a powered hub from Amazon: "UGREEN USB C Hub 4 Ports, USB C to USB Hub 3.0". It has a separate USB-C power input in addition to the laptop USB-C connection and it works fine when no other USB devices are connected to the hub. Seems to be an issue similar to what Foibled2 mentioned where the underlying issue may be power related.
I'm struggling with the same thing. Other than uninstalling in Device Manager and rebooting (sometimes several times) I can get it to recover.
There must be a better way.
I've seen references to Zadig, etc. But finally figured out the issue in my circumstance.
I disabled all of my other USB serial devices (Prolific USB for GPS tracker; and CH340 USB for Android Nano).
After that, I could plug / unplug my R Pi Pico between application and USB drive mode without rebooting.
Works now as advertised. Hope this helps short cut a few hours for someone else!

flutter doctor: device is offline

After running Flutter doctor to see why my physical LG G6 device was not being picked up, I found out that the "Device is offline".
I've tried googling around, and unplugging and re plugging the device.
Nothing seems to work.
What does this mean? My device does have debug enable, and it's definitely connecting to the pc and flutter definitely see it.
It could be a problem with the USB cable.
Had the same problem, then tried another cable, plugged in the same port as the old cable, and it didn't go offline.
If I plug in the old cable, the same problem happens: it goes offline after some time, even though it's connected, and I can see my device's files in Windows.

"No ST-LINK detected" error message, when trying to connect with ST-LINK Utility

I have a
NUCLEO-F401RE board
(with STM32F401RE)
and it has been working fine for the most part. Here recently, I followed a tutorial in the book
"Mastering STM32"
where it says to install
OpenOCD.
I had been following along before this as well, and I had been able to connect to my board and flashing it with no problem.
After attempting to get OpenOCD to work though, this is no longer possible. Every time I try to connect to my board, I simply get the following error message:
No ST-LINK detected
I have tried updating the drivers multiple times, rebooting the board, reinstalling the ST-LINK Utility, switching the USB-Cable, resetting the board and reinstalling everything and I have also tried the trick where you hold down the reset button and try to erase the chip.
So far, none of this has worked for me unfortunately.
Here you find a picture of my board.
On my desktop, I am using Windows 10. On my board, and I am using FreeRTOS.
Here you find an image of my Windows Device Manager.
I have also tried to update the firmware on my board using the ST-Link upgrade, but without luck. When attempting this, I either do not have the option to select my device (when using the .jar app) or when using the .exe app, I just get the following error messages:
No ST-Link device detected
Please connect it and then retry
I have not been able to find a solution for this anywhere, so I hope you guys can help! If you need any further relevant information, just let me know. Thank you very much.
As mentioned in other answers, the problem is almost certainly due to a competing driver (something like libusb) taking control of the device.
However, you do not need to "uninstall and reinstall everything" to select the correct driver, assuming that you have already installed it once before. Moreover, the reinstallation procedure most likely won't help, because the uninstallers usually do not uninstall the drivers anyway, and Windows will keep prefering the same wrong driver.
Instead, open Device Manager, find your STM32 STLink device, double-click to open the Properties dialog. Then click "Update Driver", then "Browse my computer for driver software", then "Let me pick from a list of available drivers on my computer", and you should see something like that:
You see that in this example, at least four different drivers available on the system are happy to service the device. The first two are generic libusb drivers, not specific to the dongle (OpenOCD is happy to use either of those, if I remember correctly). The ST-Link utility, however, wants a dedicated driver, developed by STM - those are the two entries below on my picture. If you do not see those, try installing the ST-Link utility again (no need to uninstall anything) or download just the driver from the STM website.
You can now click on the preferred driver in this list and have it replace whatever driver was assigned to the device before.
From my poor experience the "No ST-LINK detected" message in the STM32 Utility shows when you are disconnected or when other program is using a ST-LINK. So, if this start happens after installing OpenOCD try to uninstall this and try again (maybe with option "Connect under reset"?).
For your information. When you plug the cable to the PC and the board is power on then in the settings (STM32 Utility) you can see available ST-Links (even blocked). Here is example when ST-Link is blocked
From what I have learned and understood (but everyone can correct me :)), your board is divided in two parts :
The ST-Link debugger part ;
The rest with the actual microcontroller.
The ST-Link part is used to flash the microcontroller and can be used to flash any other STM32F4 device through SWD. With your picture :
The STM32 ST-Link Utility uses the ST-Link part of your board to flash it. My point is that if you have the "No ST-Link detected", the issue, I am quite sure, doesn't come from the microcontroller part but comes from the ST-Link part. And since you did say that it worked before you install openocd, I would suggest the driver part in W10 that may be the root of your problems.
Try to uninstall everything (and I mean everything) related to the STM32 (openocd, STM32 ST-Link Utility and its driver through Device Manager).
Reinstall only STM32 ST-Link utility (if you did uninstall the drivers correctly, it should ask you the permission to install the drivers during set up) and try to connect your board.
You can also try to remove the SWD jumpers (connector CN2) on your board to detach the ST-Link from the built-in microcontroller part. Since the ST-Link part is independent it will still be detected by the STM32 ST-Link Utility (but you will have to put the jumpers back if you want to actually program your microcontroller).
Just ran into this. The problem boiled down to using nucleo boards and trying to interface with them using older versions of ST-LINK (ST's search for ST-Link's first hit led me to stsw-link0004, which was not installing the right drivers). Why they don't point you to the latest greatest first, who knows.
Whenever I tried to install drivers, I could only select USB Composite device as a compatible driver, despite repeatedly uninstalling/reinstalling stlink0004.
You need to install the newest st-link e.g. stsw-link0009 (or newer).
Uninstall device (device manager had it under USB Composite Device)
Uninstall ST-LINK
Disconnect nucleo.
Reboot.
Install ST-link (stsw-link0009)
The prompt should have you install 3+ drivers. Not just 2.
Plug in. Voila.

Emulator in AMD Processor is not working

I using AMD processor. I have installed everything related to eclipse perfectly. But I'm unable to start the emulator. program is hang and keep waiting for adb forever. The same issue in android studio also. Please give a solution.
I'm using a Android Studio on an HP x360, which is a nice little laptop but has a puny processor:). I spent ages getting the Intel Hax virtual machine thingy installed on my machine, as well as configuring bios (which I found AVAST blocked changes to, so had to uninstall it).
After probably hours this week (I'm new to Android) waiting for the emulator to do it's thing, start up, load program, and eat memory, I decided to plug in my phone (Moto-e).
This has made a massive improvement! Only takes a minute to compile and run now! You also have piece of mind that your app will run in the real world.
So as a newb to Android, I'd say don't bother with the emulator.... plug a real device in.
See here for setting up HAXM, if you have trouble installing, it may be antivirus etc blocking it....
Intel HAXM
All the best.
try these threads Virtualization threads

Visual Studio/WPConnect Unable to Connect to WP7 Device

For some reason, I'm no longer able to connect and deploy to my wp7 device. Zune does not show the phone as being connected, despite the fact that it is connected and the phone shows that it's being charged ... and the wpconnect tool gives the following error:
Failed to connect to the device.
Ensure that the device is completely
booted and is connected to the PC.
(0x80070103)
I rebooted the phone, and I've deployed to it before, so it's definitely developer unlocked. I verified that my computer has internet access. Any other troubleshooting thoughts?
Hey, I run into this all the time. Simply restart your phone and connect again. Make sure you plug in and unplug the phone several times, waiting at least a minute if it doesn't work.
In short, it's temperamental, Keep trying.
Make sure that you have switched off WiFi and Bluetooth on your phone.
I have found that I cannot deploy when Wifi and Bluetooth are switched on - even though Zune is syncing music and other content in the usual fashion. The error messages are frustratingly unhelpful!
As a short term workaround try using the Application Deployment utility to deploy the xap file.
I had the same issue. When I changed the Project properties target OS to 7.1 it worked.
I had the same issue. Only restoring to the previous OS version helped me.
Also I would that it usually happens when internet sharing is turned on.
I think I finally found the problem!
When I had this problem a few days ago, I had been charging my phone (Lumia 900) using a faulty charger which keeps on getting disconnected. And now that I've changed the cable and charger, it started working again!
I had the same problem with my previous phone as well (HTC Mozart), and I had a bad cable back then, but never made the connection (geddit?) between the problem and the cable...
My theory is that when the phone is running on bad power supply/not getting enough power, it sets a flag in the registry, which throws that error.
Also, bizarrely I just found that if you have internet sharing turned on then it won't let you connect.
Any of above mentioned did not work for me. I had many different error messages (included the 0x80070103)
What did is this:
Go to https://dev.windowsphone.com, uregister your phone.
Launch registration tool ("C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Tools\Phone Registration\PhoneReg.exe")
Unregister in tool from 2) too (if it is showing still as
registered).
Now disconnect phone and connect it again
Register phone in tool from 2)