RTEMS  5.0.0
Modules | Macros
RTEMS Configuration

Modules

 Classic API Configuration
 
 Configuration Helpers
 
 Filesystems and Mount Table Configuration
 
 General System Configuration
 
 Scheduler configuration
 

Macros

#define CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY   FALSE
 
#define NULL_DRIVER_TABLE_ENTRY   { NULL, NULL, NULL, NULL, NULL, NULL }
 
#define CONFIGURE_MAXIMUM_DRIVERS
 
#define _CONFIGURE_LIBBLOCK_TASKS   0
 
#define _CONFIGURE_LIBBLOCK_TASK_EXTRA_STACKS   0
 
#define CONFIGURE_EXTRA_MPCI_RECEIVE_SERVER_STACK   0
 
#define _CONFIGURE_TIMER_FOR_SHARED_MEMORY_DRIVER   0
 
#define _CONFIGURE_MPCI_RECEIVE_SERVER_COUNT   0
 
#define CONFIGURE_MAXIMUM_ADA_TASKS   0
 
#define CONFIGURE_MAXIMUM_FAKE_ADA_TASKS   0
 
#define CONFIGURE_MAXIMUM_GOROUTINES   0
 
#define CONFIGURE_MAXIMUM_GO_CHANNELS   0
 

Detailed Description

This module contains all RTEMS Configuration parameters.

The model is to estimate the memory required for each configured item and sum those estimates. The estimate can be too high or too low for a variety of reasons:

Reasons estimate is too high:

Reasons estimate is too low:

NOTE: Eventually this may be able to take into account some of the above. This procedure has evolved from just enough to support the RTEMS Test Suites into something that can be used remarkably reliably by most applications.

This module contains configuration parameters related to the set of IDLE threads. On a uniprocessor system, there is one IDLE thread. On an SMP system, there is one for each core.

This module contains parameters related to thread and interrupt stacks.

This group contains the elements needed to define the Classic API Initialization Tasks Table.

Default User Initialization Task Table. This table guarantees that one user initialization table is defined.

WHEN CONFIGURE_HAS_OWN_INIT_TASK_TABLE is defined, the user is responsible for defining their own table information and setting the appropriate variables.

This group contains parameters related to generating a Device Driver Table.

Default Device Driver Table. Each driver needed by the test is explicitly chosen by the application. There is always a null driver entry.

This module contains parameters related to the LIBBLOCK buffering and caching subsystem. It requires tasks to swap out data to be written to non-volatile storage.

This module contains the parameters related to the Multiprocessing configuration of RTEMS.

In a single processor or SMP configuration, only two parameters are needed and they are defaulted. The user should not have to specify any parameters.

This modules includes configuration parameters for applications which use GNAT/RTEMS. GNAT implements each Ada task as a POSIX thread.

This modules includes configuration parameters for applications which use GCC Go.

Macro Definition Documentation

◆ _CONFIGURE_LIBBLOCK_TASK_EXTRA_STACKS

#define _CONFIGURE_LIBBLOCK_TASK_EXTRA_STACKS   0

This specifies the extra stack space configured for libblock tasks.

◆ _CONFIGURE_LIBBLOCK_TASKS

#define _CONFIGURE_LIBBLOCK_TASKS   0

This specifies the number of libblock tasks.

◆ CONFIGURE_EXTRA_MPCI_RECEIVE_SERVER_STACK

#define CONFIGURE_EXTRA_MPCI_RECEIVE_SERVER_STACK   0

This defines the extra stack space required for the MPCI server thread.

◆ CONFIGURE_MAXIMUM_ADA_TASKS

#define CONFIGURE_MAXIMUM_ADA_TASKS   0

This defines he number of POSIX mutexes GNAT needs. This defines he number of Ada tasks needed by the application.

◆ CONFIGURE_MAXIMUM_DRIVERS

#define CONFIGURE_MAXIMUM_DRIVERS

This specifies the maximum number of device drivers that can be installed in the system at one time. It must account for both the statically and dynamically installed drivers.

◆ CONFIGURE_MAXIMUM_FAKE_ADA_TASKS

#define CONFIGURE_MAXIMUM_FAKE_ADA_TASKS   0

This defines he number of non-Ada tasks/threads that will invoke Ada subprograms or functions.

◆ CONFIGURE_MAXIMUM_GO_CHANNELS

#define CONFIGURE_MAXIMUM_GO_CHANNELS   0

This specifies the maximum number of Go channels required.

◆ CONFIGURE_MAXIMUM_GOROUTINES

#define CONFIGURE_MAXIMUM_GOROUTINES   0

This specifies the maximum number of Go co-routines.

◆ CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY

#define CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY   FALSE

Should the RTEMS Workspace and C Program Heap be cleared automatically at system start up?

◆ NULL_DRIVER_TABLE_ENTRY

#define NULL_DRIVER_TABLE_ENTRY   { NULL, NULL, NULL, NULL, NULL, NULL }

This is an empty device driver slot.