Tests the default values of application configuration options.
More...
Tests the default values of application configuration options.
This test case performs the following actions:
- Check the effect of application configuration options with optional BSP-provided settings.
- Check the configured CONFIGURE_IDLE_TASK_BODY.
- Check the default value of CONFIGURE_IDLE_TASK_STACK_SIZE where the optional BSP-provided default value is enabled.
- Check the default value of CONFIGURE_INTERRUPT_STACK_SIZE where the optional BSP-provided default value is enabled.
- Check the BSP-provided initial extension is registered.
- Try to create a barrier.
- Check that the returned status code is RTEMS_TOO_MANY.
- Try to construct a message queue.
- Check that the returned status code is RTEMS_TOO_MANY.
- Try to create a partition.
- Check that the returned status code is RTEMS_TOO_MANY.
- Try to create a period.
- Check that the returned status code is RTEMS_TOO_MANY.
- Check that the processor maximum is one.
- Try to create a semaphore.
- Check that the returned status code is RTEMS_TOO_MANY.
- Try to construct a task.
- Check that the returned status code is RTEMS_TOO_MANY.
- Check the default CONFIGURE_MAXIMUM_TASKS value. A maximum Classic API task value of zero is only configurable if CONFIGURE_IDLE_TASK_INITIALIZES_APPLICATION is defined or CONFIGURE_MAXIMUM_POSIX_THREADS is set to a positive value. The default value of zero for CONFIGURE_MAXIMUM_POSIX_THREADS is used by the test suite containing the test case. The test suite defines CONFIGURE_IDLE_TASK_INITIALIZES_APPLICATION.
- Try to create a timer.
- Check that the returned status code is RTEMS_TOO_MANY.
- Try to create a user extension set.
- Check that the returned status code is RTEMS_TOO_MANY.