Hi Everyone
I was wandering, it is possible to use My WM device to directly run the compiled code of my smart device project on the fly?
Like the default emulators, but on my real device
Yes, you can deploy and debug over activesync. In the "target device" drop-down change it from one that's name contains "emulator" to one without. Then it should connect over activesync.
Related
When the device won't boot, is it possible to connect and access the device's ROM through the PC?
For example, I enabled KITL in "USB" and "Active" mode, then I put the device in the cradle, the PC recognized it as "HTC USB SYNC" and then ActiveSync started but after about a minute gave and error saying it was unable to connect saying the device isn't a SmartPhone or PocketPC.
Is there some sort of MSDN developer software or something I need to connect through the USB in KITL mode since ActiveSync won't do it?
Any ideas????
Thanks!
flash it with a rom
Maybe I should have been more clear.
I already have a ROM flashed onto the device, however the ROM will not boot. Using the KITL layer through the USB, I would like to access the ROM so that I can change some files in it, a few dll's and a bin file in the Windows directory to be specific. I am presuming there is an application I need to install on my PC to acomplish this in conjunction with the KITL mode, however I am currently at a loss for knowing what that application is.
FYI, this is a WM5 so yes it does have the newer KITL version that in fact supports USB sync for debugging according to MS and the KITL menu on my device. However I've read everything on MSDN and googled and have turned up nothing as far as what app I need.
Does anybody know?
Thanks!
Hi
I'm trying to debug the memwatcher SDK tools sample today item using VS2005. This used to work - i don't know what I did to break it...
First I get a message "Program to Debug A non-executable project cannot be started directly. Please set a command to use to start debugging this
project. Do you wish to continue?'
If I click yes I get a message "unable to start program
'%CSIDL_PROGRAM_FILES%\memwatcher\memwatcher.dll'.
I've tried re-installing VS2005 and the SDK with no luck.Other SDK samples that compile to exes debug fine. If I load the dll and registry items by and the sample works as expected (not debugging) - it also runs on a real device.
Can anyone suggest what to do?
Thanks
Mark
Hi,
I would like to let the user run a Win32 installer that will install the WM5 application to a device, if it is connected, otherwise it will install it to the device when it is next connected.
Is this possible?
Can I place the CAB and ini files in a certain directory and have them automatically installed to the device when it is next connected???
Thanks!
Nevermind... Just added some logic to my MSI to prompt the user to connect their device if its not connected and loop over that until a connected device is found.
Hi there,
I'm looking for some information about what i would need to do to get a USB device recognised on my x7501. I'm looking to connect a USB-to-UART bridge chip (FT232RL or something) to the device so I can essentially have a serial/COM port on my phone, which i can use for data logging.
I was wondering if anyone's had experience with anything like this so i could find out:
A) what devices are already supported in WM6, as the bridge chips can mimic a virtual com port via built in windows drivers but im not sure if this driver is in windows mobile
B) what i would need to do to setup for dev for writing WM software and the driver if necessary (i have visual studio, i think there is a WM emulator but im not sure totally?)
C) any other questions you think are relevant to my goal
thanks in advance,
sebastian
Hi,
I have a bespoke usb device that "in theory" should report as a HID keyboard.
The device works correctly on vista/mac. But I cannot get it to work on the ameo with the R6.1 MiChy ROM (or earlier versions).
Looking in the registry editor (on the devices tab) the usbhid.dll and kbdhid.dll is loaded, but I am unable to type anything on the keyboard.
I have asked in the windows mobile forums on msdn for ways of debugging, they recommended using the wince platform builder. It's a great recomendation, but also v.expensive.
I'm pretty certain it's my dodgy firmware that I have written, but it's proving v.difficult to debug.
-thanks for the help