URL
https://opencores.org/ocsvn/or1k_old/or1k_old/trunk
Details |
Compare with Previous |
View Log
Line No. |
Rev |
Author |
Line |
1 |
1026 |
ivang |
@c
|
2 |
|
|
@c COPYRIGHT (c) 1988-2002.
|
3 |
|
|
@c On-Line Applications Research Corporation (OAR).
|
4 |
|
|
@c All rights reserved.
|
5 |
|
|
@c
|
6 |
|
|
@c developtools.t,v 1.4 2002/01/17 21:47:45 joel Exp
|
7 |
|
|
@c
|
8 |
|
|
|
9 |
|
|
@chapter Development Tools
|
10 |
|
|
|
11 |
|
|
When porting RTEMS to a new CPU architecture, one will have to have a
|
12 |
|
|
development environment including compiler, assembler, linker, and
|
13 |
|
|
debugger. The GNU development tool suite used by RTEMS supports most
|
14 |
|
|
modern CPU families. Often all that is required is to add RTEMS
|
15 |
|
|
configurations for the target CPU family. RTEMS targets for the GNU tools
|
16 |
|
|
usually start life as little more than aliases for existing embedded
|
17 |
|
|
configurations. At this point in time, ELF is supported on most of the
|
18 |
|
|
CPU families with a tool target of the form CPU-elf. If this target is
|
19 |
|
|
not supported by all of the GNU tools, then it will be necessary to
|
20 |
|
|
determine the configuration that makes the best starting point regardless
|
21 |
|
|
of the target object format.
|
22 |
|
|
|
23 |
|
|
Porting and retargetting the GNU tools is beyond the scope of this manual.
|
24 |
|
|
The best advice that can be offered is to look at the existing RTEMS
|
25 |
|
|
targets in the tool source and use that as a guideline.
|
26 |
|
|
|
© copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.