On Wed, Feb 10, 2021 at 2:36 PM Gedare Bloom <ged...@rtems.org> wrote:
> > > On Wed, Feb 10, 2021 at 10:57 AM Joel Sherrill <j...@rtems.org> wrote: > >> Hi >> >> The minimum sample is intended to show how to construct the minimum >> footprint RTEMS application. I suspect that with Sebastian's recent work on >> static allocation and reducing footprint, the minimum sample may be able to >> benefit from tweaking. >> >> I just checked rtl22xx_t and it is < 16K code and 272 bytes of data. :) >> >> Hello tends to be in the 64K range. Perhaps a static allocation hello >> variant. >> >> Just wanting users to have good examples. A discussion at the Flight >> Software Workshop mentioned RTEMS was big but it doesn't seem to be if you >> look at executables which reflect those minimum feature sets. >> >> Hoping Sebastian has magic settings to apply so these numbers are as good >> as possible. >> >> This is a good idea. A "useful" minimum configuration with static > objects, or maybe even a couple of them, could be helpful to identify > reasonable bottom ends of the spectrum we can conceivably support. > It is important marketing. RTEMS is seen as big and full of functionality and we don't have any examples to say "hey RTEMS is small too". It's all just a matter of what functionality you use. FWIW size is misleading on some of our executables because the BSS sometimes is sized to end_ram. --joel > > >> --joel >> _______________________________________________ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel > >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
