Re: Booting on a WinCE 6.0 on an ARM9 SOC based device
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Wed, 21 Mar 2007 17:33:33 -0400
Uboot could work, however keep in mind some of the dependencies...
- When you launch CE from the loader, you must do it with the MMU off. I
don't know how uboot runs
- Some BSPs pass a global data structure to the OS from the loader, often
with parameters indicating the kitl transport etc. You may need to account
for this
- You are going to want a kitl implementation. In your case, that probably
means serial, unless you have a USB function port and can get that working.
Once you get the serial transport working, you can also use it for
downloading, obviating your need for uboot.
Make sure you have a means of jtagging your device if you ever plan to flash
it. You'll probably need it. In general, don't expect this to be a simple
task if you have no CE experience. Especially if you're trying to make
uboot work as well...
--
Dean Ramsier - eMVP
BSQUARE Corporation
"Amit M" <Amit M@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7907C332-A4FF-470F-A546-CB24D6527587@xxxxxxxxxxxxxxxx
Hi,
I have a terminal device on which I want to explore migration to WinCE
6.0.
The device runs on a Cirrus Logic EP9307 integrated SOC with 8M flash and
32M
DRAM -- does not have an Ethernet interface. It currently runs ucLinux and
boots through u-boot. Using the u-boot shell, I can download image files
over
serial.
I have a WinCE 6.0 BSP from Cirrus for the EDB9307 dev board - EDB9307
also
runs the EP9307 SOC. As I understand, I will need to customize this BSP
for
the custom EP9307-based board on my device.
I am very new to this and not sure of the complexity involved in getting
WinCE up and running on this platform so will be working somewhat in the
dark. My questions:
* Is it possible to boot WinCE without using ethernet / eboot? Can I boot
a
WinCE image using the current boot loader - u-boot?
* What is the general strategy for customizing the BSP for my board? From
the look of it, the BSP already supports a lot of the integrated
peripherals
- LCD controller, keyboard controller etc. What are the problem areas I
should anticipate? Any pointers on this would help a lot.
I haven't got much help from the Cirrus communities so far. Really looking
forward to some help / direction on this - pls let me know if more info is
needed to help understand the problem better.
Thanks,
Amit
.
- Prev by Date: Re: interrupt- stream driver- wince 6
- Next by Date: Re: Getting error code 6 when creating a dialog
- Previous by thread: Re: Booting on a WinCE 6.0 on an ARM9 SOC based device
- Next by thread: PXA270 and WinCE source code exemple ?
- Index(es):
Relevant Pages
|
