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 20 Jul 2004 12:18 PM by  mpinton
debug build too big for RAM-based image
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
mpinton
New Member
New Member
Posts:


--
20 Jul 2004 07:48 AM
    Hi,
    I have an OS image that is currently too large (>0xf00000) in DEBUG mode, so I get complaints during the build that the RAM/ROM boundary is compromised. Can I just go into lha400_10_config_bib.h and adjust the RAM_BUILD_IMAGE_SIZE to be larger, say 0xFF4240? Are there any constants based on the RAM_BUILD_IMAGE_SIZE that are affected?
    TIA,
    /michel
    mpinton
    New Member
    New Member
    Posts:


    --
    20 Jul 2004 12:18 PM
    OK, actually, I don't want to do want I suggested previously; if I increase the NK portion then I have to shrink the RAM portion (in the RAM-based build) and I probably need alot of that volatile memory portion since the NK is so big. My board actually has 64MB of RAM on it - how can I use it all so that I can have a RAM-based debug build that has a NK that is > 15MB (the 0xf00000). I can't cull anything out of the build, it's fine when it's a retail build.

    Thanks,
    /michel
    You are not authorized to post a reply.