blob: e13d2a0d28a9ccf92eb2f91da216539312027aea (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
@c
@c COPYRIGHT (c) 1988-1998.
@c On-Line Applications Research Corporation (OAR).
@c All rights reserved.
@c
@c $Id$
@c
@chapter CPU Initialization
This section describes the general CPU and system initialization sequence
as it pertains to the CPU dependent code.
@section Introduction
XXX general startup sequence description rewritten to make it more
applicable to CPU depdent code in executive
@section CPU Dependent Configuration Table
The CPU Dependent Configuration Table contains information which tailors
the behavior of RTEMS base Some of the fields in this table are required
to be present in all ports of RTEMS. These fields appear at the beginning
of the data structure. Fields past this point may be CPU family and CPU
model dependent. For example, a port may add a field to specify the
default value for an interrupt mask register on the CPU. This table is
initialized by the Board Support Package and passed to the
rtems_initialize_executive or rtems_initialize_executive_early directive.
@example
typedef struct @{
void (*pretasking_hook)( void );
void (*predriver_hook)( void );
void (*postdriver_hook)( void );
void (*idle_task)( void );
boolean do_zero_of_workspace;
unsigned32 idle_task_stack_size;
unsigned32 interrupt_stack_size;
unsigned32 extra_mpci_receive_server_stack;
void * (*stack_allocate_hook)( unsigned32 );
void (*stack_free_hook)( void* );
/* end of fields required on all CPUs */
unsigned32 some_other_cpu_dependent_info;
@} rtems_cpu_table;
@end example
XXX copy the descriptions of the fields from another CPU supplement
@section Initializing the CPU
The _CPU_Initialize routine performs processor dependent initialization.
@example
void _CPU_Initialize(
rtems_cpu_table *cpu_table,
void (*thread_dispatch) /* may be ignored */
)
@end example
The thread_dispatch argument is the address of the entry point for the
routine called at the end of an ISR once it has been decided a context
switch is necessary. On some compilation systems it is difficult to call
a high-level language routine from assembly. Providing the address of the
_Thread_ISR_Dispatch routine allows the porter an easy way to obtain this
critical address and thus provides an easy way to work around this
limitation on these systems.
If you encounter this problem save the entry point in a CPU dependent
variable as shown below:
@example
_CPU_Thread_dispatch_pointer = thread_dispatch;
@end example
During the initialization of the context for tasks with floating point,
the CPU dependent code is responsible for initializing the floating point
context. If there is not an easy way to initialize the FP context during
Context_Initialize, then it is usually easier to save an "uninitialized"
FP context here and copy it to the task's during Context_Initialize. If
this technique is used to initialize the FP contexts, then it is important
to ensure that the state of the floating point unit is in a coherent,
initialized state.
Finally, this routine is responsible for copying the application's CPU
Table into a locally accessible and modifiable area. This is shown below:
@example
_CPU_Table = *cpu_table;
@end example
|
