qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Changho Choi <1897680@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1897680] Re: memory address over 0x2000_7ffc is not accessible in mps2-an505
Date: Tue, 29 Sep 2020 10:10:39 -0000	[thread overview]
Message-ID: <CADiewghimshot=tKNJ0QvQ+m5izOy5X5k76Qn=eiY--ZmkpAiA@mail.gmail.com> (raw)
In-Reply-To: 160137117306.23397.9822576099583034440.malone@gac.canonical.com

Thank you for all your kind answers and suggestions.
I also have confirmed that the memory address over 0x2000_8000 is not
accessible in the real board.

Regards,

Changho Choi

2020년 9월 29일 (화) 오후 6:25, Peter Maydell <1897680@bugs.launchpad.net>님이
작성:

> (If you were just interested in having a large area of contiguous RAM,
> the "PSRAM" is the largest lump on this board: it's 16MB starting at
> 0x8000_0000.)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1897680
>
> Title:
>   memory address over 0x2000_7ffc is not accessible in mps2-an505
>
> Status in QEMU:
>   New
>
> Bug description:
>   I currently run qemu with the following options
>   `qemu-system-aarch64 -machine mps2-an505 -cpu cortex-m33 -m 16`
>
>   For some reason, memory address over 0x2000_7ffc is not accessible.
>   It can be tested in gdb as follow.
>
>   (gdb) x/x 0x20007ffc
>   0x20007ffc:   0x00000000
>   (gdb) x/x 0x20007ffd
>   0x20007ffd:   Cannot access memory at address 0x20007ffd
>   (gdb) x/x 0x20008000
>   0x20008000:   Cannot access memory at address 0x20008000
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1897680/+subscriptions
>

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1897680

Title:
  memory address over 0x2000_7ffc is not accessible in mps2-an505

Status in QEMU:
  New

Bug description:
  I currently run qemu with the following options
  `qemu-system-aarch64 -machine mps2-an505 -cpu cortex-m33 -m 16`

  For some reason, memory address over 0x2000_7ffc is not accessible.
  It can be tested in gdb as follow.

  (gdb) x/x 0x20007ffc
  0x20007ffc:	0x00000000
  (gdb) x/x 0x20007ffd
  0x20007ffd:	Cannot access memory at address 0x20007ffd
  (gdb) x/x 0x20008000
  0x20008000:	Cannot access memory at address 0x20008000

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1897680/+subscriptions


  reply	other threads:[~2020-09-29 10:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  6:57 [Bug 1897680] [NEW] memory address over 0x2000_7ffc is not accessible in mps2-an505 Changho Choi
2020-09-29  9:12 ` [Bug 1897680] " Peter Maydell
2020-09-29  9:14 ` Peter Maydell
2020-09-29  9:19 ` Peter Maydell
2020-09-29 10:10   ` Changho Choi [this message]
2020-09-29  9:42 ` [Bug 1897680] [NEW] " Philippe Mathieu-Daudé
2020-09-29  9:42   ` Philippe Mathieu-Daudé
2020-09-29 10:46 ` [Bug 1897680] " Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADiewghimshot=tKNJ0QvQ+m5izOy5X5k76Qn=eiY--ZmkpAiA@mail.gmail.com' \
    --to=1897680@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).