source: rtems/c/src/lib/libbsp/m68k/gen68302/startup/bspstart.c @ 0ccb2bb

4.104.114.95
Last change on this file since 0ccb2bb was 6ea100c1, checked in by Joel Sherrill <joel.sherrill@…>, on 05/12/08 at 18:43:55

2008-05-12 Joel Sherrill <joel.sherrill@…>

  • startup/bspstart.c: Refactored and renamed initialization routines to rtems_initialize_data_structures, rtems_initialize_before_drivers, rtems_initialize_device_drivers, and rtems_initialize_start_multitasking. This opened the sequence up so that bootcard() could provide a more robust and flexible framework which is easier to explain and understand. This also lays the groundwork for sharing the division of available memory between the RTEMS workspace and heap and the C library initialization across all BSPs.
  • Property mode set to 100644
File size: 1.7 KB
Line 
1/*
2 *  This routine starts the application.  It includes application,
3 *  board, and monitor specific initialization and configuration.
4 *  The generic CPU dependent initialization has been performed
5 *  before this routine is invoked.
6 *
7 *  COPYRIGHT (c) 1989-1999.
8 *  On-Line Applications Research Corporation (OAR).
9 *
10 *  The license and distribution terms for this file may be
11 *  found in the file LICENSE in this distribution or at
12 *  http://www.rtems.com/license/LICENSE.
13 *
14 *  $Id$
15 */
16
17#include <string.h>
18
19#include <bsp.h>
20#include <rtems/libio.h>
21#include <rtems/libcsupport.h>
22
23/*
24 *  Use the shared implementations of the following routines
25 */
26
27void bsp_libc_init( void *, uint32_t, int );
28void bsp_pretasking_hook(void);               /* m68k version */
29
30/*
31 *  bsp_start
32 *
33 *  This routine does the bulk of the system initialization.
34 */
35
36void bsp_start( void )
37{
38  extern void          *_WorkspaceBase;
39  extern void          *_RamSize;
40  extern void          *_RamSize;
41  extern unsigned long  _M68k_Ramsize;
42
43  /* RAM size set in linker script */
44  _M68k_Ramsize = (unsigned long)&_RamSize;
45
46  /*
47   *  Allocate the memory for the RTEMS Work Space.  This can come from
48   *  a variety of places: hard coded address, malloc'ed from outside
49   *  RTEMS world (e.g. simulator or primitive memory manager), or (as
50   *  typically done by stock BSPs) by subtracting the required amount
51   *  of work space from the last physical address on the CPU board.
52   */
53
54  /*
55   *  Need to "allocate" the memory for the RTEMS Workspace and
56   *  tell the RTEMS configuration where it is.  This memory is
57   *  not malloc'ed.  It is just "pulled from the air".
58   */
59
60  Configuration.work_space_start = (void *) &_WorkspaceBase;
61}
Note: See TracBrowser for help on using the repository browser.