On Wed, Feb 3, 2016 at 10:34 AM, Peter Maydell <peter.mayd...@linaro.org> wrote: > On 3 February 2016 at 13:00, Aurelio Remonda > <aurelio.remo...@tallertechnologies.com> wrote: >> Hello, i was trying to understand how does the sram and flash size >> works on lm3s6965evb, i found a hardcoded 0x00ff007f as dc0 value and >> how flash_size and sram_size are calculated based on that hexadecimal. >> I mean this: >> >> flash_size = (((board->dc0 & 0xffff) + 1) << 1) * 1024; >> sram_size = ((board->dc0 >> 18) + 1) * 1024; >> On stellaris.c >> >> When i use the -m [size] flag while running qemu how does the flag >> affect does flash_size and sram_size values? Or it doesn't? Where can >> i see that the memory has indeed change? > > This board model ignores -m. We just implement a model of this particular > bit of hardware, which has a fixed amount of RAM in it.
Thanks for the quick answer, do you think it is worth to make the m flag work for this model? Can you give me a hint on where to look?(another board that use it) so i can add this feature for this model. Thanks! -- Aurelio Remonda Software Engineer San Lorenzo 47, 3rd Floor, Office 5 Córdoba, Argentina Phone: +54-351-4217888 / 4218211
