Related
I'm working with an XR Unity project (2019.4.26f1) and I'm trying to deploy it on the HoloLens 2. I've managed to build the project and to run it in the HL from Visual Studio by cable but I need to be able to see the app in the HL when I enter on the Play Mode in Unity.
I've followed some tutorials like this one and I can do every step but when I get to the step of writing the IP in the Windows Mixed Reality window, a problem appears. When I hit play to go on Play mode, the IP disappears, and I receive an error because the Remote Machine Address is not set. Why is this happening?
I have something like this, with the IP of the HoloLens in the field, the HL are ON and with the HoloRemoting app running. I can access this IP by browser and see that the status is "Connected" and see Live footage of the Lens camera.
However, when I hit "Play", the IP disappears and I get this error.
Atempting to initiate remoting connection with no valid machine name
set. UnityEditor.EditorApplication:Internal_PlayModeStateChanged
(UnityEditor.PlayModeStateChange)
Due to potential compatibility issues, it is highly recommended to upgrade your Unity version to 2020.3.31f1 with the latest Mixed Reality OpenXR plugin. You may refer to the document on Choosing a Unity version and XR plugin - Mixed Reality | Microsoft Docs.
I've been working in a Unity app with Hololens emulator in Visual Studio 2017 in Windows Pro, and it was working great until last night where I started to get the following issue every time that I try to deploy my application into the Hololens emulator:
Error DEP6957 : Failed to connect to device '[device_ip]' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings.
I've tried to do the following things without success:
Clean/rebuild solution
Checked 'uninstall/install' checkbox in the UWP project settings
Deleted Hololens virtual machine
Uncheck/check Hyper-v feature (and restart PC after each try)
Restarted computer
No luck. Sometimes, I am able to make it work, but after 30 seconds to 1 minute, the hololens emulator gets frozen and then it closes itself; again, this was working fine until last night, and I have not installed anything different, unless an automatic windows update did something. This happens with all the applications, and they run just fine in the Unity player.
I would appreciate your help on this, I just don't think the only solution is to uninstall/install Visual studio and all its components, it makes no sense, since everything was ok.
Thank you.
UPDATE
I've just noticed that if I connect the laptop to the internet by using an ethernet cable, it works, it only fails in WIFI, have you seen that before? I also have another UWP that I deploy remotely to a raspberry and it also works only with ethernet, but both of them were used to work in wifi? any idea?
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.
I am following the instructions given HERE
I can install it to the vmware hard disk fine and get it running, but then it says to open a terminal and execute su
The terminal says that it cannot make me a root and nothing else
I am not able to go any further after this and so the internet isn't working in the virtual machine
Moreover, the internet works if I was just using the live CD version, without me having to do anything else
How do I get root permissions in android x86 on VMware?
--- EDIT---
After playing around some more with this I have noticed another problem: when I try to start the virtual machine, most of the times it reaches the Chrome coloured android startup logo, the logo animates continuously but the screen is sort of stuck at that phase. And if I loose focus to the vmware window and come back, I see that the window is blank and I am not sure if the virtual machine is even further loading or not. How do I properly get Android x86 to work on vmware (with full install on it's virtual hard disk and not just the live CD version? Should I try other virtual machines? I have not been able to get others such as qemu and bochs to work in the past and see that vmware is the easiest and most stable option, so I would like to run this in vmware if possible.
check here www.bitdirect.nl/?p=128
I followed this with a few little tweaks here and there and it worked perfectly.
only downside is transferring data outside of the android os is a pain.
I bought a new Nexus 7, and Eclipse cannot see it. It is appearing in Device Manager as Android Device ---> Android Composite ADB Interface. There is no other devices category, and I have updated the list.
My SDK Manager has everything except for the obsolete installed and updated. I have also tried reinstalling Eclipse all together.
I have updated the driver via \adt-bundle-windows-x86_64-20130514\sdk\extras\google\usb_driver and it says the best one is already installed. USB-debugging is enabled on the Nexus 7. I am all out of ideas. Please help!
Uninstall and Reinstall Nexus 7
Update:
Plan B:
OK you say it didnt work.... this is kind of a long shot but saved my bacon a lot when I was working as a technician in my past life and had to find unknown device drivers.
Right click your Nexus in device manager , select properties and go to this page
The example shows my radeon card but if you google this hardware ID( the top one in your pc), and check a couple of random sites , you are likely to find it. This method is used for finding unknown drivers, and you may as well give it a shot as you have exhausted most options.
Plan C:
Trying the same nexus on a different windows7 computer to see if it installs . If it does, then you can try to extract it from that computer ( e.g. using driverguide software) and force windows on your main pc to use that.
Plan D:
run sysprep.exe on your PC by typing it in RUN and double clicking the file and clicking Generealize.This prepares your pc for imaging and removes all drivers. Note that you'll have to activate windows again after this.
Plan E:
And lastly, the call center answer , use system restore, although the damned thing fails 90% of the time and install again after a reboot. or a whole scary reinstall of windows :(
//Ignore below now as it didn't work for you
Download this driver http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
You can also check this question for a solution for Nexus and an alternative driver. I had the same problem , although not with a Nexus, but a sony Xperia, and I had to download a generic driver to get it going. The above samsung site has the driver, but the model is called SCH-I515. You should be able to fix it without the generic driver
ADB dosn't recognize my Galaxy Nexus - Win7