Re: Error:Image is too large for current RAM and RAMIMAGE settings by foolblah
foolblah
Thu May 01 13:18:00 PDT 2008
Ming,
Do not confuse the usage of AUTOSIZE. If AUTOSIZE is set to 1 this allows
the unused RAM allocated in config.bin for the ROM to be utilized for system
RAM.
The RAMIMAGE setting in config.bib still needs to be defined large enough to
handle the base ROM image.
For instance, I have 32 MB set aside for the ROM image for a debug build.
My debug nk.bin is about 20 MB, and with AUTOSIZE=1 the other 12ish MB will
be allocated for system RAM rather than having it go to waste.
"Ming Wang" wrote:
> On May 1, 7:20 am, FoolBlah <foolb...@discussions.microsoft.com>
> wrote:
> > How much memory do you have to work with?
> >
> > Here is what I do to dynamically adjust the allocation size between retail
> > and debug builds. Obviously this needs to fit with the rest of your
> > config.bib MEMORY configuration.
> >
> > IF WINCEDEBUG == debug
> > NK 81021000 02000000 RAMIMAGE
> > RAM 83021000 04FDF000 RAM
> > ENDIF
> >
> > IF WINCEDEBUG == retail
> > NK 81021000 01200000 RAMIMAGE
> > RAM 82221000 05DDF000 RAM
> > ENDIF
> >
> > "Bruce Eitman [eMVP]" wrote:
> > > Or increase the size that you allocated for the NK in your config.bib. You
> > > seem to be aware of that, but you didn't share your config.bib so it is hard
> > > to make recommendations.
> >
> > > If this is a debug build, you may also switch to a retail build which is
> > > smaller.
> >
> > > --
> > > Bruce Eitman (eMVP)
> > > Senior Engineer
> > > Bruce.Eitman AT EuroTech DOT com
> >
> > > EuroTech Inc.
> > >www.EuroTech.com
> >
> > > "Dean Ramsier" <ramsiernos...@nospam.com> wrote in message
> > >news:edSaf84qIHA.5096@TK2MSFTNGP02.phx.gbl...
> > > > Your image is too big. Remove components you don't need from your OS
> > > > design (the catalog), and rebuild.
> >
> > > > --
> > > > Dean Ramsier - eMVP
> > > > BSQUARE Corporation
> >
> > > > "ByGalaxy" <ByGal...@discussions.microsoft.com> wrote in message
> > > >news:3DD627AC-914F-4CB7-AB1C-D0A555789F7F@microsoft.com...
> > > >> Hi;
> > > >> i'm here again with this problem.
> > > >> Windows Embedded CE 6.0 and Visual Studio 2005 using..
> >
> > > >> Warning: Unable to do imports from ppp.dll to RSAENH.dll - will late bind
> > > >> Warning: Unable to do imports from ppp.dll to ntlmssp.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from schannel.dll to RSAENH.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from k.schannel.dll to RSAENH.dll - will
> > > >> late
> > > >> bind
> > > >> Warning: Unable to do imports from ipsec.dll to RSAENH.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from ipsecsvc.dll to RSAENH.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from eapol.dll to RSAENH.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from eapchap.dll to RSAENH.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from crypt32.dll to RSAENH.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from k.crypt32.dll to RSAENH.dll - will
> > > >> late
> > > >> bind
> > > >> Warning: Unable to do imports from cryptdll.dll to RSAENH.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from k.cryptdll.dll to RSAENH.dll - will
> > > >> late
> > > >> bind
> > > >> Warning: Unable to do imports from credssp.dll to RSAENH.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from k.credssp.dll to RSAENH.dll - will
> > > >> late
> > > >> bind
> > > >> Warning: Unable to do imports from k.oleaut32.dll to k.ole32 - will late
> > > >> bind
> > > >> Warning: Unable to do imports from mstscax.dll to CREDUI.dll - will late
> > > >> bind
> > > >> Warning: Unable to do imports from cetsc.exe to CREDUI.dll - will late
> > > >> bind
> >
> > > >> Pass 2...
> >
> > > >> RAM AutoSize: RAM Start=83811000 RAM Size=fe3ef000
> > > >> Error: Image is too large for current RAM and RAMIMAGE settings
> > > >> The default end address of RAM was exceeded.
> > > >> You may try setting the environment variable IMGRAM64=1 (or equivalent)
> > > >> if
> > > >> supported for this platform.
> > > >> Fatal error hit, exiting...
> > > >> makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).
> > > >> makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).
> >
> > > >> BLDDEMO: VegaCE build complete.
> >
> > > >> VegaCE - 4 error(s), 21 warning(s)
> > > >> ========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped
> > > >> ==========
> >
> > > >> C:\WINCE600\PLATFORM\VIAMARK\CESYSGEN\files\config.bib
> >
> > > >> how to repair config.bib ??
> >
> > > >> No speak English...Sorry :(
> >
> > > >> Please Help me!!
>
> You can dynamically adjust the amount of memory allocated to the OS
> Image by using the following flag:
>
> AUTOSIZE=ON
>
> Regards,
> Ming Wang
>