Re: More about ROMOFFSET usage.
From: Dean Ramsier (ramsiernospam_at_nospam.com)
Date: 07/08/04
- Next message: Dean Ramsier: "Re: Development time for Windows CE BSP on ARM platform"
- Previous message: SnowMan: "More about ROMOFFSET usage."
- In reply to: SnowMan: "More about ROMOFFSET usage."
- Next in thread: SnowMan: "Re: More about ROMOFFSET usage."
- Reply: SnowMan: "Re: More about ROMOFFSET usage."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Jul 2004 09:50:22 -0400
Whoever is loading the image - the bootloader. It can't run until it's been
placed in (copied to) the location it needs to run from. Therefore, the
image itself can't be responsible for the copy.
Typically, ROMOFFSET is used as a convenience to allow the image to be
stored in flash. The bootloader then copies the the image in flash to RAM,
and jumps there.
-- Dean Ramsier - eMVP "SnowMan" <SnowMan@discussions.microsoft.com> wrote in message news:7F8626CE-788D-4E14-ABE1-3FC893A0B862@microsoft.com... > Hi All, > > ROMOFFSET is supposed to be used to generate BIN file records for placing the > image in memory at an address different from where it will execute from. Can anybody confirm who should take the responsibility to move the image from where it is stored to where it will run from? Boot loader, image itself, or OS loader? > > Thanks, > SN
- Next message: Dean Ramsier: "Re: Development time for Windows CE BSP on ARM platform"
- Previous message: SnowMan: "More about ROMOFFSET usage."
- In reply to: SnowMan: "More about ROMOFFSET usage."
- Next in thread: SnowMan: "Re: More about ROMOFFSET usage."
- Reply: SnowMan: "Re: More about ROMOFFSET usage."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading