Hi Jehudi, Maybe Greg can explain better, but I think CONFIG_FLASH_SIZE/START/END and CONFIG_RAM_SIZE/START/END were used in the past when the MCU were very simple.
Over the time things became more complex, there are many possible RAM configurations/layouts (OCRAM, etc, etc) that these config became obsolete. So, instead of trying to apply it again, I suggest you analyze why it became obsolete and implement something different. Maybe a defined area in the linker script. The solution must accommodate both scenarios: users who want or need to use a Bootloader, and users who neither need nor want to use one. BR, Alan On Tue, Aug 18, 2026 at 1:28 PM Laczen JMS <[email protected]> wrote: > Hi, > > NuttX has generic kconfig parameters for FLASH_(V)START and FLASH_SIZE. > > Many of the board linker files are not using these parameters to > configure the location of > the image on flash (default is 0x0). > > I would like to use these parameters to configure NuttX when used in > combination with a > bootloader. Of course I don't want to break existing defconfigs. > > My idea was to use the value of FLASH_SIZE as an indicator for the > linker files to switch > from the default settings to the configuration parameters. As long as > FLASH_SIZE=0 the > default setup in the linker script is used, when FLASH_SIZE != 0 the > configured parameters > are put into use (this of course after the linker script is changed). > > Do you agree with such an approach? Or is there a better alternative? > > Kind regards, > > Jehudi >
