Re: How Physical Memory Mapping / Allocation works

From	Gunther Mannigel <newsgroups@mannigel.net>
Newsgroups	comp.arch.embedded
Subject	Re: How Physical Memory Mapping / Allocation works
Date	2018-03-03 22:54 +0100
Message-ID	<fg0jt5FhporU1@mid.individual.net> (permalink)
References	<73de56bf-5a75-42a2-a9be-651839c209e0@googlegroups.com> <p732lu$7cf$1@dont-email.me> <556136b3-264a-4965-a4ca-fd9a0ffc872f@googlegroups.com> <p73moj$lu8$1@dont-email.me> <b92550f1-ea4f-497b-be61-7f4d5137d078@googlegroups.com>

Show all headers | View raw

Am 27.02.2018 um 19:11 schrieb Ilias Abrams:
> You are absolutely right. Lets start again, I am a student and I have a project. I want to work on ARM architecture and not on x86. I am working some C examples on RPI2 and 3 and also I have a microcontroller Tiva C TM4C123G Launchpad. 
> I want to right a baremetal software that can save registers values into the memory address like stack lets say and print those values from memory to screen. But I want to use C and assembly (maybe inline assembly) and I want to use physical addresses (If its not possible to use directly the physical addresses maybe I can achieve a 1-1 mapping logical to physical) 

Hi Ilias,

with a Tiva, you can use the Ressource Explorer to open examples which
are bare metal. Start there. :-)

sincerely
Gunther

Thread

How Physical Memory Mapping / Allocation works Ilias Abrams <iliasabrams@gmail.com> - 2018-02-26 14:07 -0800
  Re: How Physical Memory Mapping / Allocation works Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2018-02-26 21:26 -0500
  Re: How Physical Memory Mapping / Allocation works David Brown <david.brown@hesbynett.no> - 2018-02-27 08:51 +0100
    Re: How Physical Memory Mapping / Allocation works Ilias Abrams <iliasabrams@gmail.com> - 2018-02-27 02:34 -0800
      Re: How Physical Memory Mapping / Allocation works David Brown <david.brown@hesbynett.no> - 2018-02-27 14:34 +0100
        Re: How Physical Memory Mapping / Allocation works Ilias Abrams <iliasabrams@gmail.com> - 2018-02-27 10:11 -0800
          Re: How Physical Memory Mapping / Allocation works Jack <jack4747@gmail.com> - 2018-02-27 23:31 -0800
            Re: How Physical Memory Mapping / Allocation works David Brown <david.brown@hesbynett.no> - 2018-02-28 09:51 +0100
              Re: How Physical Memory Mapping / Allocation works Paul <paul@pcserviceselectronics.co.uk> - 2018-03-01 14:54 +0000
          Re: How Physical Memory Mapping / Allocation works Gunther Mannigel <newsgroups@mannigel.net> - 2018-03-03 22:54 +0100
    Re: How Physical Memory Mapping / Allocation works Ilias Abrams <iliasabrams@gmail.com> - 2018-02-27 02:36 -0800
      Re: How Physical Memory Mapping / Allocation works Mel Wilson <mwilson@the-wire.com> - 2018-02-27 16:51 +0000
      Re: How Physical Memory Mapping / Allocation works antispam@math.uni.wroc.pl - 2018-03-10 14:05 +0000
  Re: How Physical Memory Mapping / Allocation works Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2018-02-27 10:14 +0200

csiph-web