Re: Remote Tools not connecting
- From: "Yannick Chamming's [eMVP]" <ychammings_nospam@xxxxxxxxxx>
- Date: Wed, 10 Aug 2005 11:07:57 +0200
Can you check if platform manager is configured to use CESH + KITL
--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADENEO (ADESET)
Windows Embedded Manager
ychammings AT adeset DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------
"Benoît Bousquet" <bbousquet@xxxxxxxxxxxxxxxx> a écrit dans le message de
news: %23h69iqRnFHA.1088@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks for the reply, but that option was already enabled. Here's a list
> of my platform options (Platform/Settings/Build Options) for the debug
> build:
>
> - Enable CE Target Control Support
> - Enable Eboot Space in Memory
> - Enable Full Kernel Mode
> - Enable Images Larger than 32MB
> - Enable Kernel Debugger
> - Enable KITL
>
> As a side note, I have tried using the emulator instead of a target PC and
> it yields the same result (remote tools not working, although everything
> seems to). When I was messing around with the target PC I also realized
> that my crossover cable was useless - I just connected the CE machine to
> the main company network and it worked fine for downloading/debugging
> (still no remote tools however).
>
> -BB
>
> "Dean Ramsier" <ramsiernospam@xxxxxxxxxx> wrote in message
> news:uMQa8aRnFHA.3288@xxxxxxxxxxxxxxxxxxxxxxx
>> You need CE target control support in order to allow the remote tools to
>> work. Should be an option in Platform->Settings, or from the catalog at
>> Core Os->Kernel Features. Ends up resolving to SYSGEN_SHELL, and pulling
>> in
>> the relfsd component.
>>
>> --
>> Dean Ramsier - eMVP
>>
>>
>> "Benoît Bousquet" <bbousquet@xxxxxxxxxxxxxxxx> wrote in message
>> news:OXL7wfPnFHA.420@xxxxxxxxxxxxxxxxxxxxxxx
>>> Greetings.
>>>
>>> Using PB 4.2. Current setup:
>>> - development PC with 2 network cards (one to main company network, the
>>> other connected to target PC with a crossover cable, using address
>>> 192.168.10.1)
>>> - target PC with 1 network card (192.168.10.2 set on the boot floppy,
>>> connected to development PC with crossover cable)
>>>
>>> I built a pretty basic CEPC/Mobile Handheld image, have configured the
>>> PB
>>> remote connection as Ethernet for both Download and Kernel Transport,
>>> and
>> my
>>> target PC downloads and boots the image successfully - I also get a ton
>>> of
>>> traces, as it should be.
>>>
>>> So far, all is good. However, I can't seem to be able to connect to the
>>> target PC with ANY of the remote tools. I'm somewhat confused as to the
>>> steps required. I tried (I believe) all the combinations in the remote
>>> tools' connection panels, to no avail.
>>>
>>> I have a NULL cable (serial) lying around if it can actually help.
>>>
>>> --
>>> -----
>>> Benoît Bousquet
>>> (e-mail address is invalid)
>>>
>>>
>>
>>
>
>
.
- References:
- Remote Tools not connecting
- From: Benoît Bousquet
- Re: Remote Tools not connecting
- From: Dean Ramsier
- Re: Remote Tools not connecting
- From: Benoît Bousquet
- Remote Tools not connecting
- Prev by Date: Re: How to change interrupt priority
- Next by Date: Re: "Core OS Version"/"winCE Version" are they different?
- Previous by thread: Re: Remote Tools not connecting
- Next by thread: tiny kernel startup crash
- Index(es):
Relevant Pages
|
