How Boot from USB

I am new to Windows CE. I use Windows Ce 6.0 and ICOP VSX-6154 Borad. I made
My Image by using Visual Studio 2005(I used all default options). I compiled
my Image. I connected My Target device to my developing station by ethernet
cable. I booted My target device into DOS(I have bootable flash connected to
USB). I copied LOADCEPC and EBoot.bin into my flash. I typed LoadCEPC
Eboot.bin. After a while the image started to be copied into my target
device. after the copy process completed, my Monitor is blank and it seems
that my target device hanged. My device works by demo Images. How could I
boot my target device By my Image(Nk.bin). Is there any other way to copy
NK.bin into flash and boot target device directly? Your immediate response
would be appreciated.

Bruce
Tue May 20 08:31:43 PDT 2008

"I used all default options" Huh? You say that like it clears everything
up, but it doesn't. How did you create your project? Do you have a BSP for
the board?

Debug output would be very valuable here.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

"Samoody" <Samoody@discussions.microsoft.com> wrote in message
news:D599B9AC-BC95-44BB-AFF0-50A51BF07423@microsoft.com...
>I am new to Windows CE. I use Windows Ce 6.0 and ICOP VSX-6154 Borad. I
>made
> My Image by using Visual Studio 2005(I used all default options). I
> compiled
> my Image. I connected My Target device to my developing station by
> ethernet
> cable. I booted My target device into DOS(I have bootable flash connected
> to
> USB). I copied LOADCEPC and EBoot.bin into my flash. I typed LoadCEPC
> Eboot.bin. After a while the image started to be copied into my target
> device. after the copy process completed, my Monitor is blank and it seems
> that my target device hanged. My device works by demo Images. How could I
> boot my target device By my Image(Nk.bin). Is there any other way to copy
> NK.bin into flash and boot target device directly? Your immediate response
> would be appreciated.
>

Paul
Tue May 20 08:32:46 PDT 2008

We can't tell you what's going wrong because you've not given us enough
information to help. Is this a DEBUG or RETAIL build of the OS that you're
loading? If DEBUG, it's almost certain that the image was built expecting
to use the Kernel Debugger over KITL, so you *MUST* connect Platform Builder
up or the OS will be sitting on your device forever waiting for the debugger
to be ready. You have to know how your image is built and, if it is a DEBUG
image, how it's expecting to connect to the debugger. It's quite possible
that one of the device's serial ports is committed to debug messages and, if
so, capturing those with Hyperterminal or something would tell you what's
going on. This should be the first step, after you figure out what your BSP
is expecting with respect to debugging and whether you've built a DEBUG or
RETAIL OS.

Paul T.

"Samoody" <Samoody@discussions.microsoft.com> wrote in message
news:D599B9AC-BC95-44BB-AFF0-50A51BF07423@microsoft.com...
>I am new to Windows CE. I use Windows Ce 6.0 and ICOP VSX-6154 Borad. I
>made
> My Image by using Visual Studio 2005(I used all default options). I
> compiled
> my Image. I connected My Target device to my developing station by
> ethernet
> cable. I booted My target device into DOS(I have bootable flash connected
> to
> USB). I copied LOADCEPC and EBoot.bin into my flash. I typed LoadCEPC
> Eboot.bin. After a while the image started to be copied into my target
> device. after the copy process completed, my Monitor is blank and it seems
> that my target device hanged. My device works by demo Images. How could I
> boot my target device By my Image(Nk.bin). Is there any other way to copy
> NK.bin into flash and boot target device directly? Your immediate response
> would be appreciated.
>

Mauricio
Tue May 20 11:58:15 PDT 2008

Hi Samoody,

You have two ways to load you windows ce (nk.bin) image in your
platform.

First -> Install the DOS in your flash, copy the loadcepc and your
image (nk.bin) to the flash and execute the "loadcepc nk.bin" in
autoexec.bat
this link will help you to configure the loadcepc tool (http://
msdn.microsoft.com/en-us/library/aa448678.aspx)

Second (indicate) -> Install the Windows CE Boot Loader (BLDR) in your
platform and copy the image (nk.bin) to flash
this link will help you to do that (http://www.dmp.com.tw/tech/os-
wince/Boot_Windows_CE_from_DOM.pdf)

You can=B4t to forget to remove the KITL variable of you environment
before to compile your image.


I hope to be helpfull

Mauricio de Sousa Coelho
Windows CE R&D Team
www.connec.com.br

Bruce
Tue May 20 12:18:16 PDT 2008

His post indicates that he knows how to load the OS, but it isn't running.

Your suggestion to disable KITL is a good one. Again debug output would be
handy to analyse the real problem.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

"Mauricio Sousa (Connec Brasil)" <mauricio.scoelho1@gmail.com> wrote in
message
news:444c6c8d-4782-480f-bdc7-dafb0f2b0d11@l28g2000prd.googlegroups.com...
Hi Samoody,

You have two ways to load you windows ce (nk.bin) image in your
platform.

First -> Install the DOS in your flash, copy the loadcepc and your
image (nk.bin) to the flash and execute the "loadcepc nk.bin" in
autoexec.bat
this link will help you to configure the loadcepc tool (http://
msdn.microsoft.com/en-us/library/aa448678.aspx)

Second (indicate) -> Install the Windows CE Boot Loader (BLDR) in your
platform and copy the image (nk.bin) to flash
this link will help you to do that (http://www.dmp.com.tw/tech/os-
wince/Boot_Windows_CE_from_DOM.pdf)

You can´t to forget to remove the KITL variable of you environment
before to compile your image.


I hope to be helpfull

Mauricio de Sousa Coelho
Windows CE R&D Team
www.connec.com.br

Samoody
Wed May 21 13:46:02 PDT 2008

Dear All,
Details of my project.
I installed Visual studio SP1 and Windows CE 6.0 SP1 too. I use Vortex
SX-6154(ICOP company) Hardware. I used the following (default options) to
make my Image.
1-Board Support Package: Vortex86SX_60A: x86
2-Design Template: Industrial Device
3-Design Template Variants: Internet Appliance
4-All next Steps: Default
options are selected
5-I Disabled All build options. I just enabled â??Enable Ship Buildâ?? AND
â??Run-time image can be larger than 32Mâ??

I connected my Target device to my developing station by Ethernet and Modem
Null cable. I ran HyperTerminal in my developing station to get debug
information, if there is any.

Then I compiled my Image in Debug & Release mode. I Made a USB stick(1GB)
Dos bootable by Make.bat utility(From ICOP web site) which uses
makebootfat.exe to make USB Flash bootable. I Copied NK.bin, Eboot.bin and
LOADCEPC into my USB flash. I copied ICOPâ??s demo Image into USB flash too.
Then I booted my system into dos. I typed LOADCEPC nk.bin(Release versioin).
LoadCEPC loads image completely. But after that the screen is blank. My hyper
terminal looks like this:

HIMEM - Always On A20 method used
Kernel: allocated 44 Diskbuffers = 23408 Bytes in HMA

FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]

C:\>loadcepc nk.bin
1 PCI bus (Version 3.00) using Configuration Mechanism # 1
******************** 98%

Then I did the same with debug version. The hyper terminal is like this:

C:\>loadcepc nk.bin
1 PCI bus (Version 3.00) using Configuration Mechanism # 1
Error image section doesn't fit in allocated block
Block allocated at 0x129000, size = 33553408
Section physical start = 0x02105000, size = 204800

I rebooted my system. I typed LOADCEPC Eboot.bin. The image starts to be
transferred to target device in visual studio. After that, the screen is
again blank . hyper terminal is like this:

HIMEM - Always On A20 method used
Kernel: allocated 44 Diskbuffers = 23408 Bytes in HMA

FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]

C:\>loadcepc eboot.bin
1 PCI bus (Version 3.00) using Configuration Mechanism # 1
à à àüàüà üüü üüüü à àà à à à ü àà ü à üüà àü

in all situations the output debug window in visual studio shows the
following message:
â??PB Debugger The Kernel Debugger is waiting to connect with target.â??

My hardware is ok. Because I can load Windows CE by demo Image which I
downloaded from ICOP company.
Would you please tell me what the problem is?

I eagerly look forward to hearing from you.

Regards

M.Samoody


"Paul G. Tobey [eMVP]" wrote:

> We can't tell you what's going wrong because you've not given us enough
> information to help. Is this a DEBUG or RETAIL build of the OS that you're
> loading? If DEBUG, it's almost certain that the image was built expecting
> to use the Kernel Debugger over KITL, so you *MUST* connect Platform Builder
> up or the OS will be sitting on your device forever waiting for the debugger
> to be ready. You have to know how your image is built and, if it is a DEBUG
> image, how it's expecting to connect to the debugger. It's quite possible
> that one of the device's serial ports is committed to debug messages and, if
> so, capturing those with Hyperterminal or something would tell you what's
> going on. This should be the first step, after you figure out what your BSP
> is expecting with respect to debugging and whether you've built a DEBUG or
> RETAIL OS.
>
> Paul T.
>
> "Samoody" <Samoody@discussions.microsoft.com> wrote in message
> news:D599B9AC-BC95-44BB-AFF0-50A51BF07423@microsoft.com...
> >I am new to Windows CE. I use Windows Ce 6.0 and ICOP VSX-6154 Borad. I
> >made
> > My Image by using Visual Studio 2005(I used all default options). I
> > compiled
> > my Image. I connected My Target device to my developing station by
> > ethernet
> > cable. I booted My target device into DOS(I have bootable flash connected
> > to
> > USB). I copied LOADCEPC and EBoot.bin into my flash. I typed LoadCEPC
> > Eboot.bin. After a while the image started to be copied into my target
> > device. after the copy process completed, my Monitor is blank and it seems
> > that my target device hanged. My device works by demo Images. How could I
> > boot my target device By my Image(Nk.bin). Is there any other way to copy
> > NK.bin into flash and boot target device directly? Your immediate response
> > would be appreciated.
> >
>
>
>

Sergei
Wed May 21 15:31:11 PDT 2008

Hello,

"Samoody" <Samoody@discussions.microsoft.com> wrote in message
news:847D4E15-89AF-4DE8-B571-99E0F81D1459@microsoft.com...
> Dear All,
> Details of my project.

[unrelated material skipped]

> C:\>loadcepc nk.bin
> 1 PCI bus (Version 3.00) using Configuration Mechanism # 1
> ******************** 98%
>
> Then I did the same with debug version. The hyper terminal is like this:
>
> C:\>loadcepc nk.bin
> 1 PCI bus (Version 3.00) using Configuration Mechanism # 1
> Error image section doesn't fit in allocated block
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Block allocated at 0x129000, size = 33553408
> Section physical start = 0x02105000, size = 204800

here is what would be the starting point of my investigation. The
bootloader, loadcepc, failed to load your image, nk.bin, completely.
Therefore it did not even launch it, hence the black screen (made by
loadcepc).

Something is not right in the last portion of your nk.bin (note that it
failed at 98%). It is not obvious that this problem is directly related to
usb booting. My take on it would be to try exact same image using different
transport or different bootloader.

Sergei R

>
> Regards
> M.Samoody

Samoody
Wed May 21 23:28:11 PDT 2008

hi
loadcepc is OK. I tried the same boot loader for demo IMAGE. It loaded the
windows. you are right the problem is not related to USB. because I tried the
same project by DOM and Screen is blank. When I loaded Demo Image, Hyper
terminal showed 98% as my own IMAGE. but by demo Image the windows started. I
think it is the speed of serial port. before showing the 100% system goes
into windows and the connection with hyper terminal fails.


"Sergei R" wrote:

> Hello,
>
> "Samoody" <Samoody@discussions.microsoft.com> wrote in message
> news:847D4E15-89AF-4DE8-B571-99E0F81D1459@microsoft.com...
> > Dear All,
> > Details of my project.
>
> [unrelated material skipped]
>
> > C:\>loadcepc nk.bin
> > 1 PCI bus (Version 3.00) using Configuration Mechanism # 1
> > ******************** 98%
> >
> > Then I did the same with debug version. The hyper terminal is like this:
> >
> > C:\>loadcepc nk.bin
> > 1 PCI bus (Version 3.00) using Configuration Mechanism # 1
> > Error image section doesn't fit in allocated block
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Block allocated at 0x129000, size = 33553408
> > Section physical start = 0x02105000, size = 204800
>
> here is what would be the starting point of my investigation. The
> bootloader, loadcepc, failed to load your image, nk.bin, completely.
> Therefore it did not even launch it, hence the black screen (made by
> loadcepc).
>
> Something is not right in the last portion of your nk.bin (note that it
> failed at 98%). It is not obvious that this problem is directly related to
> usb booting. My take on it would be to try exact same image using different
> transport or different bootloader.
>
> Sergei R
>
> >
> > Regards
> > M.Samoody
>
>
>

jscott
Thu Jul 03 08:22:00 PDT 2008

Has this issue been resolved? We are having the same issue. What demo image
were you able to get to work. We tried using the sample project that they
have and it won't even open because of special characters in the file name...

"Samoody" wrote:

> hi
> loadcepc is OK. I tried the same boot loader for demo IMAGE. It loaded the
> windows. you are right the problem is not related to USB. because I tried the
> same project by DOM and Screen is blank. When I loaded Demo Image, Hyper
> terminal showed 98% as my own IMAGE. but by demo Image the windows started. I
> think it is the speed of serial port. before showing the 100% system goes
> into windows and the connection with hyper terminal fails.
>
>
> "Sergei R" wrote:
>
> > Hello,
> >
> > "Samoody" <Samoody@discussions.microsoft.com> wrote in message
> > news:847D4E15-89AF-4DE8-B571-99E0F81D1459@microsoft.com...
> > > Dear All,
> > > Details of my project.
> >
> > [unrelated material skipped]
> >
> > > C:\>loadcepc nk.bin
> > > 1 PCI bus (Version 3.00) using Configuration Mechanism # 1
> > > ******************** 98%
> > >
> > > Then I did the same with debug version. The hyper terminal is like this:
> > >
> > > C:\>loadcepc nk.bin
> > > 1 PCI bus (Version 3.00) using Configuration Mechanism # 1
> > > Error image section doesn't fit in allocated block
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > Block allocated at 0x129000, size = 33553408
> > > Section physical start = 0x02105000, size = 204800
> >
> > here is what would be the starting point of my investigation. The
> > bootloader, loadcepc, failed to load your image, nk.bin, completely.
> > Therefore it did not even launch it, hence the black screen (made by
> > loadcepc).
> >
> > Something is not right in the last portion of your nk.bin (note that it
> > failed at 98%). It is not obvious that this problem is directly related to
> > usb booting. My take on it would be to try exact same image using different
> > transport or different bootloader.
> >
> > Sergei R
> >
> > >
> > > Regards
> > > M.Samoody
> >
> >
> >