platform manager and remote tool

[at siconix @com Derek Ou]

Hi, all,

I am trying a new 5.0 platform. I got the debug image downloaded and
running through KITL. But when I tried to conect using remote tools like
Remote Registry Editor, I could not get the connection going. I checked the
Debug output and found that CEMGRC.EXE is missing. So I added Platform
Manager and Build & Sysgen the Sysgen. I could see the cemgrc.exe in the
release directory now. But the system still complains:
307685 PID:e1717ea6 TID:e1717c22 0x81717c64: >>> Loading module CEMGRC.EXE
at address 0x0A010000-0x0A01F000
Loaded
'G:\WINCE500\PBWORKSPACES\AP2_IC_01\RELDIR\ARMPACK02_ARMV4I_DEBUG\CEMGRC.EXE
', no matching symbolic information found.
308438 PID:e1717ea6 TID:e1717c22 0x81717c64: >>> Loading module
cetlkitl.dll at address 0x01F50000-0x01F56000
Loaded
'G:\WINCE500\PBWORKSPACES\AP2_IC_01\RELDIR\ARMPACK02_ARMV4I_DEBUG\CETLKITL.D
LL', no matching symbolic information found.

Anybody knows why this happen and how to solve it?

Thanks,
Derek

[Henrik Viklund]

First of all, never ever "build and sysgen", only "sysgen" (if you
wonder why, do a search and you'll find loads of posts on this topic).
Secondly, the log snippet you provided dosn't really contain anything
unusual. The "no matching symbolic information found" message is just
to inform you that the debuggger can't found that this particualr
module dosn't contain the symbolic information needed for debugging,
but is otherwise harmless. It dosn't contain this information because
MS chose not to include that for this and lots of other modules.

Henrik Viklund
http://www.addlogic.se

[at siconix @com Derek Ou]

Thanks a lot for your reply. Now, I "sysgen" the system with "clean before
building" option. I still could not connect the remote tools. When I
tried, the platform loaders says "timestamp of module on device does not
match timestamp of local module" for both cemgr.exe and cetlkitl.dll. Is it
because I "build and sysgen" before?
Here is the debug log:
Loaded symbols for
'G:\WINCE500\PBWORKSPACES\AP2_IC_01\RELDIR\ARMPACK02_ARMV4I_DEBUG\VMINI.DLL'
45117 PID:617a392e TID:617a390a 0x817a36c8: Response='
47135 PID:617a392e TID:617a390a 0x817a36c8: Response='y'
47218 PID:6171770a TID:617176e6 0x81717750: >>> Loading module coredll.dll
at address 0x03F30000-0x03FF2000 (RW data at 0x01FFE000-0x01FFF5E5)
47230 PID:6171770a TID:617176e6 0x81717750: >>> Loading module CEMGRC.EXE

at address 0x0A010000-0x0A01F000
Loaded
'G:\WINCE500\PBWORKSPACES\AP2_IC_01\RELDIR\ARMPACK02_ARMV4I_DEBUG\CEMGRC.EXE

', timestamp of module on device does not match timestamp of local module.
60357 PID:6171770a TID:617176e6 0x81717750: >>> Loading module

cetlkitl.dll at address 0x01F50000-0x01F56000
Loaded
'G:\WINCE500\PBWORKSPACES\AP2_IC_01\RELDIR\ARMPACK02_ARMV4I_DEBUG\CETLKITL.D

LL', timestamp of module on device does not match timestamp of local module.
62243 PID:6171770a TID:617176e6 Opening KITL stream "platmanXport"...

Thanks,
Derek

"Henrik Viklund" <henrik....@gmail.com> wrote in message
news:1152861010.8...@35g2000cwc.googlegroups.com...

[Henrik Viklund]

That happens if your image conain modules that have a different
timestamp from the ones in you release directory. You may have rebuilt
a module but failed to update the image ("make runtime image"), or
you've managed to load an out of date image on the device.