You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Environ is defined in libgloss and libc: - libgloss/or1k/syscalls.c - libc/stdlib/environ.c When linking we sometimes get errors: or1k-elf-g++ test.o -mnewlib -mboard=or1ksim -lm -o test /opt/shorne/software/or1k/lib/gcc/or1k-elf/5.3.0/../../../../or1k-elf/lib/libor1k.a(syscalls.o):(.data+0x0): multiple definition of `environ' /opt/shorne/software/or1k/lib/gcc/or1k-elf/5.3.0/../../../../or1k-elf/lib/libc.a(lib_a-environ.o):(.data+0x0): first defined here collect2: error: ld returned 1 exit status This doesnt happen after the fix. Basic things build fine too.
|5 years ago|
|boards||7 years ago|
|include||7 years ago|
|Makefile.in||7 years ago|
|README||7 years ago|
|aclocal.m4||7 years ago|
|board.h||7 years ago|
|caches-asm.S||7 years ago|
|configure||7 years ago|
|configure.in||7 years ago|
|crt0.S||5 years ago|
|exceptions-asm.S||7 years ago|
|exceptions.c||7 years ago|
|impure.c||7 years ago|
|interrupts-asm.S||7 years ago|
|interrupts.c||7 years ago|
|mmu-asm.S||7 years ago|
|or1k-internals.h||6 years ago|
|or1k_uart.c||7 years ago|
|or1k_uart.h||7 years ago|
|outbyte.S||7 years ago|
|sbrk.c||7 years ago|
|sync-asm.S||7 years ago|
|syscalls.c||5 years ago|
|timer.c||6 years ago|
|util.c||6 years ago|
This document describes the internals of the port for OpenRISC
1000. The API is documented in or1k-support.h as Doxygen comments.
# Data Structures
| vectors |
| text,data,.. |
| bss |
| heap |
| vv |
| ^^ |
| stack(s) |
+----------------+ _or1k_board_mem_base +
## Stack and Heap
The stack is allocated at the end of available physical memory which
is defined by each board as _or1k_board_mem_base and
_or1k_board_mem_size. The _or1k_stack_top and _or1k_stack_bottom are
determined by those variables and _or1k_stack_size (which may be
overwritten in _or1k_board_init_early).
A second stack for exceptions is allocated as we allow exceptions to
be arbitrary complex and call C functions etc. It is not an option to
re-use the current software stack as we want to be so generic, that
this can also be a virtual memory stack at moment of exception. The
exception starts below the normal software stack and is
Multicore: For each core a stack and exception stack is allocated and
the stack pointer set at boot. That is: sp(core0) = _or1k_stack_top,
sp(core1) = _or1k_stack_top - _or1k_stack_size, etc.
## _or1k_stack_core (multicore only)
An array of pointers to the software stacks (size:
4*or1k_numcores()). It is dynamically allocated from heap in or1k_init
by calling sbrk(). The pointers contain the values for stack top
pointers as described above. This variable is essentially used on boot
of the slave cores to configure the stack register.
## _or1k_exception_stack_core (multicore only)
An array of pointers to the exception stacks (size:
4*or1k_numcores()). It is allocated identical as the stack_core
array. It is loaded whenever an exception occurs to start with a clean
stack in the exception.
A table of function pointers to the handlers of the exceptions. The
generic exception handler checks if an exception handler is registered
and calls it. There are 30 exceptions defined (0x0 is not an exception
vector and 0x100 is reset which is static). This array resides in BSS
and is therefore initialized as 0 (no handler registered) after start.
Multicore: As the number of course is not known at compile time, the
variable is a pointer to and array of arrays (cores x 30) which is
allocated in or1k_init() on heap (using sbrk).
## _or1k_interrupt_handler_table and _or1k_interrupt_handler_table_data_ptr
The interrupt handlers are stored identical to to the exception handler table.
The struct _or1k_reent contains formerly global data and allows for
reentrancy. In the single core case, this is an allocated object,
while it is a pointer to an array of structs in the multicore library.
It is allocated in _or1k_reent_init() on the heap.