Changing the config.bib file

Tech-Archive recommends: Speed Up your PC by fixing your registry

/*sorry for bringing this topic on top, but i thought it should
normally come on top once a new message is posted :-(, and i dearly
need an answer. You can straight to to end of discussion to get a hold
of where we are now. Thanks everybody*/


Hi Everybody,
I need to know how to address memory less than 1Mb
in ARM based systems in g_oalAddressTable, as I think that memory is
addressed in MB's for processors apart from x86. As a matter of fact,
I have 32Kb of internal memory which I want to use it. Can anybody
guide me how to implement in this case?

I have kept it like this:
DCD 0x8D000000, 0x01008000, 1 ; 32KB
internal SRAM

As its shown above, its written as 1, must be something to signify
that its 32Kb not 1Mb. Please revert back if anybody knows how to go
about this.

Thanks and Regards,
zix


R. de Gravelaine
Hi,

g_oalAddressTable granularity is the megabyte. You can't go bellow.
However, this should not be an issue if you have enough virtual space
to
map all your memory and peripherals (max is 512 MB.)
Using the example bellow, you will be able to access the physical
memory
between 0x01008000 and 0x0100FFFF using virtual addresses ranging
from
0x8D000000 to 0x8D007FFF. It is up to you not to go beyond this limit.

HTH
Remi

zix
Hi Remi,
thanks for the reply. Let me explain what I am trying for.
We have a running bsp+application. Now, I am trying to use the 32Kb
internal sram. So, I have modified the g_oalAddressTable and
config.bib file.

The changes are below:
part of g_oalAddressTable----------------------added the entry for
32Kb part

DCD 0x80000000, 0x10000000, 16 ; 16MB CS4
flash
DCD 0x84000000, 0x44000000, 64 ; 64MB
CSD0 SDRAM
DCD 0x88000000, 0x01008000, 1 ; 32KB
internal SRAM
DCD 0x88100000, 0x40000000, 64 ; 64MB
CSD0 SDRAM
DCD 0x90000000, 0x03000000, 16 ; 16MB
CS0 FPGA(ASIC)
DCD 0x93100000, 0x05000000, 2 ; 2MB
CS3

Now, the config.bib file---------------------------
BLDR 84000000 00100000 RESERVED
EDBG 84100000 00020000 RESERVED
NK 84120000 02800000 RAMIMAGE
RAM 86920000 015C0000 RAM
MLBMEM 87EE0000 00004000 RESERVED
AUDIO 87EE4000 00004000 RESERVED
ASTLOG 87EE8000 00100000 RESERVED
GDISUB 87FE8000 00020000 RESERVED
VIDEO 88100000 04000000 RESERVED
PERI 9AE00000 00200000 RESERVED

Over here, I have increased the RAM entry by 32Kb,and all the
subsequent entries by 32Kb, except PERI 9AE00000.

When I build the bsp and load with application, it hangs, figured that
it cant start off properly. Do I need to see other things also? Can
you please have a look and revert back if possible?

Thanks and Regards,
zix

Dean Ramsier
A couple things:

1) The addresses in the OEM address table (physical and virtual)
should be
1MB aligned. Your 32KB address is not.
2) There is no need to put 32KB SRAM into the OEM address table unless
you
need to access it from the kernel. Otherwise, just map it in using
MmMapIoSpace or related API
3) If you do need to put 32K SRAM into oem address table, it would be
better
to pick an unused location. Don't shift everything else around.
4) What is your debug output? Do a debug build to see where you are
hanging.

--
Dean Ramsier - eMVP
BSQUARE Corporation

zix
1) The addresses in the OEM address table (physical and virtual) should be
1MB aligned. Your 32KB address is not.
2) There is no need to put 32KB SRAM into the OEM address table unless you
need to access it from the kernel. Otherwise, just map it in using
MmMapIoSpace or related API
3) If you do need to put 32K SRAM into oem address table, it would be better
to pick an unused location. Don't shift everything else around.
4) What is your debug output? Do a debug build to see where you are
hanging.

--
Dean Ramsier - eMVP
BSQUARE Corporation

Hi Dean, thanx for the answer. I guess to fix (1), I have to start
from (3), as I am not going via (2). For performance issues, I am
trying to use this 32Kb memory, so I must put it under RAMIMAGE,
rather than MmMapIoSpace as I dont want to change any thing else in
bsp. Now, as I can have only 1 Ramimage section, how can I proceed
without shifting all the other ones around, if I have to push
something in the middle? can I place this far after every section and
still put it under RAMIMAGE section? The debug build is quite big for
the memory :-(

Thanks n Regards,
zix
.

Relevant Pages

  • Re: Changing the config.bib file
    ... You are saying you are going through all this trouble to add an extra 32 *KB* to the memory available to CE for normal application use? ... zix wrote: ... internal SRAM ... Do a debug build to see where you are ...
    (microsoft.public.windowsce.embedded)
  • Re: less than 1 Mb in g_oalAddressTable
    ... The addresses in the OEM address table should be ... What is your debug output? ... trying to use this 32Kb memory, so I must put it under RAMIMAGE, ...
    (microsoft.public.windowsce.embedded)
  • [UNIX] PHP gd Library imageRotate() Function Information Leak Vulnerability
    ... PHP gd Library imageRotateFunction Information Leak Vulnerability ... Information leak vulnerabilities allow access to e.g. the Apache memory ... gdImagePtr gdImageRotate (gdImagePtr src, double dAngle, ... if($debug) ...
    (Securiteam)
  • Re: Problem only in release version!
    ... Debug version may still have the problem, but the stack space is better ... memory or a buffer on the stack is not always caught. ... > Just to affirm Jochen's point, the Debug version initializes most ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Epia Mini-ITX ce installation
    ... run your apllication on the CE simulator, or maybe even when you try to ... Normally the Emulator emulates a device with 32MB ram memory. ... A debug CE image is roughly about twice the size of a retail image. ...
    (microsoft.public.windowsce.embedded)