Troubleshooting a Connection to a Target Device That Uses Platform Manager
Other versions of this page are also available for the following:
8/27/2008
When you try to establish a connection to a target device from a remote tool by using Platform Manager, you might encounter issues, even if Platform Builder is successfully connected to the target device through your chosen download service.
The following table shows prerequisites for successfully connecting to a target device from the remote tools.
Prerequisite | Description |
---|---|
The time stamp for shell.exe on the device must match the time stamp for the local shell.exe module. |
If you receive an error message that indicates that the time stamps do not match, remove the time-stamps setting for debug messages while the modules are being loaded onto the target device as follows.
|
To connect to the remote tools the first time in Platform Builder, you must set the path to the correct version of PSPubSubCE.DLL for the microprocessor family of the target device. |
Do the following:
|
When you connect to a target device that uses an ARM microprocessor and you use ActiveSync as the transport, you must create a separate folder named ARMV4 that has identical contents as the ARMV4I folder. This enables Platform Manager to locate the file required to establish a connection to an ARM-based target device. |
Do the following:
The next time that Platform Manager tries to establish a connection by using a file in this directory, it will locate the armV4 folder and download the correct file to your target device. |
See Also
Tasks
Configuring the Connection to a Target Device Using Platform Manager