qemu-riscv.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: max <cmax@mailbox.org>, qemu-discuss@nongnu.org
Cc: qemu-riscv <qemu-riscv@nongnu.org>
Subject: Re: riscv virt target write pflash
Date: Mon, 19 Feb 2024 09:19:49 +0100	[thread overview]
Message-ID: <98da32fd-8027-4635-bd12-c5d45fd0b948@linaro.org> (raw)
In-Reply-To: <6f8f1176-90ce-4fa4-9877-816f52478340@mailbox.org>

Cc'ing qemu-riscv mailing list which is more focused.

On 18/2/24 22:32, max wrote:
> I am relatively new to QEMU so I hope that this is the right place to ask:
> 
> I tried starting QEMU with the following command:
> ```
> qemu-system-riscv64 -M virt -drive 
> if=pflash,format=raw,unit=0,file=bios.rom -m 512M -nographic -s -S
> ```
> 
> I am using GDB to debug the `bios.rom` Firmware. At some point in the 
> execution `bios.rom` writes into some global variable (at 0x2000525C) 
> inside the .bss section which is linked to be inside the memory mapped 
> pflash0. But when I step forward with GDB to the exact location where 
> the store instruction (sw) is executed, QEMU prints the following:
> ```
> pflash_write: Unimplemented flash cmd sequence (offset 000000000000525c, 
> wcycle 0x0 cmd 0x0 value 0x1)
> ```
> According to the top of `hw/block/pflash_cfi01.c` Flash writes are 
> supported. I am probably missing something here so it would be nice if 
> someone could point me in the right direction. I would also gladly 
> contribute if there is something missing in the riscv virt target.
> 
> 



           reply	other threads:[~2024-02-19  8:19 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <6f8f1176-90ce-4fa4-9877-816f52478340@mailbox.org>]

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=98da32fd-8027-4635-bd12-c5d45fd0b948@linaro.org \
    --to=philmd@linaro.org \
    --cc=cmax@mailbox.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=qemu-riscv@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 read-only IMAP folder(s) and NNTP newsgroup(s).