> On 29 May 2015, at 14:08, Paolo Bonzini <pbonz...@redhat.com> wrote: > > > > On 29/05/2015 00:11, Liviu Ionescu wrote: >> for more flexibility, in the new Cortex-M implementation I'm working on, I >> can overwrite the vendor defined MCU internal SRAM size by using: >> >> -m sizeK >> >> I'm trying to find a way to also overwrite the internal flash size and the >> first idea I had was to extend the "-m" command like: >> >> -m sizeK,flash=sizeK >> >> would this be ok? >> >> for more readability I would prefer something like: >> >> --memory ram=sizeK,flash=sizeK >> >> any other suggestions? > > 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. regards, Liviu
