diff options
Diffstat (limited to 'bsp_howto/initilization_code.rst')
| -rw-r--r-- | bsp_howto/initilization_code.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/bsp_howto/initilization_code.rst b/bsp_howto/initilization_code.rst index d6ce46b..4657602 100644 --- a/bsp_howto/initilization_code.rst +++ b/bsp_howto/initilization_code.rst @@ -4,7 +4,7 @@ Initialization Code Introduction ============ -The initialization code is the first piece of code executed when there’s a +The initialization code is the first piece of code executed when there's a reset/reboot. Its purpose is to initialize the board for the application. This chapter contains a narrative description of the initialization process followed by a description of each of the files and routines @@ -178,7 +178,7 @@ The ``boot_card()`` routine performs the following functions: When in the context of the first task but before its body has been entered, any C++ Global Constructors will be invoked. -That’s it. We just went through the entire sequence. +That's it. We just went through the entire sequence. bsp_work_area_initialize() - BSP Specific Work Area Initialization ------------------------------------------------------------------ @@ -227,7 +227,7 @@ in the order they appear in the Device Driver Table. The Driver Address Table is part of the RTEMS Configuration Table. It defines device drivers entry points (initialization, open, close, read, write, and control). For more information about this table, please -refer to the *Configuring a System* chapter in the*RTEMS Application C User’s Guide*. +refer to the *Configuring a System* chapter in the*RTEMS Application C User's Guide*. The RTEMS initialization procedure calls the initialization function for every driver defined in the RTEMS Configuration Table (this allows @@ -289,7 +289,7 @@ of ``__uhoh`` in the ``gen68340`` BSP. At ``__uhoh`` label is the default interrupt handler routine. This routine is only called when an unexpected interrupts is raised. One can -add their own routine there (in that case there’s a call to a routine - +add their own routine there (in that case there's a call to a routine - $BSP_ROOT/startup/dumpanic.c - that prints which address caused the interrupt and the contents of the registers, stack, etc.), but this should not return. @@ -325,7 +325,7 @@ Integrated Processor Registers Initialization The CPUs used in many embedded systems are highly complex devices with multiple peripherals on the CPU itself. For these devices, there are always some specific integrated processor registers -that must be initialized. Refer to the processors’ manuals for +that must be initialized. Refer to the processors' manuals for details on these registers and be VERY careful programming them. Data Section Recopy @@ -348,7 +348,7 @@ The RTEMS Configuration Table The RTEMS configuration table contains the maximum number of objects RTEMS can handle during the application (e.g. maximum number of tasks, -semaphores, etc.). It’s used to allocate the size for the RTEMS inner data +semaphores, etc.). It's used to allocate the size for the RTEMS inner data structures. The RTEMS configuration table is application dependent, which means that @@ -367,7 +367,7 @@ application. In 4.9 and newer, we have eliminated the BSP copies of the configuration tables and are making efforts to make the configuration information generated by ``<rtems/confdefs.h>`` constant and read only. -For more information on the RTEMS Configuration Table, refer to the*RTEMS Application C User’s Guide*. +For more information on the RTEMS Configuration Table, refer to the*RTEMS Application C User's Guide*. .. COMMENT: COPYRIGHT (c) 1988-2008. |