I can't seem to able to build/ make the eboot or uboot successfully.
Any suggestion?

Re: builidng eboot/uboot using cygwin by Bruce

Bruce
Wed Mar 12 15:44:56 PDT 2008

It is going to be very difficult for us to give you any suggestions if we
don't know anything about what you are doing.

What version of CE
What BSP?
What are you doing to try to build it?
What is going wrong?

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"garlic" <garlic@yahoo.com.sg> wrote in message
news:BBBEF351-E0F3-4AA2-9840-6F1E0756047F@microsoft.com...
>I can't seem to able to build/ make the eboot or uboot successfully.
> Any suggestion?



Re: builidng eboot/uboot using cygwin by Silver

Silver
Wed Mar 12 17:13:34 PDT 2008

Step one: Read the instructions, concentrate on the developing an OS and
developing Drivers areas, and perhaps the building a bootloader section
(http://msdn2.microsoft.com/en-us/library/aa909653.aspx):
http://msdn2.microsoft.com/en-us/library/bb159115.aspx

Uboot has nothing to do with MS so you will not find help for that in the
docs.

Here is the quick overview of building an OS:
http://msdn2.microsoft.com/en-us/library/aa908931.aspx

You seem to be coming from a Linux environment so here are a few tips. Note
that many statements here greatly simplify what is happening, but it is a
start.

- never changes files in the wince600\public tree
- You don't need to build a root file system - it is part of the image that
gets build, "nk.bin"
nk.bin is comprised:
kernel
filesystem
registry
drivers
some applications
"other stuff" like fonts, icons, links etc....

- never changes files in the wince600\public tree
- What goes into nk.bin is controlled largely by the catalog, which in turns
sets environment variables - SYSGEN_xxx variables. BSP_xxx variables are
used too.
- The build files get put into the 'release' directory. That is where you
will find nk.bin.
- A BSP for CE has the same concept as a BSP for Linux.
- never changes files in the wince600\public tree
- The usual bootloader is "eboot". How is is build is BSP dependent, but it
is usually built as part of the platform.
- Building is done in phases. When you have decided what pieces to put into
your OS by putting the pieces into the workspace from the catalog you will
need to 'sysgen'. This creates lots of libraries with the components from
the catalog/sysgen_xxx variables. See here:
http://msdn2.microsoft.com/en-us/library/aa909653.aspx
- It then copies that stuff to the release dir
- Then it bundles the applicable pieces into the final nk.bin. (read about
bib files http://msdn2.microsoft.com/en-us/library/aa908680.aspx,
http://msdn2.microsoft.com/en-us/library/aa909329.aspx)



Re: builidng eboot/uboot using cygwin by garlic

garlic
Wed Mar 12 18:22:01 PDT 2008

I get the idea
PXA255 boot process is ================================
board power up goes to Reset vector address, RVA locate bootdrive and
jumps immediately to vector 0x00 where the eboot resides that will pull the
NK.bin
This means that if i am booting from a CF/SD card, two files(eboot.bin
&NK.bin) must reside inside??

Now how do i create or setup a eboot? Does the platform wizard set it up for
me?
IS the directory in c:\WinCE500\platform\CEPC\src\BL?


Re: builidng eboot/uboot using cygwin by Bruce

Bruce
Thu Mar 13 05:28:17 PDT 2008

No, you don't get the idea. The idea is for you to give us enough details
about what you are doing so that we can assist you. If you really got the
idea you would have answered at least one of my questions, that was the
idea.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"garlic" <garlic@yahoo.com.sg> wrote in message
news:36CA7AF1-6D3B-4AB4-B0D4-666590FE7F76@microsoft.com...
>I get the idea
> PXA255 boot process is ================================
> board power up goes to Reset vector address, RVA locate bootdrive and
> jumps immediately to vector 0x00 where the eboot resides that will pull
> the
> NK.bin
> This means that if i am booting from a CF/SD card, two files(eboot.bin
> &NK.bin) must reside inside??
>
> Now how do i create or setup a eboot? Does the platform wizard set it up
> for
> me?
> IS the directory in c:\WinCE500\platform\CEPC\src\BL?
>



Re: builidng eboot/uboot using cygwin by garlic

garlic
Fri Mar 14 02:36:00 PDT 2008

I went to the below site. do as it mention until step 5, create source file
.c and makefile, paste the sample code and on setp 6 build the bootloader but
with error.

http://msdn2.microsoft.com/en-us/library/ms903967.aspx

command prompt mention
"Failed opening C:%_winCEroot%\public\CEBASE\cesysgen\sdk\inc\ceconfig.h
I understand somehow sysgen.bat are unable to use cesysgen.bat to nmake.exe.
But i don't know what i should do.


Re: builidng eboot/uboot using cygwin by Bruce

Bruce
Fri Mar 14 05:41:25 PDT 2008

Now we are getting someplace. Those instructions are incomplete.

You need to Sysgen your project before building the bootloader. That error
also indicates that you probably have something wrong in your files. The
error probably shouldn't say C:%_winCEroot%... it should say C:\WINCE500.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"garlic" <garlic@yahoo.com.sg> wrote in message
news:68976298-0E1B-4759-B769-211FEFEF2F9C@microsoft.com...
>I went to the below site. do as it mention until step 5, create source file
> .c and makefile, paste the sample code and on setp 6 build the bootloader
> but
> with error.
>
> http://msdn2.microsoft.com/en-us/library/ms903967.aspx
>
> command prompt mention
> "Failed opening C:%_winCEroot%\public\CEBASE\cesysgen\sdk\inc\ceconfig.h
> I understand somehow sysgen.bat are unable to use cesysgen.bat to
> nmake.exe.
> But i don't know what i should do.
>



Re: builidng eboot/uboot using cygwin by garlic

garlic
Fri Mar 14 10:48:00 PDT 2008

Is there a startup.s [entry function for BL] or BL files for Pxa255 that i
can download.
I did sysgen but i have error,
ya, you are right, _winCEroot env path is C:\Wince500. I make that up :>



Re: builidng eboot/uboot using cygwin by Bruce

Bruce
Fri Mar 14 11:08:47 PDT 2008

If you are going to change the error messages, you should note that so we
don't waste time reviewing you change thinking it is the problem.

Why aren't you using a PXA255 BSP?
Why are you starting a project using a PXA255, isn't it end of life really
soon? Or are you just experimenting?

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"garlic" <garlic@yahoo.com.sg> wrote in message
news:174A967A-B34D-4FDF-8BE2-25DE4AE63951@microsoft.com...
> Is there a startup.s [entry function for BL] or BL files for Pxa255 that i
> can download.
> I did sysgen but i have error,
> ya, you are right, _winCEroot env path is C:\Wince500. I make that up :>
>
>



Re: builidng eboot/uboot using cygwin by garlic

garlic
Fri Mar 14 18:35:00 PDT 2008


I know they are end of life next year.
It is an abandon board, use to run on Unix, thus no WinCE BSP

I try communicating the board with RS232, Ethernet but to no avail.
I thought of getting JTAG to download WinCE support bootloader into Flash .
Is this the only approach



Thanks
Alvin


"Bruce Eitman [eMVP]" wrote:

> If you are going to change the error messages, you should note that so we
> don't waste time reviewing you change thinking it is the problem.
>
> Why aren't you using a PXA255 BSP?
> Why are you starting a project using a PXA255, isn't it end of life really
> soon? Or are you just experimenting?
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> beitman AT applieddata DOT net
>
> Applied Data Systems
> www.applieddata.net
> An ISO 9001:2000 Registered Company
> Microsoft WEP Gold-level Member
>
> "garlic" <garlic@yahoo.com.sg> wrote in message
> news:174A967A-B34D-4FDF-8BE2-25DE4AE63951@microsoft.com...
> > Is there a startup.s [entry function for BL] or BL files for Pxa255 that i
> > can download.
> > I did sysgen but i have error,
> > ya, you are right, _winCEroot env path is C:\Wince500. I make that up :>
> >
> >
>
>
>

Re: builidng eboot/uboot using cygwin by garlic

garlic
Sat Mar 15 07:05:00 PDT 2008


What are the files that i need to put on the CF card so that the processor
PXA255 will read and load the NK.bin inside the CF card?

When reset, the PXA255 detecting bootloader in the CF card will run it
rather than the bootloader in the Flash and upload the NK.bin in the CF card?


Re: builidng eboot/uboot using cygwin by Chris

Chris
Sat Mar 15 09:03:09 PDT 2008

The PXA255 can't and doesn't know jack about the CF card. When it's booted
it starts execution at address zero. Presumably you'll have Flash at that
address and you'll have your bootloader code written there. A fairly common
path is to do minimal initialization and then load the entire bootloader
into RAM and complete execution from there. The bootloader could have code
that allows it to access a CF card and read the FAT to pull out files and
write then into flash (including a new bootloader - which is why it's good
to be executing from RAM) or RAM and then jump to them when loaded. How
that progresses is very much hardware dependent and very much up to what you
want it to do.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com


"garlic" <garlic@yahoo.com.sg> wrote in message
news:6B3593CC-EBE2-44E6-89FD-453BC0333382@microsoft.com...
>
> What are the files that i need to put on the CF card so that the processor
> PXA255 will read and load the NK.bin inside the CF card?
>
> When reset, the PXA255 detecting bootloader in the CF card will run it
> rather than the bootloader in the Flash and upload the NK.bin in the CF
> card?
>



Re: builidng eboot/uboot using cygwin by Chris

Chris
Sat Mar 15 09:04:18 PDT 2008


Yes, JTAG is likely the only way to get the bootloader onto it (unless it
already has a bootloader which can update itself - kind of a Catch-22
though.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

"garlic" <garlic@yahoo.com.sg> wrote in message
news:B0449F5B-6F74-40FA-93DF-DDAD93B29788@microsoft.com...
>
> I know they are end of life next year.
> It is an abandon board, use to run on Unix, thus no WinCE BSP
>
> I try communicating the board with RS232, Ethernet but to no avail.
> I thought of getting JTAG to download WinCE support bootloader into Flash
> .
> Is this the only approach
>
>
>
> Thanks
> Alvin
>
>
> "Bruce Eitman [eMVP]" wrote:
>
>> If you are going to change the error messages, you should note that so we
>> don't waste time reviewing you change thinking it is the problem.
>>
>> Why aren't you using a PXA255 BSP?
>> Why are you starting a project using a PXA255, isn't it end of life
>> really
>> soon? Or are you just experimenting?
>>
>> --
>> Bruce Eitman (eMVP)
>> Senior Engineer
>> beitman AT applieddata DOT net
>>
>> Applied Data Systems
>> www.applieddata.net
>> An ISO 9001:2000 Registered Company
>> Microsoft WEP Gold-level Member
>>
>> "garlic" <garlic@yahoo.com.sg> wrote in message
>> news:174A967A-B34D-4FDF-8BE2-25DE4AE63951@microsoft.com...
>> > Is there a startup.s [entry function for BL] or BL files for Pxa255
>> > that i
>> > can download.
>> > I did sysgen but i have error,
>> > ya, you are right, _winCEroot env path is C:\Wince500. I make that up
>> > :>
>> >
>> >
>>
>>
>>



Re: builidng eboot/uboot using cygwin by garlic

garlic
Sat Mar 15 14:33:00 PDT 2008

But i am able to update a unix os onto it using a CF card. I thought the
Bootloader in the CF card will overright the BL in the Flash, why can't it do
that.
what are the files that should reside in the CF card?



"Chris Tacke, eMVP" wrote:

> Yes, JTAG is likely the only way to get the bootloader onto it (unless it
> already has a bootloader which can update itself - kind of a Catch-22
> though.
>
>
> --
>
> Chris Tacke, Embedded MVP
> OpenNETCF Consulting
> Giving back to the embedded community
> http://community.OpenNETCF.com
>
> "garlic" <garlic@yahoo.com.sg> wrote in message
> news:B0449F5B-6F74-40FA-93DF-DDAD93B29788@microsoft.com...
> >
> > I know they are end of life next year.
> > It is an abandon board, use to run on Unix, thus no WinCE BSP
> >
> > I try communicating the board with RS232, Ethernet but to no avail.
> > I thought of getting JTAG to download WinCE support bootloader into Flash
> > .
> > Is this the only approach
> >
> >
> >
> > Thanks
> > Alvin
> >
> >
> > "Bruce Eitman [eMVP]" wrote:
> >
> >> If you are going to change the error messages, you should note that so we
> >> don't waste time reviewing you change thinking it is the problem.
> >>
> >> Why aren't you using a PXA255 BSP?
> >> Why are you starting a project using a PXA255, isn't it end of life
> >> really
> >> soon? Or are you just experimenting?
> >>
> >> --
> >> Bruce Eitman (eMVP)
> >> Senior Engineer
> >> beitman AT applieddata DOT net
> >>
> >> Applied Data Systems
> >> www.applieddata.net
> >> An ISO 9001:2000 Registered Company
> >> Microsoft WEP Gold-level Member
> >>
> >> "garlic" <garlic@yahoo.com.sg> wrote in message
> >> news:174A967A-B34D-4FDF-8BE2-25DE4AE63951@microsoft.com...
> >> > Is there a startup.s [entry function for BL] or BL files for Pxa255
> >> > that i
> >> > can download.
> >> > I did sysgen but i have error,
> >> > ya, you are right, _winCEroot env path is C:\Wince500. I make that up
> >> > :>
> >> >
> >> >
> >>
> >>
> >>
>
>
>

Re: builidng eboot/uboot using cygwin by Chris

Chris
Sat Mar 15 17:07:02 PDT 2008

That is completely up to the existing bootloader. The PXA255 knows nothing
and does nothing but execute at zero at boot. Obviously your hardware has
flash at that address and some sort of Unix/Linux bootloader aleady there.
What the behavior of that bootloader is we can't tell you. Can you use it
to write eboot.bin to Flash? Again, we don't know (I suspect it could be
done if you can use it to update the Unix bootloader).

Files on a CF card are purely pulled in by the bootloader - the processor
has no concept of a "CF card" let alone a FAT file system. You need to
either get more info on the bootloader you have and its behavior, or just
JTAG down your CE bootloader. Will that bootloader pull files of a CF card?
Again, we can't say. Depends on what the code for your bootloader does.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com


"garlic" <garlic@yahoo.com.sg> wrote in message
news:0B9DFD8C-28D0-460D-9B24-D692047540C5@microsoft.com...
> But i am able to update a unix os onto it using a CF card. I thought the
> Bootloader in the CF card will overright the BL in the Flash, why can't it
> do
> that.
> what are the files that should reside in the CF card?
>
>
>
> "Chris Tacke, eMVP" wrote:
>
>> Yes, JTAG is likely the only way to get the bootloader onto it (unless it
>> already has a bootloader which can update itself - kind of a Catch-22
>> though.
>>
>>
>> --
>>
>> Chris Tacke, Embedded MVP
>> OpenNETCF Consulting
>> Giving back to the embedded community
>> http://community.OpenNETCF.com
>>
>> "garlic" <garlic@yahoo.com.sg> wrote in message
>> news:B0449F5B-6F74-40FA-93DF-DDAD93B29788@microsoft.com...
>> >
>> > I know they are end of life next year.
>> > It is an abandon board, use to run on Unix, thus no WinCE BSP
>> >
>> > I try communicating the board with RS232, Ethernet but to no avail.
>> > I thought of getting JTAG to download WinCE support bootloader into
>> > Flash
>> > .
>> > Is this the only approach
>> >
>> >
>> >
>> > Thanks
>> > Alvin
>> >
>> >
>> > "Bruce Eitman [eMVP]" wrote:
>> >
>> >> If you are going to change the error messages, you should note that so
>> >> we
>> >> don't waste time reviewing you change thinking it is the problem.
>> >>
>> >> Why aren't you using a PXA255 BSP?
>> >> Why are you starting a project using a PXA255, isn't it end of life
>> >> really
>> >> soon? Or are you just experimenting?
>> >>
>> >> --
>> >> Bruce Eitman (eMVP)
>> >> Senior Engineer
>> >> beitman AT applieddata DOT net
>> >>
>> >> Applied Data Systems
>> >> www.applieddata.net
>> >> An ISO 9001:2000 Registered Company
>> >> Microsoft WEP Gold-level Member
>> >>
>> >> "garlic" <garlic@yahoo.com.sg> wrote in message
>> >> news:174A967A-B34D-4FDF-8BE2-25DE4AE63951@microsoft.com...
>> >> > Is there a startup.s [entry function for BL] or BL files for Pxa255
>> >> > that i
>> >> > can download.
>> >> > I did sysgen but i have error,
>> >> > ya, you are right, _winCEroot env path is C:\Wince500. I make that
>> >> > up
>> >> > :>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>



Re: builidng eboot/uboot using cygwin by garlic

garlic
Sun Mar 16 06:19:01 PDT 2008

Thanks

Obviously your hardware has flash at that address and some sort of
Unix/Linux bootloader aleady there.
What the behavior of that bootloader is we can't tell you. Can you use it
to write eboot.bin to Flash?
1) does this need to be Flash over using JTAG (bec i have not bought it yet)
2) Can you direct me on where to get a free eboot.bin


Files on a CF card are purely pulled in by the bootloader - the processor
has no concept of a "CF card" let alone a FAT file system. You need to
either get more info on the bootloader you have and its behavior, or just
JTAG down your CE bootloader.
>i do not have a JTAG to get more info on the BL. Must i get a JTAG?

thanks for the help



Re: builidng eboot/uboot using cygwin by Dean

Dean
Mon Mar 17 06:17:47 PDT 2008

You are completely missing the point. Based on what you've told us so far
it is *impossible* for you to do any WindowsCE development with this board.

Let me try to be clear:
1) You MUST have a BSP for THIS board in order to create an eboot or OS
image that will run on this board.
2) It is IMPOSSIBLE to put a generic/free bootloader onto this device and
expect it to do anything at all. You could get it into flash using either
your existing Linux bootloader or jtag, but once there it would NOT run.
3) It is IMPOSSIBLE to put a generic OS image onto this device and expect it
to do anything at all. You could get it into flash using either your
existing Linux bootloader or jtag, but once there it would NOT run.
4) You MUST have complete specification (schematics or equivalent) for the
entire BOARD (not CPU) in order to create a BSP for this device. That BSP
(that you can't create without schematics) is REQUIRED in order to create a
bootloader or OS that will run on the device (see #1)
5) It is IMPOSSIBLE for us to tell you how your existing bootloader works or
what it expects. Only the entity that created the bootloader can tell you
that.

The bottom line is this: You must have a BSP written specifically for this
board in order to get WindowsCE to run on this device. You say you don't
have that. Therefore you must write one specifically for this board, and
that can only be done if you have full schematics for the board. Do you?
If not, throw the board away because it can't be done. If you do, get ready
for months of development time because it's going to take that long.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"garlic" <garlic@yahoo.com.sg> wrote in message
news:83BD14CC-D413-40C4-87B9-B296C4C28A0B@microsoft.com...
> Thanks
>
> Obviously your hardware has flash at that address and some sort of
> Unix/Linux bootloader aleady there.
> What the behavior of that bootloader is we can't tell you. Can you use it
> to write eboot.bin to Flash?
> 1) does this need to be Flash over using JTAG (bec i have not bought it
> yet)
> 2) Can you direct me on where to get a free eboot.bin
>
>
> Files on a CF card are purely pulled in by the bootloader - the processor
> has no concept of a "CF card" let alone a FAT file system. You need to
> either get more info on the bootloader you have and its behavior, or just
> JTAG down your CE bootloader.
>>i do not have a JTAG to get more info on the BL. Must i get a JTAG?
>
> thanks for the help
>
>



Re: builidng eboot/uboot using cygwin by garlic

garlic
Mon Mar 17 19:01:03 PDT 2008

Understand, I will try to find a third party who can bring the board up with
the available schematic, if i am doing it, i will need training. Many thanks


"Dean Ramsier" wrote:

> You are completely missing the point. Based on what you've told us so far
> it is *impossible* for you to do any WindowsCE development with this board.
>
> Let me try to be clear:
> 1) You MUST have a BSP for THIS board in order to create an eboot or OS
> image that will run on this board.
> 2) It is IMPOSSIBLE to put a generic/free bootloader onto this device and
> expect it to do anything at all. You could get it into flash using either
> your existing Linux bootloader or jtag, but once there it would NOT run.
> 3) It is IMPOSSIBLE to put a generic OS image onto this device and expect it
> to do anything at all. You could get it into flash using either your
> existing Linux bootloader or jtag, but once there it would NOT run.
> 4) You MUST have complete specification (schematics or equivalent) for the
> entire BOARD (not CPU) in order to create a BSP for this device. That BSP
> (that you can't create without schematics) is REQUIRED in order to create a
> bootloader or OS that will run on the device (see #1)
> 5) It is IMPOSSIBLE for us to tell you how your existing bootloader works or
> what it expects. Only the entity that created the bootloader can tell you
> that.
>
> The bottom line is this: You must have a BSP written specifically for this
> board in order to get WindowsCE to run on this device. You say you don't
> have that. Therefore you must write one specifically for this board, and
> that can only be done if you have full schematics for the board. Do you?
> If not, throw the board away because it can't be done. If you do, get ready
> for months of development time because it's going to take that long.
>
> --
> Dean Ramsier - eMVP
> BSQUARE Corporation
>
>
> "garlic" <garlic@yahoo.com.sg> wrote in message
> news:83BD14CC-D413-40C4-87B9-B296C4C28A0B@microsoft.com...
> > Thanks
> >
> > Obviously your hardware has flash at that address and some sort of
> > Unix/Linux bootloader aleady there.
> > What the behavior of that bootloader is we can't tell you. Can you use it
> > to write eboot.bin to Flash?
> > 1) does this need to be Flash over using JTAG (bec i have not bought it
> > yet)
> > 2) Can you direct me on where to get a free eboot.bin
> >
> >
> > Files on a CF card are purely pulled in by the bootloader - the processor
> > has no concept of a "CF card" let alone a FAT file system. You need to
> > either get more info on the bootloader you have and its behavior, or just
> > JTAG down your CE bootloader.
> >>i do not have a JTAG to get more info on the BL. Must i get a JTAG?
> >
> > thanks for the help
> >
> >
>
>
>

Re: builidng eboot/uboot using cygwin by Chris

Chris
Mon Mar 17 20:56:11 PDT 2008

And I'd say that "months" is likely optimistic. It's probably more than
that starting from no BSP at all.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com


"Dean Ramsier" <ramsiernospam@nospam.com> wrote in message
news:%23t$1MFDiIHA.3780@TK2MSFTNGP06.phx.gbl...
> You are completely missing the point. Based on what you've told us so far
> it is *impossible* for you to do any WindowsCE development with this
> board.
>
> Let me try to be clear:
> 1) You MUST have a BSP for THIS board in order to create an eboot or OS
> image that will run on this board.
> 2) It is IMPOSSIBLE to put a generic/free bootloader onto this device and
> expect it to do anything at all. You could get it into flash using either
> your existing Linux bootloader or jtag, but once there it would NOT run.
> 3) It is IMPOSSIBLE to put a generic OS image onto this device and expect
> it to do anything at all. You could get it into flash using either your
> existing Linux bootloader or jtag, but once there it would NOT run.
> 4) You MUST have complete specification (schematics or equivalent) for the
> entire BOARD (not CPU) in order to create a BSP for this device. That BSP
> (that you can't create without schematics) is REQUIRED in order to create
> a bootloader or OS that will run on the device (see #1)
> 5) It is IMPOSSIBLE for us to tell you how your existing bootloader works
> or what it expects. Only the entity that created the bootloader can tell
> you that.
>
> The bottom line is this: You must have a BSP written specifically for this
> board in order to get WindowsCE to run on this device. You say you don't
> have that. Therefore you must write one specifically for this board, and
> that can only be done if you have full schematics for the board. Do you?
> If not, throw the board away because it can't be done. If you do, get
> ready for months of development time because it's going to take that long.
>
> --
> Dean Ramsier - eMVP
> BSQUARE Corporation
>
>
> "garlic" <garlic@yahoo.com.sg> wrote in message
> news:83BD14CC-D413-40C4-87B9-B296C4C28A0B@microsoft.com...
>> Thanks
>>
>> Obviously your hardware has flash at that address and some sort of
>> Unix/Linux bootloader aleady there.
>> What the behavior of that bootloader is we can't tell you. Can you use
>> it
>> to write eboot.bin to Flash?
>> 1) does this need to be Flash over using JTAG (bec i have not bought it
>> yet)
>> 2) Can you direct me on where to get a free eboot.bin
>>
>>
>> Files on a CF card are purely pulled in by the bootloader - the processor
>> has no concept of a "CF card" let alone a FAT file system. You need to
>> either get more info on the bootloader you have and its behavior, or just
>> JTAG down your CE bootloader.
>>>i do not have a JTAG to get more info on the BL. Must i get a JTAG?
>>
>> thanks for the help
>