Bootloader

From: Tweeeek (Tweeeek_at_nospam.com)
Date: 08/26/04


Date: Thu, 26 Aug 2004 16:32:19 +0100

Hi
We have been running wince.net 4.2 on sa1110 based hardware. The
bootloader we use has been ported from wince300 when it used to exist in
the sa11x0bd bsp supplied by Intel.

The bootloader runs without problems. We are now moving to Xscale and
again are now porting our bootloader across (we want to port this across
because it has had lots of features added to it, and we understand the
code well).

My question is that we do not use BLCOMMON, or any bootloader code
supplied by the new XScale BSP. We are purely porting our bootloader
across to Xscale. Can I do this??? do we have to use BLCOMMON??? Is
there anything that we should be weary of, or watch out for.

Any help would be appreciated

Regards



Relevant Pages

  • Re: bootloader-bios interaction
    ... >> location where the bootloader code is executed. ... >> running the processor is configured in real mode. ... >> code is executing, will the processor switch to protected mode?(i am ...
    (comp.os.linux.embedded)
  • Re: WinCE 5.0 Problems at BootUp x86 HDD
    ... Your Bootloader obviously has support for Ethernet booloading ("Microsoft ... Controller that KITL will use, ... Bootloader code with your NK.BIN code: if you disable KITL in your image ...
    (microsoft.public.windowsce.platbuilder)
  • Bootloader wince.net 4.2
    ... My first bootloader was developed when I was working on wince300. ... you then had to create an EBOOT shortcut with a command line. ... We are moving to Xscale, obviously he bootloader will have to be modified to ...
    (microsoft.public.windowsce.platbuilder)
  • Re: ST ARMs
    ... But does exist a 'general' STFamily bootloader (i mean like the ... The bootloader code depends on: ... of network, and if you are lucky something for your specific hardware. ...
    (comp.sys.arm)
  • Re: atmega32 RIP
    ... you could still update firmware with the bootloader, ... Found no explanation for this so far. ... "Corruption" was probably in the bootloader code, ...
    (sci.electronics.design)