Re: Newbie - First attemt to load nk.bin to target (ce 6.0, x386 devi

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I remember following the same steps as you did when I started my CE
development. I couldn't get it working either. A couple of things you should
consider:

1. If you want to download an image over the network, the bootloader will
need to be able to control the network adapter in your target laptop. It
doesn't support just any network adapter.

This having said, you should look for the specifications needed for the CEPC
platform.

The standard CE video driver for instance requires your video adapter to be
vesa 2.0 compatible.

A very important thing is the debug output port. CE sends debug and other
messages trough a serial port. If you connect that port with a NULL modem
cable to another PC serial port, you can follow the boot proces and see were
things go wrong.

If the USB legacy support is enabled in your bios, it will conflict with the
CE USB driver if you have one in your image.

In my opinion, you better start experimenting with a platform that has CE
support already. Just make sure it comes with the sources of the BSP (board
support package), so that you can learn from it. If your company will make
it's own platform, try to find a platform with the same cpu architecture and
support chips.

I can't disagree about the benefit of a training either. You will probably
get more out of your training if you already learned some of the basics of
CE development.

Take a look at the Microsoft SPARK project for cheap hardware platforms with
CE support.




"senrdev" <senrdev@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C561895-CE19-479F-B3CA-C0BC0642717B@xxxxxxxxxxxxxxxx
Hi, can anybody help - am I missing something?

I have spent many hours now Googling around and still no real answers,
although many helpful tips (thanks everybody)

I am a complete newbie to embedded, although a professional developer
in mainstream .NET apps. Our new small company is building a CE
device (not yet ready for me to play with - in fact it will be my
job to set it all up when I do get it) so to familiarize with all this
I am trying to create a ce 6.0 system on an old Dell laptop -
simple as I can make it, standard laptop, hard drive, serial port,
dos 622 loaded, (diskette drive available)

On my main development computer I have built a no-frills "all default"
nk.bin with the ce600 (vs 2005) add-on (custom device, x86 cepc)

I have tried to download this bin to my target machine without success
using (so far) 2 methods

1. Ethernet

I would like to use ethernet but do not know how to get plain dos
to handle that (any ideas, special drivers needed?) so I turned to

2. serial.

Seemed simple enough. I assumed that I would need serial comms
software so I set that up in dos.

At the end of the build the vs tool starts communicating ok with the
target dos machine and I see the target continually displaying the
sent-over polling requests but the devlopment system never
receives back a "BOOTME" response (it just waits on that. How do I
set up a way to send back BOOTME (is there some special software I
have to install in the dos? Does it use sbin for example to create BOOTME
packets?)

3. Several web tips suggested using loadcepc on the target in local
mode to directly load the nk.bin file, instead of downloading
I tried that, copying the bootloader stuff to my target dos device and the
nk.bin file but loadcepc just literally "freezes" - no messages, as if it
is
a completely invalid dos exe. If I rename the nk.bin for a test loadcepc
does not even complain about that so clearly it is crashing way before
that

My question there is - can I simply use the supplied loadcepc (from
the ce600 toolkit) on my dos machine or does it have to be specially
"made" from the source supplied (via parameters or something)

Any help on the install process would be most appreciated, thanks

Rob



.

Relevant Pages

  • Re: Newbie - First attemt to load nk.bin to target (ce 6.0, x386
    ... cable to another PC serial port, you can follow the boot proces and see were ... If the USB legacy support is enabled in your bios, ... I have tried to download this bin to my target machine without success ... I would like to use ethernet but do not know how to get plain dos ...
    (microsoft.public.windowsce.platbuilder)
  • Re: SDI2HD- Additional Question From Orig Author
    ... I understand why you can't use xcopy from DOS. ... party solutions that support long file names under DOS. ... the target storage, this approach may work just fine for you. ...
    (microsoft.public.windowsxp.embedded)
  • Re: BP 7.0 has seconds of delay under WinXP
    ... FPC uses v2, apparantly I'm mistaking/outdated since go32.exe is no longer ... FPC did support go32v1, but I never saw it run. ... there are other DOS extenders that were demand loaded (e.g. ... On Windows it even has the linker built-in. ...
    (comp.lang.pascal.borland)
  • Re: BP 7.0 has seconds of delay under WinXP
    ... DJGPP decided it was too much trouble to support both DPMI and e.g. ... there are other DOS extenders that were demand loaded (e.g. ...
    (comp.lang.pascal.borland)
  • Re: Win32Forth command-line apps
    ... support for DOS has reduced ... They changed the driver model in Vista, ... Win2k did actually add LFN support to DOS apps (previously ... is almost the only way for DOS apps to access more RAM under Windows? ...
    (comp.lang.forth)