Hi All,
Going to keep this fairly brief for start. Typically I like to keep a new Activesync with the CE 5.0 devices and debug stuff with it on my main machine and I haven't figured out how to make two different versions of activesync run at the same time to target the older devices. Previously I just debug code with many logfile writes, but now that I got a different machine I can dedicate to older HW development I figured I may as use remote debugging. I did not install CE services, but do have ActiveSync 3.8, which can connect to all devices it is supposed to from CE 2.0 to 3.0. Hit some snags across the board in getting remote debugging working but the below info solved it for a couple platforms. Trying to get this workign with the MC 16.
This info solved it for me for CE 2.11 and CE 3.0
(HPC2K
) only:
http://groups.google.com/group/microsoft.public.win32.programmer.wi...
* I renamed Programme to Program Files in the above task
Noticing the registry already had these same exact keys up a couple levels and across in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Tools\Platform Manager\{2A4F783A-014E-11D2-BBA0-00A0C9C9CCEE}\{919E8310-4C05-11D2-BD39-0060089A6894}\CEMON.EXE
I saw a more comprehensive list of CEMON targets. I decided to export the whole thing and then update the target registry hive path to
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows CE Tools\Platform Manager\{F384D888-F9AA-11D1-BB9E-00A0C9C9CCEE}\{6D5C6210-E14B-11D2-B72A-0000F8026CEE}\{2A4F783A-014E-11D2-BBA0-00A0C9C9CCEE}\{919E8310-4C05-11D2-BD39-0060089A6894}]
I did this to see if it was as simple as that, since it seemed to be as simple as that for CE 2.11 and 3.0. No luck for CE 2.0, but CE 2.11 and CE3.0 continued to operate with remote debugging. That made me what is called stuck...
I noticed the hex values seem to indicate:
unknown 2
CPU ID, 1 MIPS, 4 SH3, 5 ARM, 3 PPC, 8 THUMB,
CPU SubId: usually 0, but 13 27 for SH3, 15 27 SH4, cc 10 MIPSFP,
Unknown 00s
Unknown 10
Platform:: 02 CE 2, 2.11, 2.12 and 03 CE 300 and subplatform for the differentiation between 2.0 2.01, 2.1, 2.11, and etc.
Unknown 01
Not that it matters, but it was a pattern I observed. Copying the keys to the correct package places helped a lot for 2.1x and 3.x, but failed me for 2.0. Running REGMON to see what registry keys are inspected by EVC3.0 when I press build, which launches the platform manager ot copy files creates a blue screen. I can see them dig through the Windows CE Tools hive, but then it bluescreens and closes Platform Manager, so I can't get too far there.
So the main questions:
Is anyone able to use EVC to target Windows CE 2.0 devices? Confirmation will keep me on the chase cuz then I will know it is possible.
If so, can you use RegMon to show me a log of the inspected registry keys when the platform manager launches after pressing build on a simple hello world project? I may be able to add/move/copy/modify some keys to get me in business!
Thank you for making it this far into the dry technical message!