I am working on vxworks 5.5.1 and Tornado 2.2.1 porting a BSP for an Intel atom board.
I have set the options (memory, console (serial) and other options) and produced a bootrom and vxworks image.
my development host is a 32-bit XP and I created a boot floppy image using mkboot a: bootrom
Then I used HDD raw copy to copy the image to a USB.
When I boot the atom board with the USB, all I see is the display "1.6+++++++++++++++++++++++++++++++++++++++++++++++++++++++".
Since I compiled serial code into the bootrom (and there is a Rs-232 on the board), I was expecting to see some output on the Tornado COM1 console running in my environment.
It does not look like the bootrom is talking to serial port on the board at all.
Does anyone have any clues on where to look?
Thanks,
RK
I tried to deploy my Windows phone 10 package to device.
I created package from VS2015 (.appx)
Switched on dev mode on mobile device (with win phone 10)
Plugged mobile device to PC with USB
Ran command WinAppDeployCmd devices 10
And still WinAppDeployCmd is unable to find any device.
How should I setup WinAppDeployCmd to make it able to find my mobile device?
Thank you.
I found solution.
[PC]create package in VS2015 (.appx)
[Mobile]Go to Settings=>Update and Security=>For developers=>switch on Developer mode
[Mobile]Switch on Wi-Fi and connect to network (the same network as PC)
[Mobile]Go to Settings=>Network & wireless=>Wi-Fi=>press network name you connected to=>find IP address
[Mobile]Go to Settings=>Update and Security=>For developers=>switch on Device discovery=>press Pair=>remember code
[PC]run command WinAppDeployCmd install -file "path to .appx file" -ip [IP address from 4th step] -pin [code from 5th step]
It helps deploy package to device
I'm now trying to set up my kinect version 2
I installed Microsoft sdk and usb extension board (Renseas 720202)
Question is, Kinect can be detected before driver of usb board install.
In Kinect verifier program, usb controller are not compatible but can get
color image with low fps.
ahttp://ppt.cc/XvKOg (Sorry I can't post more than two links. Plz remove 'a' and see the pic)
http://ppt.cc/kv38M
After install driver of usb board, I get nothing...
ahttp://ppt.cc/hbWAE
http://ppt.cc/Cw29u
I search that intel and Renaseas chips are compatible with Kinect v2.
What can I do? Thanks
update
In the end, I change computer which use intel chipset on mother board to solve the problem.
After getting my app to work in the emulator, I now want to test it on my Sony Xperia Arc Android phone. I follow the instructions from google here http://developer.android.com/sdk/win-usb.html but can't get their USB driver to load.
When I plug the phone into the computer via the supplied USB data cable, Windows 7 installs it's own driver and doesn't give me a chance to point to the google driver located here: C:\Program Files\Android\android-sdk\extras\google\usb_driver\android_winusb.inf.
When I go to the device manager and right-click on the Device Manage and try to Update Driver Software to point to the Google driver, it says it already has the best one and won't change it! (even though it doesn't work, ie. no drive label appears for the phone plus the device manager shows an ! for it)
I've spent many hours reading dozens of posts with similar problems but no solutions work for me. Any ideas?
Download the drivers from here:
http://developer.sonymobile.com/cws/devworld/downloads/download/sonyericssonxperiaarcxperianeoxperiaplaydrivers
This programming guide implies that this is possible, so I figure what the heck.
Right now, though, it doesn't work.
Host OS is Vista 64-bit, VMWare Workstation 6.5.3 is running Windows 7 Enterprise 32-bit.
Installed Software on the VM:
Visual C# 2010 Express
Microsoft Server Speech Platform Runtime
Microsoft Server Speech Recognition Language - Kinect
Microsoft Speech Platform SDK
Kinect for Windows SDK Beta
I plug in the Kinect, the device is recognized by the VM, then I run the Sample Shape Game and it doesn't recognize the device. It says "Plug in the Kinect and try again" which turns out to be error 0x80080014, which leads to
http://social.msdn.microsoft.com/Forums/en-US/kinectsdknuiapi/thread/4da8c75e-9aad-4dc3-bd83-d77ab4cd2f82/
which gives me two things to look at:
is it plugged in with the special cable? yes
are all 4 entries in the Device Manager? no
In the Device Manager, I see a "Microsoft Kinect" group containing Microsoft Kinect Audio Control, Microsoft Kinect Camera and Microsoft Kinect Device, but there is nothing under "Sound, video and game controllers" other than VMware VMaudio. "Kinect USB Audio" should be there.
I'm guessing that there is some further twiddling I have to do with the VMWare USB / hardware options (whatever that tray with the USB / CD / HD / floppy etc icons is called) or some deft combination of rebooting and (un)plugging, but I'm almost out of enthusiasm.
Any ideas? TIA
EDIT: I realized that I had some lingering drivers on my host (Vista) system from OpenKinect. After removing them, I can no longer see the Kinect at all in the VM. Hmm.
There is this on read.me
Virtual machines: You must run applications built with the Kinect for Windows SDK Beta in a native Windows environment. Kinect for Windows applications cannot run in a virtual machine, because the Microsoft Kinect drivers and this SDK Beta must be installed on the computer where the application is running.
just to share that (not really understood how) VM Workstation 8 running in a host win 7 x64 with guest OS Ubuntu 10.04 sucessfully detected and installed Kinect drivers.
I was able to test it with libfreenect (OpenKinect Project) http://openkinect.org/wiki/Getting_Started#Manual_Build_on_Linux
best regards,
I'm late to the party, but we've been running and developing for the Kinect with Windows 7 running under VMWare under Mac OS X Mountain Lion.
I'm not a Computer Scientist, but I thought Turing showed that a universal Touring Machine was basically the same as physical hardware. I've had Distributed COM+ running on 3 or 4 VM's on the same physical hardware, but somehow the Kinect device is different? I don't buy that at all.
The most recent version of Microsoft Kinect for Windows (v1.6, possibly slightly earlier versions) in combination with the "Kinect for Windows" hardware does work inside a virtual machine. I run this setup on a MacBook Pro, Parallels 7 and Windows 7.
Note that a Kinect for Xbox does not work inside a virtual machine.
This page from Microsoft says that the "Kinect for Windows" device should work in a VM, but that the "Kinect for XBOX" does NOT work.
First of all you just need two Things to be installed:
libfreenect
libusb
after that you should set three flags to 0x02 at the line
typedef enum {FREENECT_DEVICE_MOTOR = 0x02,FREENECT_DEVICE_CAMERA = 0x02,FREENECT_DEVICE_AUDIO = 0x02,} freenect_device_flags;
Inside the headerfile located at /usr/local/include/libfreenect libfreenect.h but you will lose the ability to control the movement and the the microphone usage will be disabled so don't even try to access them or your device might get damaged after that you should also set
#define PKTS_PER_XFER 32
#define NUM_XFERS 6
inside your libfreenect/src/usb_libusb10.h file at the linux Line
After that rebuild your libfreenect by
mkdir build
cd build cmake ..
make make install.
Than Restart your virtual System and plug and connect only the Kinect Camera Device and no other Kinect device during start of the VM. When System is up you could test your device is properly working by switching to your previously created libfreenect build directory and go to bin there you run ./freenect-camtest you should get no or only a small number of package losses if a lot of losses occur try restart your vm with the camera device pluged in and already connected to your vm. You might need to active disconnect and connect the Webcam from the VM during startup to receive images this should be done during first seconds of VM Boottime!
Works with Ubuntu 14.04 and Workstation 10 and 11 and 11.1
HOST OS Windows 7 and Kinect SDK installed and Kinectdevice for Windows
Also it seems to be quite unstable you often have to restart your virtual system if you can't receive images from your Kinect. But if you once received images don't unplug device or you won't get data until you reboot virtual system with Kinect Camera connected to it.
=> This actually solved the problem otherwise to much frames get lost and its not possible to display proper image!