Changes between Version 60 and Version 61 of Developer/OpenProjects

Timestamp:

12/15/08 06:24:56 (15 years ago)

Author:

JoelSherrill

Comment:

/* TinyRTEMS */ Update

Developer/OpenProjects

@@ -208 +208 @@
 
 
-Status: Ongoing effort with multiple discrete projects.  Much progress has made on this goal since 4.7.0 but there is more shrinking left.  We are now to the point where the ARM/Thumb BSP rtl22xx_t has ~24K of code in the minimum.exe test.
+Status: Ongoing effort with multiple discrete projects.  Much progress has made on this goal since 4.7.0 but there is more shrinking left.  We are now to the point where the ARM/Thumb BSP rtl22xx_t has ~15K of code in the minimum.exe test.
 
 Reduce footprint of minimum RTEMS application.  We would like to be able to run on a CPU with only 64K ROM and 16K RAM.  This level of target hardware obviously is too small to host some RTEMS features.  
 
-Currently a minimum RTEMS application assumes that you want items like a reentrant C library,
-shutdown code and a minimal filesystem infrastructure.  Some ideas in
-this area are captured at [wiki:Projects/TinyRTEMS TinyRTEMS].  The project would focus on
-breaking linkages between components so they can be configured out by
-the user, dropped out automatically at link time, or other mechanisms.
-The goal is to be able to provide the user with a full featured RTEMS
-library and defer as much configuration as possible to application
-configuration and link time.
+Currently a minimum RTEMS application assumes that you want items like a shutdown code, initialization of all Classic API Managers, and support for c.  Some ideas in
+this area are captured at [wiki:Projects/TinyRTEMS TinyRTEMS].  The project would focus on breaking linkages between components so they can be configured out by 
+the user, dropped out automatically at link time, or other mechanisms.  The goal is to be able to provide the user with a full featured RTEMS
+library and defer as much configuration as possible to application configuration and link time.
+
+One issue that will be an ongoing concern is that the minimum footprint varies by BSP.  This is because some BSPs are structured to be lean, while others may have 
+unintentional dependencies.  One idea is a tool to assist in identifying RTEMS symbols which are not expected occur in some of the sample applications such minimum,
+hello, and ticker.  This utility could provide guidance on the known reasons this symbol creeps in.  For example, placing printk() support in the same file as
+the console driver will result in the entirety of the Termios subsystem being in the minimum footprint even though it is unused.
 = More NIC Drivers =