[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC] extensions to the -m memory option

From: Liviu Ionescu
Subject: Re: [Qemu-devel] [RFC] extensions to the -m memory option
Date: Fri, 29 May 2015 23:13:30 +0300

> On 29 May 2015, at 22:33, Paolo Bonzini <address@hidden> wrote:
> On 29/05/2015 21:27, Liviu Ionescu wrote:
>>> If the flash is persistent, it should be tied to either "-pflash"
>>> (NOR) or "-mtd" (NAND).  Just using a different image then
>>> results in resizing the flash.
>> I did not try the resizing mechanism, but I don't think it is
>> appropriate, one of my use cases is to start QEMU as GDB server,
>> without any image specified on the command line, and in this case the
>> flash size needs to be known in advance, I doubt the it can resize
>> when the image is loaded by the GDB client.
> You can use -drive if=mtd,snapshot=on,file=null-co://,file.size=128K to
> start QEMU with a zero 128K NOR flash.

did someone else have a faint thought that:

- the above syntax might be a bit too complicated or non intuitive?

- specifying NOR flash might not be appropriate for defining the internal flash 
for all Cortex-M MCUs?

I know that this is mainly a linux shop, using large application processors, 
but perhaps we can find a simpler way to accommodate the slightly different MCU 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]