Connecting to a Local Image

I have a locally booted image (i.e. not using eboot). I want to be
able to connect to the device from Platform Builder to get the system
information.

What build options do I have to set to allow me to connect to the
device.

Thanks,
J

query_me2001
Wed Feb 11 08:20:44 CST 2004

query_me2001@yahoo.co.uk (John Flynn) wrote in message news:<761ef898.0402101324.72eba912@posting.google.com>...
> I have a locally booted image (i.e. not using eboot). I want to be
> able to connect to the device from Platform Builder to get the system
> information.
>
> What build options do I have to set to allow me to connect to the
> device.
>
> Thanks,
> J

The sort of tools that I want to use is under the "Tools -> Remote
xxxxx" selection. I would want to connect to the target system over
Ethernet.

J

anonymous
Thu Feb 12 05:16:06 CST 2004

Can anyone please help me with this one

Thanks
J

Oliver
Thu Feb 12 08:16:00 CST 2004

Hi John,

these thinks had been discussed a lot of time in this newsgroup, so try a
search with google in groups *windowsce*.

So just a short description what you have to do:
Add network adapter to your device which will be supported by Windows CE
(e.g. NE2000 compatible)
To get all informations from your device your image must be a debug image
with options KITL, CE Target Control and Kernel Debug in Platform -
Settings - Build Options.
Also your image has to include Platform Manager Base Engine and Transports
TCP/IP and KITL (all from catalog).
Make settings for your ethernet adapter in autoexec.bat of your bootdisk
(IOBase, IRQ, IP)
Start your device with bootdisk and select eboot.bin startup.
Go in Platform Builder Workspace to Target - Configure Remote Connection.
Set Download and Transport to Ethernet and click ethernet.
Wait till an entry magically appears in the box (about 30 - 60 seconds after
booting your CE device)
Select it and click OK and OK again (parent window).
Select Target - Download / Initialize and your image will be send to your
device.
Select a remote tool you want and click Cancel (first we have to configure
remote connection).
Select Connection - Configure.
Select Device and Properties.
Set Transport to KITL and startup to CESH
Close all dialogs with OK (ignore the test).
Select Connection - Connect and select your device.
Happy connection!!

Best regards,
Oliver Münchow
--
---------------------------------------
Gesytec GmbH eMail:
52076 Aachen omuenchowATgesytecDOTde
http://www.gesytec.de


"John Flynn" <anonymous@discussions.microsoft.com> schrieb im Newsbeitrag
news:2B77DA04-E3E2-4A84-A6A6-165E045A0C3A@microsoft.com...
> Can anyone please help me with this one.
>
> Thanks,
> J

Rui
Fri Feb 13 10:05:36 CST 2004

1. You must build your image with KITL enabled.
2. If you build your image KITL enabled, when it boots up (not matter you
launched it from EBOOT or some whatever bootloader), the OS will halt there
until KITL is connected. You can then connect from your PB to the image.

There may be something tricky like most platforms have the driver globals
that contain the filed for EDBG information. You may need to zero that field
in your loader (if not EBOOT) before jump to the image (that's how I did on
my platform). This will cause the DHCP process being activated. However,
this is highly depend on the OAL implementation, you should read it and
uderstand how it works if there is a problem.

--

Rui Tang
Centrality Communications Inc


"John Flynn" <anonymous@discussions.microsoft.com> wrote in message
news:3A67FF9E-2810-4CD9-8F3F-A9928E5DDD51@microsoft.com...
> Oliver,
>
> Thank you very much for your reply. I was beginning to think there was no
one out there!
>
> I must have described my problem incorrectly. The method that you
described is what I use normally for development and this works fine.
>
> The problem that I now have is that I compiling the nk.bin image then
placing in on the hard disk of the target machine. I then boot to this image
(a local image). I can successfully boot and run Windows CE using this
method.
>
> What I now want to do is use the Platform Builder remote tools to get
information from the target system.
>
> Firstly, can this be achieved? If so how?
>
> I hope that I have explained this a bit better.
>
> Regards,
> John

query_me2001
Wed Feb 18 05:03:30 CST 2004

This works for a system that is in the lab, but if the system is out
in the field then it would not work. I would want to bring a host
system with PB on it and connect to the target system that is running
Window CE.

The scanario I have in mind is that the image would boot completely to
Windows CE. At some later stage I may want to connect to the system
and use remote tools - but not necessarily.

Regards,
J


"Rui Tang" <tangrui76_nospam@hotmail.com> wrote in message news:<#Vtc8uk8DHA.632@TK2MSFTNGP12.phx.gbl>...
> 1. You must build your image with KITL enabled.
> 2. If you build your image KITL enabled, when it boots up (not matter you
> launched it from EBOOT or some whatever bootloader), the OS will halt there
> until KITL is connected. You can then connect from your PB to the image.
>
> There may be something tricky like most platforms have the driver globals
> that contain the filed for EDBG information. You may need to zero that field
> in your loader (if not EBOOT) before jump to the image (that's how I did on
> my platform). This will cause the DHCP process being activated. However,
> this is highly depend on the OAL implementation, you should read it and
> uderstand how it works if there is a problem.
>
> --
>
> Rui Tang
> Centrality Communications Inc
>
>
> "John Flynn" <anonymous@discussions.microsoft.com> wrote in message
> news:3A67FF9E-2810-4CD9-8F3F-A9928E5DDD51@microsoft.com...
> > Oliver,
> >
> > Thank you very much for your reply. I was beginning to think there was no
> one out there!
> >
> > I must have described my problem incorrectly. The method that you
> described is what I use normally for development and this works fine.
> >
> > The problem that I now have is that I compiling the nk.bin image then
> placing in on the hard disk of the target machine. I then boot to this image
> (a local image). I can successfully boot and run Windows CE using this
> method.
> >
> > What I now want to do is use the Platform Builder remote tools to get
> information from the target system.
> >
> > Firstly, can this be achieved? If so how?
> >
> > I hope that I have explained this a bit better.
> >
> > Regards,
> > John