When you're creating your WinCE image, did you select:

Core OS->Windows CE devices->Applications - End User->ActiveSync??

If not, that might do the trick methinks..

Quote:
When you're creating your WinCE image, did you select:

Core OS->Windows CE devices->Applications - End User->ActiveSync??

If not, that might do the trick methinks..

Oh yes, I have had that in the build from the start. What got it working for me was when I read this in the readme.txt for the USBF driver:




I was missing the Serial driver.

-Kevin

Ahh OK. Good thing you figured it out and got it working..

So,... why is this not a dependency requirement for Active Sync? It should be automatically included in the profile when Active Sync is. (Unless Active Sync can be connected other ways.)

I had the same problem when using the 404 Dev image. When I used the LPD NK.BIN it worked fine, yet when I built the image from the included PB image build it would not work. Why is this left out of the version supplied for us to build?

I tried building an image to test Active Sync, and I just included the display, touch and the lpd_lh7a40x_usbf_a40x_50_1_3_0 driver, and included:
- Standard Shell
- Active Sync (sub features optional)
- Network User Interface
- Dial Up Networking (all sub features)
- Telephony API (all sub features)

I get nothing at all on my PC or on the screen of the device.

So I changed my Active Sync design, and included the v1.5.0 of the USBF driver instead of the 1.3.0 version. Per the readme I included:

To enable USB ActiveSync functionality the following must be enabled:
* Catalog Item(s):
".\Shell and User Interface\User Interface\Network User Interface"
".\Applications - End User\ActiveSync"
".\Device Drivers\USB Function\USB Function Clients\Serial"

I still get nothing on my PC, but now I get a message box on the device:

Quote:
Connection Not Valid
Cannot start communications with the desktop computer. Unable to open the connection '`USB'. This connection is not valid or does not exist.

Please open Communications in the Control Panel on your device, specify a new connection to use for PC Connection, and reconnect.

Also, in my Tera Term window i have the message:

Quote:
Posting WM_NETCONNECT(FALSE) message, ErrorCode = 623(0x26F)
AUTORAS:: Dialer notifies: [1] [Dialer Start]
AUTORAS:: Dialer notifies: [2] [Dialer Terminate]
CPL: Failed to load '\Windows\system.cpl'
CTLPNL: cmdline=\Windows\cplmain.cpl,0
--->>>CTLPNL: CPL='\Windows\cplmain.cpl' icon=0 tab=0

By changing the entry in lpd_lh7a40x_usbf_a40x_50_1_5_0.reg from:

Quote:
"Cnct"="`USB"

to:

Quote:
"Cnct"="`Desktop @ 19200`"

the CE device at least recognizes the connection and attempts to connect. (Yes, the Grave Accent marks are required.) My ActiveSync icon turns green and rotates for about a minute before it gives up. This makes me think that at least the USB connection is being made. But I still can't get the connection.

On my Tera Term, I now get:

Quote:
AUTORAS:: Dialer notifies: [1] [Dialer Start]
RASCS_Disconnected: Ecode=619
Posting WM_NETCONNECT(FALSE) message, ErrorCode = 619(0x26B)
AUTORAS:: Dialer notifies: [2] [Dialer Terminate]

The LPD NK.BIN works fine and connects on my PC so I know the problem isn't my PC.

I just noticed in the download pages that lpd_lh7a40x_usbf_a40x_50_1_5_0 is no longer available and that lpd_lh7a40x_usbf_a40x_50_1_3_0 is listed as current. Was there a problem with the newer driver and Active Sync?

When I put 50_1_3_0 back in, I get absolutely nothing when I plug in the USB cable, so I do not think that makes sense.

I don't know if it's related, but I always get this debug output when I open the Control Panel on the device to look at the connection:

2560198 PID:e5ba5e6e TID:e5ba5cd6 CPL: Failed to load '\Windows\system.cpl'

Can you make sure you have the Telephony API and Dial Up Networking (all sub-options) included in your catalog?

Bruce,
Did you install the USBF Workstation drivers on your PC? These are necessary for the A404.

I have just built a new Internet Appliance image from the BSP drivers available on the web and I can successfully connect over ActiveSync with my PC. I can explore my device.

Have you compared your Platform Builder workspace to the workspace provided in the sample bin image zip file?

Did you check the readme for the USB Function driver? It include all the necessary components that need to be added for ActiveSync to work.

Quote:
Can you make sure you have the Telephony API and Dial Up Networking (all sub-options) included in your catalog?

Yes, I do have those options with all sub-options included in my build. They are part of the LPD Dev image.

Quote:
Did you install the USBF Workstation drivers on your PC? These are necessary for the A404.

I did install the USBF Workstation drivers on my PC. As I mentioned earlier, the Active Sync works fine with the image supplied by Logic, so I know my PC is configured correctly.

Quote:
Have you compared your Platform Builder workspace to the workspace provided in the sample bin image zip file?

I copied the workspace from the LH7A404_DEV_IMAGE_For_All_Other_PNs.zip, so it pretty much has to be the same. I also compared the SysgenSettings.out files from the .zip file and from my workspace after building, and they are identical. The NK.BIN files are not identical. If they were, I would expect my image to work. Since the Logic image was built at a particular point in time, and I keep my Platform Builder updated from Microsoft, it is likely that there have been changes in some modules. Is it possible to fingure out which versions of updates have been installed in Logic's Platform Builder?

Quote:
Did you check the readme for the USB Function driver? It include all the necessary components that need to be added for ActiveSync to work.

From the readme:

Quote:
To use this as an Activesync transport, ensure that the following
components are installed in workspace using the Standard Shell:
- Active Sync (sub features optional)
- Network User Interface
- Dial Up Networking (all sub features)
- Telephony API (all sub features)

I have all of these installed, including all sub features of each.

I realized that Platform Builder, like Windows, might accumulate cruft over time, and I have had my system installed for a while. I removed Platform Builder completely, removed all references to it from the Registry, and started over, adding only the 2005 and 2006 rollup updates.

Now it connects with USB and Active Sync. I can explore the device.

I also found that the remote tools in VS2005 require my image to have C++ exception handling included (SYSGEN_CPP_EH_AND_RTTI), or it won't connect. I got an error message on the serial debug something like "%1 is not a valid device".

The USBF driver I'm using is the lpd_lh7a40x_usbf_a40x_50_1_3_0. I haven't tried the lpd_lh7a40x_usbf_a40x_50_1_5_0 since reinstallation, but I see it is no longer on the downloads site, so perhaps there was a problem with it.