Page History

...

The functions prefixed with app_ are supplied by the RTEMS application, i.e., the RCE project, in our case.

1. bsp_start()
   • Set up default character output function
   • Get CPU type and revision cached
   • Initialize device driver parameters
     • Rate of timer source for clock.c
     • bsp_timer_internal_clock
     • bsp_timer_average_overhead
     • bsp_timer_least_valid
   • Initialize default raw exception handlers
   • Call app_bsp_start()
   • Return to boot_code()
2. bsp_pretasking_hook()
   • Call app_bsp_pretasking_hook()
   • Return to boot_code()
3. bsp_predriver_hook()
   • Call app_bsp_predriver_hook()
   • Return to boot_code()
4. bsp_postdriver_hook()
   • Call rtems_libio_supp_helper() to open /dev/console for stdin, stdout and stderr, if it exists
   • Call app_bsp_postdriver_hook()
   • Return to boot_code()
5. bsp_cleanup()
   • Call app_bsp_cleanup()
   • Return to boot_code()

RCE BSP

This is the portion of the BSP that is specific to the RCE project. It can be found in release/rce/init/src/Init.cc.

1. app_bsp_start()
   • This routine should set up the processor and board as needed for the task at hand, i.e., it is not generic.
   • Replace the character output function with one that writes to the syslog
   • Return to bsp_start()
2. app_bsp_pretasking_hook()
   • Initialize RceDebug
   • Initialize RcePic
   • Return to bsp_pretasking_hook()
3. app_bsp_predriver_hook()
   • Initialize RceEthernet
   • Initialize RceBsdnet
   • Return to bsp_predriver_hook()
4. app_bsp_postdriver_hook()
   • Return to bsp_postdriver_hook()
5. app_bsp_cleanup()
   • Return to bsp_cleanup()

RceDebug

• Set up an RTEMS extension that creates and manages the syslog
• Return to app_bsp_pretasking_hook()

...