Re: Activesync CE 6.0 RS232

When we manually execute repllog on the target with debugging disabled, we
are able to see "CLIENT" come across using HyperTerm on the dev. system;
however, it still does not connect. The repllog dialog on the target goes
away almost immediately and we only see one "CLIENT" string come across the
wire.

We are enabling and disabling debugging information by modifying the
loadcepc line in the autoexec.bat file on the boot floppy.

Using /c:0
- no debugging information
- repllog dialog closes immediately without error message
- "CLIENT" is seen on HyperTerm (cable connected to target COM1)

Using /c:1
- debugging information from target COM1
- debugging info shows lineMakeCall fails with error 8000004b
(LINEERR_RESOURCEUNAVAIL) opening "COM1".
- nothing comes out of the target COM2

Using /c:2
- debugging information from target COM2
- debugging info shows lineMakeCall fails with error 8000004b
(LINEERR_RESOURCEUNAVAIL) opening "COM1".
- nothing comes out of the target's COM1

Platform builder has all the available patches installed through March.

Again, any help or suggestions would be appreciated. Thanks!

"Valter Minute" wrote:

=?Utf-8?B?YnViYmE=?= <bubba@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:2B25C2DA-9841-4678-90D2-F1179D1AD651@xxxxxxxxxxxxx:

We are targeting a CEPC (VIACN700 chipset) and are having trouble
getting Activesync up and running. The device has repllog;
however, when I try to initiate an ActiveSync connection from the
dev. sytem, it does not connect.

We are loading the nk.bin image over Ethernet and have proven that
the COM1 and COM2 hardware work properly (using an XP image).

We have disabled the debug messages from using COM1 (on the
device); however, Activesync still does not connect.

Any suggestions or hints would be appreciated.

Repllog get executed on the device when you connect the cable?
If you open an hyperterminal session on the PC using 19200 8N1 you
see the string CLIENT sent by the device?
Even if you disabled serial debug on COM1 it will be recognized as
COM2 in CE and the "dos" COM2 will be COM1 in CE (if you used a
CEPC-based BSP).

--
Valter Minute
(the reply address of this message is invalid)
(l'indirizzo di reply di questo messaggio non è valido)

.

Relevant Pages

  • Re: WinDBG, doesnt support kernel debugging?
    ... I would not want to debug my drivers on the same machine I use ... serial or 1394 to a target to protect my development environment. ... For what I have to pay for softice, I can purchase a cheap dual processor ... > I meant you can't do KM debugging on a single machine. ...
    (microsoft.public.development.device.drivers)
  • Re: WinDBG, doesnt support kernel debugging?
    ... I would not want to debug my drivers on the same machine I use ... serial or 1394 to a target to protect my development environment. ... For what I have to pay for softice, I can purchase a cheap dual processor ... > I meant you can't do KM debugging on a single machine. ...
    (microsoft.public.win32.programmer.kernel)
  • RE: reconnecting a CEPC or Geode to platform builder without re-bootin
    ... If you are not making changes to your platform, and are just debugging ... the target, it will get pulled down via kitl from the PB release directory on ... When I rediscovered that ActiveSync isn't ...
    (microsoft.public.windowsce.platbuilder)
  • Re: [Lit.] Buffer overruns
    ... >>safety checks for debugging and disabling them for production is like ...
    (sci.crypt)
  • Re: Microsoft Debugger
    ... If I click on Yes I get another screen "Just-In-Time Debugging". ... New instance of Microsoft script editor. ... Then it gives me the option to: "Choose the program that you want to debug". ... How can I correct this error other than disabling Script Debugging? ...
    (microsoft.public.windowsxp.basics)