Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 06 May 2004 12:04 PM by  mikee@logicpd.com
Problem Building CE Image
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
greg.iva@comcast.net
New Member
New Member
Posts:


--
05 May 2004 05:33 PM
    Any time I try to build an image larger than the tiny kernel in Platform Builder I get an error stating that the "Ram start overlaps the rom binary".

    Writing C:\WINCE420\PUBLIC\Test5\RelDir\LOCE_A~2\NK.bin
    Table of contents 815ef0d0 000017a8 ( 6056)
    Writing ROM signature and TOC pointer at 800e0040
    Kernel data copy section 80e71d0c 00000040 ( 64)
    ROM Header 815ef07c 00000054 ( 84)
    First DLL code Address: 028c0000
    Last DLL code Address: 04000000
    First DLL Address: 01ec01ec
    Last DLL Address: 02000000
    Physical Start Address: 800e0000
    Physical End Address: 815f0878
    Start RAM: 81000000
    Start of free RAM: 8103a000
    End of RAM: 81c00000
    Number of Modules: 114
    Number of Copy Sections: 4
    Copy Section Offset: 80e71d0c
    FileSys 4K Chunks/Mbyte: 128 <2Mbyte 128 2-4Mbyte 0 4-6Mbyte 0 >6Mbyte
    CPU Type: 01c2h
    Extensions Pointer: 800e16b0
    Total ROM size: 01510878 ( 22087800)
    [color=red:1zu6421d]Error: Ram start overlaps rom binary
    Rom end : 0x815f0878
    Ram start: 0x8103a000
    NK
    physfirst 800e0000
    physlast 815f0878
    ulRAMFree 8103a000

    I've tried removing features from the image, but it hasn't been enough. Is there any way to push the ram out farther?
    Anonymous
    Posts:


    --
    06 May 2004 10:20 AM
    Have you successfully built a CE Image before?

    Aaron Stewart
    Technical Support Engineer
    Loigc Product Development
    Anonymous
    Posts:


    --
    06 May 2004 10:22 AM
    Have you successfully built a CE Image before?

    Aaron Stewart
    Technical Support Engineer
    Loigc Product Development
    greg.iva@comcast.net
    New Member
    New Member
    Posts:


    --
    06 May 2004 10:56 AM
    Yes, I can build the tiny kernel as well as the web server, and I have no problem booting the demo image you provided. However when I try to build something like the mobile handheld, or a custom image, I get the error message.
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    06 May 2004 12:04 PM
    IVA,

    Your image is huge!

    From your output, you are building an image that is 21 MBytes in size. This won't fit into RAM. Although the kits have 32 MBytes of RAM, the operating system needs a good chunk of that to implement heaps, stacks, etc. Therefore, not all 32 MBytes are available to execute from.

    Basically, you have a few choices:

    1) Build a retail image instead of a debug image. At least, I'm operating under the assumption that an image of that size is a debug build. Making it a retail build will cut it in half (at least).

    2) Build your image to run from Flash instead of RAM. To do this, set the environment variable "IMGFLASH" in the batch file \Wince420\Platform\LoCE_A400_xxx_xxx\LoCE_A400_xxx_xxx.bat to one and completely rebuild your platform.

    3) Contact Logic support and they can help you generate a multiple XIP image which can take advantage of the segmented 64 Mbytes of SDRAM that may exist on your kit.

    Best regards,
    --mikee
    You are not authorized to post a reply.