Re: Memory configuration of WinCE Image

Hi John,
Thankyou very much. As you suggested I tired to download image into RAM.
Actually I am not sure how to configure my PB to dowload image in RAM? I
tried to remove the tick mark of "Write Run-time image to FLash Memory" in
build options of Platform settings. But it generated errors of which I have
no clue.

Errors are :
________________________________________________________
total space 386788 in 238 ranges
Writing
C:\WINCE500\PBWorkspaces\Mainstone\RelDir\MAINSTONEII_ARMV4I_Debug\NK.bin
Table of contents 9dfb1078 000024f0 ( 9456)
Writing ROM signature and TOC pointer at 9aa80040
Kernel data copy section 9d4f8d44 00000080 ( 128)
Error: Too much data space used by DLL's in MODULES section
Current usage = 28544k, Maximum usage = 26624k.
Reduce DLL usage or move some DLL's into the FILES section.
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).
Volume in drive C has no label.
Volume Serial Number is 1818-69A7
Directory of
C:\WINCE500\PBWorkspaces\Mainstone\RelDir\MAINSTONEII_ARMV4I_Debug
21.08.2006 17:27 55.385.099 NK.bin
1 File(s) 55.385.099 bytes
0 Dir(s) 102.808.096.768 bytes free
BLDDEMO: Mainstone build complete.

Mainstone - 3 error(s), 227 warning(s)
__________________________________________________________

As the error is pointing of lack of memory, I have configured memory in my
config.bib as :
________________________________________________________
IF IMGFLASH!

; Name Start Size Type
; ------- -------- -------- ----
RSVD 80000000 000FF000 RESERVED
ARGS 800FF000 00001000 RESERVED
NK 80100000 03000000 RAMIMAGE
RAM 83100000 00F00000 RAM

ENDIF

IF IMGFLASH

; Name Start Size Type
; ------- -------- -------- ----
RSVD 80000000 000FF000 RESERVED
ARGS 800FF000 00001000 RESERVED
NK 9AA80000 04000000 RAMIMAGE
RAM 80100000 03F00000 RAM
ENDIF

CONFIG

IF IMGFLASH!
AUTOSIZE=ON
;ELSE
; ROMOFFSET=20000000
ENDIF
_________________________________________________________

oemaddrtab_cfg.inc has been changed as follows:

DCD 0x80000000, 0xA0000000, 64 ; MAINSTONEII: SDRAM (64MB).
DCD 0x84000000, 0x5C000000, 1 ; BULVERDE: Internal SRAM (64KB bank
0).
DCD 0x84100000, 0x58000000, 1 ; BULVERDE: Internal memory PM
registers.
DCD 0x84200000, 0x4C000000, 1 ; BULVERDE: USB host controller.
DCD 0x84300000, 0x48000000, 1 ; BULVERDE: Memory controller.
DCD 0x84400000, 0x44000000, 1 ; BULVERDE: LCD controller.
DCD 0x84500000, 0x40000000, 32 ; BULVERDE: Memory-mapped registers
(peripherals).
DCD 0x86500000, 0x3C000000, 64 ; BULVERDE: PCMCIA S1 common memory
space.
DCD 0x8A500000, 0x38000000, 64 ; BULVERDE: PCMCIA S1 attribute
memory space.
DCD 0x8E500000, 0x30000000, 32 ; BULVERDE: PCMCIA S1 I/O space.
DCD 0x90500000, 0x2C000000, 64 ; BULVERDE: PCMCIA S0 common memory
space.
DCD 0x94500000, 0x28000000, 64 ; BULVERDE: PCMCIA S0 attribute
memory space.
DCD 0x98500000, 0x20000000, 32 ; BULVERDE: PCMCIA S0 I/O space.
DCD 0x9A500000, 0xE0000000, 1 ; MAINSTONEII: Zero-bank (in
reserved slot - no physical memory required).
DCD 0x9A600000, 0x14000000, 1 ; MAINSTONEII: nCS5: eXpansion board
header.
DCD 0x9A700000, 0x10000000, 1 ; MAINSTONEII: nCS4: SMSC 91C111
Ethernet controller.
DCD 0x9A800000, 0x0A000000, 1 ; MAINSTONEII: nCS2 (upper half):
2MB SRAM.
DCD 0x9A900000, 0x08000000, 1 ; MAINSTONEII: nCS2 (lower half):
Board registers (FPGA).
DCD 0x9AA00000, 0x04000000, 64 ; MAINSTONEII: nCS1: Secondary flash
(32MB).
; DCD 0x9B800000, 0x00000000, 50 ; MAINSTONEII: nCS0: Boot Flash
(32MB).
DCD 0x9EA00000, 0x50000000, 1 ; BULVERDE: Camera peripheral
interface.
DCD 0x00000000, 0x00000000, 0 ; end of table
_________________________________________________________

I have also changed maisntoneii.inc and mainstoneii.h files also as follows
for the new boot flash address:

// MainstoneII: (on PDC): nCS0: Boot FLASH (32MB)
#define MAINSTONEII_BASE_PA_BOOT_FLASH 0x04000000
#define MAINSTONEII_SIZE_BOOT_FLASH 0x04000000

// MainstoneII: nCS1: Secondary FLASH (32MB)
#define MAINSTONEII_BASE_PA_SECONDARY_FLASH 0x04000000

// MainstoneII: nCS2: Board-Level Registers (FPGA)
#define MAINSTONEII_BASE_REG_PA_FPGA 0x08000000

// MainstoneII: nCS5: eXpansion Board Header
#define MAINSTONEII_BASE_PA_SDRAM 0xA0000000
#define MAINSTONEII_SIZE_SDRAM 0x04000000
_________________________________________________________

Is there anyother file do I need to consider? or I wrongly assigning memory?
I tried to build both with and without including the platform building
setting to write image on flash memory but both giving same error of too much
space used by dll.

Thanks
Sandeep

"John Baik" wrote:

Previous my email is for RAM image.
Since you said you saved image to Flash, here I saw the issue too.
You have 32MB Flash (0x9CA00000 ~ 0x9EA00000).
In your config. bib file, you have 35.6MB Image at 0x9CB80000 .
Yon can't really save image to flash location.
I'd rather download image to RAM to debug something.

You may try this if you still copy image to Flash.
But you also need to change all the code which refers previous Flash
Address.

On OEM Address Table,
DCD 0x9CA00000, 0x08000000, 32 ; MAINSTONEII: nCS1: Secondary
flash (32MB).
DCD 0x9AA00000, 0x00000000, 32 ; MAINSTONEII: nCS0: Boot Flash
(32MB).

On Config.bib,
NK 9AA80000 02500000 RAMIMAGE

Thanks
John Baik


"Sandeep" <Sandeep@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:81DC67F1-BF03-46FB-8809-8158E7E02078@xxxxxxxxxxxxxxxx
Thanks Bruce.

Yeah sorry bootloader hangs. Yeah I think I have enough RAM . Following is
the configuration of OEM address table from oemaddrtab_cfg.inc. I have
tried
to change the configuration of boot flash from 32 Mb to 64 ( as my board
support) but still no success. Do I need to change any other files?
Actually
I am not sure which are the files I need to change to make change in
memory
map.

DCD 0x80000000, 0xA0000000, 64 ; MAINSTONEII: SDRAM (64MB).
DCD 0x84000000, 0x5C000000, 1 ; BULVERDE: Internal SRAM (64KB
bank
0).
DCD 0x84100000, 0x58000000, 1 ; BULVERDE: Internal memory PM
registers.
DCD 0x84200000, 0x4C000000, 1 ; BULVERDE: USB host controller.
DCD 0x84300000, 0x48000000, 1 ; BULVERDE: Memory controller.
DCD 0x84400000, 0x44000000, 1 ; BULVERDE: LCD controller.
DCD 0x84500000, 0x40000000, 32 ; BULVERDE: Memory-mapped
registers
(peripherals).
DCD 0x86500000, 0x3C000000, 64 ; BULVERDE: PCMCIA S1 common
memory
space.
DCD 0x8A500000, 0x38000000, 64 ; BULVERDE: PCMCIA S1 attribute
memory space.
DCD 0x8E500000, 0x30000000, 32 ; BULVERDE: PCMCIA S1 I/O space.
DCD 0x90500000, 0x2C000000, 64 ; BULVERDE: PCMCIA S0 common
memory
space.
DCD 0x94500000, 0x28000000, 64 ; BULVERDE: PCMCIA S0 attribute
memory space.
DCD 0x98500000, 0x20000000, 32 ; BULVERDE: PCMCIA S0 I/O space.
DCD 0x9A500000, 0xE0000000, 1 ; MAINSTONEII: Zero-bank (in
reserved slot - no physical memory required).
DCD 0x9A600000, 0x14000000, 1 ; MAINSTONEII: nCS5: eXpansion
board
header.
DCD 0x9A700000, 0x10000000, 1 ; MAINSTONEII: nCS4: SMSC 91C111
Ethernet controller.
DCD 0x9A800000, 0x0A000000, 1 ; MAINSTONEII: nCS2 (upper half):
2MB SRAM.
DCD 0x9A900000, 0x08000000, 1 ; MAINSTONEII: nCS2 (lower half):
Board registers (FPGA).
DCD 0x9AA00000, 0x08000000, 32 ; MAINSTONEII: nCS1: Secondary
flash
(32MB).
DCD 0x9CA00000, 0x00000000, 32 ; MAINSTONEII: nCS0: Boot Flash
(32MB).
DCD 0x9EA00000, 0x50000000, 1 ; BULVERDE: Camera peripheral
interface.
DCD 0x00000000, 0x00000000, 0 ; end of table

Thanks

SD
"Bruce Eitman [eMVP]" wrote:

Your Hyperterminal hangs? I don't think so, your bootloader hangs.

Do you have enough RAM? Did you configure OEMAddressTable for the RAM
and
flash? Did you update your bootloader?

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Sandeep" <Sandeep@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:49039951-0519-4748-AAB1-E608BAEDB7DF@xxxxxxxxxxxxxxxx
Hi ,

Actually I am very new to WinCE environment so I would greatly
appreciate
if
someone could guide me. I am working on WinCE 5.0. My custom board is
using
PXA270 MainstoneII. As Mainstone II has support for 32 MB ROM but my
image
size in debug mode is 35.6MB. So my hyperterminal gets hanged up in
middle
while downloading image on board.

As my board support 64 MB memory so I want to change the Mainstone II
memory
configuration to 64 MB.

I have tried to increase the memory in config.bib as follows
NK 9CB80000 02500000 RAMIMAGE
but still image gets hanged up. Can anyone suggest me which other files
or
parameters do I need to change ?

Thanks in advance.

Kind Regards,
SD






.

Relevant Pages

  • Re: Steve Jobs demos Macintosh in 1984
    ... Woody wrote: ... Stop annoying the fucking hell out of me, ... For sure not much computer memory had been made in 1948 - but it could ... For sure you got a bit more RAM to use in the Speccy - ...
    (uk.comp.sys.mac)
  • Re: Windows uses 4 GB? Really?
    ... I bought 4 GB of RAM because I thought it would speed up my system a bit. ... Some info that is posted here as reference seems to suggest that it is a Windows issue, but others seem to suggest that it is also a hardware issue. ... "I have install total 4GB memory on my motherboard. ... On a SLI system, since PCI-Ex graphic cards will occupy around 256MB, another 256MB will be occupied after you install a 2nd PCI-Ex graphic card. ...
    (microsoft.public.windowsxp.general)
  • Re: Memory Map Accelent Board
    ... CS1 - Alternate Flash ... > I derived in a great difficulty the following memory map for Accelent. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Memory Map Accelent Board
    ... CS1 - Alternate Flash ... > I derived in a great difficulty the following memory map for Accelent. ...
    (microsoft.public.windowsce.embedded)
  • Re: What File System supports Application XIP
    ... > You won't gain at runtime by using XIP though. ... I thought that when you XIPed from flash, ... directly back to the flash memory address. ... There shouldn't be a RAM ...
    (Linux-Kernel)
Loading