Install/deploy custom CE6 OS via USB

I've built my OS Design in Embedded CE 6.0 R2 in VS2005 using the ARM BSP,
and it runs fine in the ARM emulator. Now I'd like to deploy it to the
target device itself. I've searched around online for this for hours, but
know I'm missing something b/c the download runtime image dialog sits waiting
for BOOTME from the target device.

The target CE device only has a USB connection, and the device is recognized
through Active Sync (version 3.8) -- so I can browse the device in XP, but
Platform Builder 6.0 in VS2005 doesn't seem to be able to deploy the os image.

Can you give me some pointers (or a reference) that would help me figure
this out?

Thanks for helping a newbie to the community!!!

Silver
Wed Apr 23 09:28:37 PDT 2008

BOOTME comes from eboot - the CE bootloader. Activesync is something the OS
uses to transfer data - a very different creature.

Get your hardware to go into 'eboot' mode to download the nk.bin.

!!!However!!!, "the" ARM BSP worries me - there is no such thing. ARM is a a
company that designs CPUs, a BSP is for a 'board' conataining a lot mare
than a CPU.
You need to build the BSP for your target hardware - what is your target?

Geoff
--

Bruce
Wed Apr 23 10:02:53 PDT 2008

Jon:

Like Geoff, I am concerned about what you are trying to do. I wonder if you
have a consumer device like a Windows Mobile phone or PDA.

The OS that you built is meant to run on the emulator and **nothing** else.
If you had been successful in putting it on your device, you probably would
have a nice paperweight. The same can be said about the OS that is
currently running on your device, it is meant to run on that device and
**nothing** else.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com

EuroTech Inc.
www.EuroTech.com

"Jon P" <Jon P@discussions.microsoft.com> wrote in message
news:C1617F94-6D96-4150-816D-7442FA3B84A6@microsoft.com...
> I've built my OS Design in Embedded CE 6.0 R2 in VS2005 using the ARM BSP,
> and it runs fine in the ARM emulator. Now I'd like to deploy it to the
> target device itself. I've searched around online for this for hours, but
> know I'm missing something b/c the download runtime image dialog sits
> waiting
> for BOOTME from the target device.
>
> The target CE device only has a USB connection, and the device is
> recognized
> through Active Sync (version 3.8) -- so I can browse the device in XP, but
> Platform Builder 6.0 in VS2005 doesn't seem to be able to deploy the os
> image.
>
> Can you give me some pointers (or a reference) that would help me figure
> this out?
>
> Thanks for helping a newbie to the community!!!
>

JonP
Wed Apr 23 11:13:50 PDT 2008

Bruce & Geoff,

Thanks for the pointers; being new, I wasn't clear on the importance of the
unique BSP; I'd, obviously naively, assumed that there was compatibility
among BSPs, but your clarification helps immensely. I'll have to track down
the original BSP (which has been built already).

Thanks again.

"Bruce Eitman [eMVP]" wrote:

> Jon:
>
> Like Geoff, I am concerned about what you are trying to do. I wonder if you
> have a consumer device like a Windows Mobile phone or PDA.
>
> The OS that you built is meant to run on the emulator and **nothing** else.
> If you had been successful in putting it on your device, you probably would
> have a nice paperweight. The same can be said about the OS that is
> currently running on your device, it is meant to run on that device and
> **nothing** else.
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> Bruce.Eitman AT EuroTech DOT com
>
> EuroTech Inc.
> www.EuroTech.com
>
> "Jon P" <Jon P@discussions.microsoft.com> wrote in message
> news:C1617F94-6D96-4150-816D-7442FA3B84A6@microsoft.com...
> > I've built my OS Design in Embedded CE 6.0 R2 in VS2005 using the ARM BSP,
> > and it runs fine in the ARM emulator. Now I'd like to deploy it to the
> > target device itself. I've searched around online for this for hours, but
> > know I'm missing something b/c the download runtime image dialog sits
> > waiting
> > for BOOTME from the target device.
> >
> > The target CE device only has a USB connection, and the device is
> > recognized
> > through Active Sync (version 3.8) -- so I can browse the device in XP, but
> > Platform Builder 6.0 in VS2005 doesn't seem to be able to deploy the os
> > image.
> >
> > Can you give me some pointers (or a reference) that would help me figure
> > this out?
> >
> > Thanks for helping a newbie to the community!!!
> >
>
>
>

Bruce
Wed Apr 23 13:17:16 PDT 2008

You didn't answer the questions about what your device is, which is okay,
but how you download a new OS quite often is device specific. There may be
some commonality, but what your device actually supports is based on
hardware and bootloader support.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com

EuroTech Inc.
www.EuroTech.com

"Jon P" <JonP@discussions.microsoft.com> wrote in message
news:C68F1B07-3744-4921-8133-F263AC9DEC4D@microsoft.com...
> Bruce & Geoff,
>
> Thanks for the pointers; being new, I wasn't clear on the importance of
> the
> unique BSP; I'd, obviously naively, assumed that there was compatibility
> among BSPs, but your clarification helps immensely. I'll have to track
> down
> the original BSP (which has been built already).
>
> Thanks again.
>
> "Bruce Eitman [eMVP]" wrote:
>
>> Jon:
>>
>> Like Geoff, I am concerned about what you are trying to do. I wonder if
>> you
>> have a consumer device like a Windows Mobile phone or PDA.
>>
>> The OS that you built is meant to run on the emulator and **nothing**
>> else.
>> If you had been successful in putting it on your device, you probably
>> would
>> have a nice paperweight. The same can be said about the OS that is
>> currently running on your device, it is meant to run on that device and
>> **nothing** else.
>>
>> --
>> Bruce Eitman (eMVP)
>> Senior Engineer
>> Bruce.Eitman AT EuroTech DOT com
>>
>> EuroTech Inc.
>> www.EuroTech.com
>>
>> "Jon P" <Jon P@discussions.microsoft.com> wrote in message
>> news:C1617F94-6D96-4150-816D-7442FA3B84A6@microsoft.com...
>> > I've built my OS Design in Embedded CE 6.0 R2 in VS2005 using the ARM
>> > BSP,
>> > and it runs fine in the ARM emulator. Now I'd like to deploy it to the
>> > target device itself. I've searched around online for this for hours,
>> > but
>> > know I'm missing something b/c the download runtime image dialog sits
>> > waiting
>> > for BOOTME from the target device.
>> >
>> > The target CE device only has a USB connection, and the device is
>> > recognized
>> > through Active Sync (version 3.8) -- so I can browse the device in XP,
>> > but
>> > Platform Builder 6.0 in VS2005 doesn't seem to be able to deploy the os
>> > image.
>> >
>> > Can you give me some pointers (or a reference) that would help me
>> > figure
>> > this out?
>> >
>> > Thanks for helping a newbie to the community!!!
>> >
>>
>>
>>

JonP
Wed Apr 23 14:39:00 PDT 2008

I've been reading up on BSPs and boot loaders this afternoon. I guess my
moniker of "newbie" was an understatement! :) The boot loader will
definitely be device specific.

One lingering question I had was that once the proper BSP is in place within
Platform Builder, the target device boot loader must initiate the BOOTME
connection (broadcast ethernet from my reading)... but how is this actually
done via a USB connection (which seems to be an option within the PB target
connectivity options); does this mean that the ethernet broadcast is through
the USB?

And in the case of a new device with no OS, drive, etc., how does one
initiate the boot loader on the target device if it's "blank."

If I'm way off in my questions, please forgive. As pointed out elsewhere,
there aren't many books for this that I've seen, but if needed, please feel
free to toss me somewhere that I can get the basics. I've read through the
MSDN "Bringing Up a Board Support Package", but are there other resources for
this?

Thanks in advance! This space is great, and I've learned so much from your
help!

Bruce
Thu Apr 24 05:31:35 PDT 2008

> does this mean that the ethernet broadcast is through
> the USB?

Yes. Your bootloader needs to expose the USBF port as an RNDIS device.

> initiate the boot loader on the target device if it's "blank."

Usually JTAG, but again it is device specific.

http://www.microsoft.com/windows/embedded/support/training/default.mspx

Building Powerful Platforms with Platform Builder by Wilson and Havawala is
an old book for CE 3.0, but much of the information is still very valuable.
The system architecture is outdated, and it dosen't talk about using USB to
download an image, but I still recomend it to get started.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com

EuroTech Inc.
www.EuroTech.com

"Jon P" <JonP@discussions.microsoft.com> wrote in message
news:9B30AA5B-B951-488C-A9AF-86A222C9068C@microsoft.com...
> I've been reading up on BSPs and boot loaders this afternoon. I guess my
> moniker of "newbie" was an understatement! :) The boot loader will
> definitely be device specific.
>
> One lingering question I had was that once the proper BSP is in place
> within
> Platform Builder, the target device boot loader must initiate the BOOTME
> connection (broadcast ethernet from my reading)... but how is this
> actually
> done via a USB connection (which seems to be an option within the PB
> target
> connectivity options); does this mean that the ethernet broadcast is
> through
> the USB?
>
> And in the case of a new device with no OS, drive, etc., how does one
> initiate the boot loader on the target device if it's "blank."
>
> If I'm way off in my questions, please forgive. As pointed out elsewhere,
> there aren't many books for this that I've seen, but if needed, please
> feel
> free to toss me somewhere that I can get the basics. I've read through
> the
> MSDN "Bringing Up a Board Support Package", but are there other resources
> for
> this?
>
> Thanks in advance! This space is great, and I've learned so much from
> your
> help!