I've been trying all the methods possibile to install it, with noobs (Windows 10 IoT wasn't even in the list), Windows dashboard and manually (converting the .ffu to .img). I also updated the firmware from raspbian but nothing changes, it stucks in the rainbow screen. I don't understand why, it has the same processor (BCM2837) as the pi 3 and it was released more than a year ago...
So can you guys help me? At least to understand why it doesn't work.
Thanks and sorry for my bad English.
Related
I am using Dfu-util to flash firmware onto an NXP device. It all works fine on my Windows 7 64 bit desktop, but on my Dell Inspiron 6400 laptop, running W10 32 bit(rather well, as it happens), the firmware download takes about ten times as long. Any pointers or suggestions would be much appreciated.
Answering here two years later because I found a possible solution, at least applicable in my case.
Connecting the board directly to the PC resulted in extremely slow DFU speed. However, adding a simple hub (4-port USB 2.0, unpowered) in between immediately made DFU download much faster.
It may be possible that the difference between the two computers was due to one using an internal hub or different USB topology that had the same effect.
As to why this helped, I have no clue, but it did and is perfectly reproducible in my case.
I just bought myself a new laptop(check link for details) and i was wondering how could i know if my laptop is compatible with running DDR5 ram, instead of DDR3. I have 2 slots and i really want to upgrade to DDR5. I have been searching on google for motherboard specs, but i am a little new to this stuff. So, can anyone please tell me if my laptop can run DDR5? Thanks a lot.
http://us.acer.com/ac/en/US/content/model/NX.MP4AA.007
There is no DDR5 available, maybe you are confusing with GDDR5 which is embedded on a discrete graphic card ?
The listed laptop is compatible with DDR3L (low voltage)
Since 3-4 Weeks I have Problems with Video-File Recording. Everytime I become an Index Fail after close / finish the Recorded File. But the Index is very important for me, because the recorded files should be used later for some Cut Processes. With this Index Failure it Cut me the wrong Part from the Video...
The Constalation is the Follow:
Logitech (B910HD) Webcam as Input Source => Xvid Codec as De/Encoder => Filewriter. All this done by a little, own developed Tool with the help of DirectShow (DirectShowLib-2005.dll).
I tried all logical debugging Steps... I has reinstalled Codecs / tried very lot of Codec Settings / tried other Computers and other Codecs (x264vfw) / reinstalled System (Windows 7 Pro x64 AND Windows XP Pro SP3) / changed WebCam (other B910HD and C920HD Pro) / ....
The more or less crazy thing is that its working very well before the 4 Weeks AND that is working fine on some other machines (same OS / exactly same Units and Hardware). So I though maybe its a Hardware failure from this Units (maybe HDD or Memory) but Tests of this Hardware was good too!
Thanks in advance for all possible solutions!
Comment:
Only VLC Media Player says the Index is defect. Windows Media Player tell me nothing and play the File....
I had a similar experience, seems like the B910 and also C920 webcams are not providing a constant framerate under all conditions. This leads to an incorrect video index. For me it helped to disable the auto-exposure feature. Please try and report if it helped to solve your problems.
#Moderator: please don't delete again, the answer is serious and could help the OP.
Does anyone here use USB 3.0, and can tell me why when I plugin my Xbox One Kinect 2.0 USB 3.0 cable into the computer, why it keeps sporadically disconnecting and reconnecting even though I downloaded all the windows updates, all the graphics card updates, all the firmware updates, etc...? And YES, I tried several different Ports. It's not broke. I got it new for Christmas.
After fighting with this for weeks, I finally found the root of my frequent disconnects. At some point, I had disabled the Xbox NUI Sensor Microphone Array to eliminate a feedback loop:
Control Panel > Hardware and Sound > Sound > Recording
After re-enabling the Kinect microphone, the Kinect stopped disconnecting.
To eliminate the feedback loop, I reduced the Kinect microphone's level setting to 0. You can get to the level setting from the Recording tab in the Sound dialog. Select the Xbox NUI Sensor Microphone Array and click the Properties button. From there, select the Levels tab.
I had a similar issue and I kept trying every thing for days, and finally the issue turned to be from the kinect AC adaptor... I tried it with the official windows sdk and developer toolkit, when I attempted one of the example codes the issue persists to appear but with a clear message asking to plug the power cord in, though the adaptor is brand new!!
I searched for some information a bout the AC adaptor and it seems that there is a problem with the adaptor, and most importantly the Kinect manual states that any unoriginal adaptors may cause the device to fail - also the manual says that original AC adaptor power output is 12V-1.1A while the one I have is rated 12V-1.08A (no big deal but who knows)
Kinect for Xbox 360 freezes and disconnects from USB after running Processing SimpleOpenNi depth image example
I had this problem,too. My system using pci-e usb 3 gen 2 and in windows 10 v1903 and kinect sdk 2 ... and all thing OK.. worked correctly .then after a date .reapetdly disconnect and restart.
at last ..I found this problem on my system...
I disabled sound using in windows setting.
I enabled this item in setting and all things became OK.
Read this, if you use an USB3.0 expansion card in a PCIe slot.
In my case I had connected the adaptor to an USB3.0 card (Transcent PDU3). After some hours research I discovered that the mainboard (MSI K9a2 Platinum) had Gen2 PCIe for the PCI-E x16 slots, but not for the PCI-E x1 I had plugged the USB card into. After switching to a PCI-E x16 slot, the constant disconnecting was over.
Don't confuse PCIe version and USB version here. For a Kinect 2.0 you need USB 3.0 and for USB 3.0 to run at super speed, you need PCIe 2.0 (or Gen2).
Testing PCIe version
You can use GPU-Z to determine which PCIe-Version the slot has where you got your graphics card plugged in -- let the mouse pointer hover over the bus interface field and wait for the tooltip and it will reveal the PCI-e version of your graphics card as well as the one of your mainboard. If you confirm it is Gen2 (or PCI 2.0) try to use that slot to put a confirmed-as-working-with-the-Kinect-2-USB3.0-card in it. (Having onboard graphics or a second PCI-Ex16 slot will definitely come in handy here).
Hope this helps.
I think it has to do with the USB 3.0 version, older machines won't run it. You need USB "3.1" and controllers usually manufactured after 2013 have it. It's often mislabelled as USB 3.0 in marketing material. USB 3.1 is also known as "SuperSpeed" or "SS10" which goes up to 10 Gbit/s. USB 3.0 "only" transports at 5 Gbit/s.
I have two five years old big rigs (Z68X-UD3H-B3, i7-3770K, and a 970a-D3, FX-8350) and it constantly disconnects. Both have 2011 board technology.
I also have two laptops, a VAIO and a Lenovo, which were built after 2013 (when they changed to USB 3.1) and it runs fine on both of those machines.
I too suspected the power supply at one point, nope, I thought I had a broken Kinect (bought a second, nope, now I own two.)
Other things to check:
- You might be able to use a USB 3.1 PCI card as long your MotherB will carry it.
- Remember to load the Kinect SDK 2.0 and also update the driver to the 2016 driver (SDK 2.0 comes with the 2014 driver).
- Remember USB 3.x is the "Blue" USB plug not the black.
This is not a case of requirements increasing beyond the capabilities of USB3.0!
Its also not a problem with Win10 1809 or KinectSDK 1409.
It will disconnect if your apps have no access to either microphone or camera.
You can check or reset your settings the easiest with a free program called OOSU10.
Runs fine on my 2012 laptop.
If your problem is that the Kinect Configuration Verifier does not start at all, then this is caused by having disabled the printer spooler service.
I used until yesterday afternoon a Kinect for XBOX 360 on my computer, a MacBook Pro 15" Late 2011, whose specifications are available here. I use Windows 7 (natively installed, without using virtual machines). The version of the SDK I had installed was 1.0.
All of a sudden, from today the Kinect no longer worked. Initially I thought it was some error in my code, but I noticed that the program remained stuck at the beginning, when I called the method KinectSensor.Start().
I started looking for information on the internet. I read about a solution obtained by reinstalling the drivers. It did not work, and then I tried to install version 1.6 of the SDK. Unfortunately, even that did not work.
I've seen at this stage, there might be compatibility issues with certain USB host controllers, such as the Intel 5 Series/3400 Series Chipset USB host controller. In my case, however, there should be no problems (because there were not ever been up to yesterday):
To check if the problem was really due to the sensor, and not to my application, I run one of the test applications provided with the SDK, called Kinect Explorer. However, I encountered the same problem with this test application. After waiting about one minute, when the Kinect Explorer starts I cannot see neither the color stream, nor the depth stream, nor information about skeleton. The only thing I can do is move the Kinect up and down, changing the angle of the neck. Even the microphone array seems to work properly.
I read two interesting posts about this kind of problem: this and this, which have not been answered.
In the first of these two links, the user who reports the problem says that the hardware has been compromised. I thought the same thing myself until I started again Kinect Explore, initially with the sensor unplugged. Once started this program, I plug-in the cable, and I noticed that Kinect Explorer has marked the Kinect sensor as Connected. After a short initialization phase, I again see the color stream, while the depth stream showed an image of uniform color (green-gray):
This situation lasted a few seconds, after which the image is locked and the question came up. Also, sometimes the FPS value drops from 30 to 29.
I am able to reproduce this latter situation only after keeping the Kinect unplugged for a while (10 minutes are sufficient).
How can I solve this strange and terrible problem? Is it possible to restore the Kinect sensor, and make it works again? Or do I have to conclude that the sensor is irretrievably broken?