This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Memorymapping and MMU (mem-map in referencemanual and in eCos not the same!!)


Hi!
As you might have understood by now, I am working with a mediaEngine from
Brighstar.
The closest porting I could find was the nanoEngine, which is on RedHats
list of supported
hardware.
A question that arises was that when I checked the memorymappings used for
eCos (in
the Config tool,-> memory layout),
I found that the mapping represented there was NOT the same as the one given
in the referencemanual
of nanoEngine (table 3-1 in http://www.brightstareng.com/pub/nanoman.pdf)

So I thought that this could be because of the MMU settings, which means
that
the memory layout in Config tool shows the modified memory layout whereas
the
referencemanuals shows the physical memoryadressing.
So my question is: 
* How does one manually set and edit the mapping that the MMU uses? (Since I
use media, not nanoEngine)
* What happens if I DON'T install the MMU?(By unchecking the "install MMU
tables in Config tool, eCos HAL -> Platform indep HAL options)
  How does eCos then find the startvectors etc
* What does the alternative static MMU tables do?


The reason for me wanting to do this, is that the example two threads
doesn't work, but all
the other examples do. (the mail from David Karlberg. We work on the same
thesis project!)
So I thought that maybe it's during the initiation of the threads that
something goes wrong (it tries to 
access memory that isn't there or something..)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]