| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
This makes it easier to review start.o and set break points to trap table
entries. This change was checked by inspecting the trap table in start.o with
objdump.
Update #4458.
|
|
|
|
|
|
|
|
|
|
| |
The _ISR_Handler_initialization() does not touch the _ISR_Vector_table[]. Move
the definition of _ISR_Vector_table[] to a separate file.
Change license to BSD-2-Clause according to file history and re-licensing
agreement.
Update #3053.
|
|
|
|
|
|
|
| |
This variable is actually contained in _Per_CPU_Information[] which is already
zero initialized.
Remove superfluous includes.
|
|
|
|
|
|
|
| |
This CPU port macro was not used. Since the _ISR_Vector_table[] is statically
allocated, CPU ports could initialize this table in _CPU_Initialize() if
necessary. Remove _CPU_Initialize_vectors() to simplify the CPU port
interface.
|
|
|
|
|
|
| |
Fix an off by one error.
Update #3269.
|
|
|
|
|
|
|
| |
Change the default value of BSP_INTERRUPT_VECTOR_COUNT so that no interrupt
vectors are supported and all related directives return RTEMS_INVALID_ID.
Update #3269.
|
|
|
|
|
|
| |
This define is no longer used.
Update #3269.
|
|
|
|
|
|
| |
Use BSP_INTERRUPT_VECTOR_COUNT instead of BSP_INTERRUPT_VECTOR_MAX.
Update #3269.
|
|
|
|
|
|
| |
Replace it with BSP_INTERRUPT_VECTOR_COUNT.
Update #3269.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Assert BSP_INTERRUPT_VECTOR_MAX + 1 == BSP_INTERRUPT_VECTOR_COUNT.
After building all BSPs with this patch, BSP_INTERRUPT_VECTOR_MAX can be
removed and replaced by BSP_INTERRUPT_VECTOR_COUNT. The
BSP_INTERRUPT_VECTOR_COUNT allows a default implementation which supports no
interrupt vector at all. Using COUNT instead of MAX may avoid some
interpretation issues, for example is the maximum value a valid vector number
or not.
Update #3269.
|
|
|
|
|
|
| |
This define represents the last valid interrupt vector number.
Update #3269.
|
|
|
|
|
|
|
|
|
|
| |
Remove BSP_INTERRUPT_VECTOR_MIN and unconditionally let interrupt vector
numbers start with zero.
The BSP_INTERRUPT_VECTOR_MIN == 0 invariant was tested by the previous commit
and building all BSPs.
Update #3269.
|
|
|
|
|
|
|
| |
After building all BSPs with this patch, this BSP-specific define can be
removed to simplify the implementation.
Update #3269.
|
|
|
|
| |
Update #3269.
|
|
|
|
|
|
|
|
|
| |
This BSP uses a customized implementation of the interrupt extension API. It
was the only BSP which defined BSP_INTERRUPT_VECTOR_MIN to a value other than
zero. Define it to zero and use a custom bsp_interrupt_is_valid_vector()
function instead.
Update #3269.
|
|
|
|
|
|
|
| |
Remove the support for BSP_INTERRUPT_NO_HEAP_USAGE. This was only used
by one BSP and provides no real benefit.
Update #3269.
|
|
|
|
| |
Close #4461.
|
| |
|
|
|
|
| |
Fix compile error with RTEMS_DRVMGR_STARTUP = True.
|
|
|
|
|
|
|
| |
This adds the possibility to open an I2C bus with O_NONBLOCK (or set it
later via fcntl) to get non-blocking transmissions. This means that if
the bus is busy, a read, write or transfer ioctl will return with a
EAGAIN errno.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The write to RBAR didn't have the valid flag set. Therefore the write to
RASR had an influence on the previously set region. That means for
example that if Region 0 had been enabled but 1 should be disabled due
to a size of 0, the previous code would have disabled region 0 instead.
This patch fixes that behaviour.
Close #4450
|
|
|
|
|
|
|
| |
Don't initialze regions that have a negative size (for example due to a
wrong calculation).
Update #4450
|
|
|
|
| |
Closes #4455
|
|
|
|
|
|
|
| |
Change license to BSD-2-Clause according to file history and
re-licensing agreement.
Update #3053.
|
| |
|
| |
|
|
|
|
| |
Callers usually want to output a character.
|
| |
|
|
|
|
| |
This is already done in rtems_putc().
|
|
|
|
|
|
| |
Get rid of the hack to output into the idle stack during the early system
initialization. This fixes also a couple of test program failures which fail
due to missing output.
|
|
|
|
|
| |
Replace the global variable ambapp_plb with a function to allow an automatic on
demand initialization.
|
|
|
|
|
| |
Make the memory allocations in ambapp_scan() customizable via the new struct
ambapp_context parameter which generalizes the memory copy handler.
|
|
|
|
| |
Update #4202.
|
|
|
|
|
| |
The change also helps to avoid reports from static analysers since most
callers of _Thread_queue_Make_ready_again() check the unblock status.
|
|
|
|
|
|
|
| |
Mention the type of the pointer in the parameter description. Use the
more general term "object" instead of "variable".
Update #3993.
|
|
|
|
|
|
|
|
|
| |
Make the initialization of the per-CPU data optional.
Change license to BSD-2-Clause according to file history and
re-licensing agreement.
Update #3053.
|
|
|
|
|
| |
Make sure that the linker sets work if placed in a library (this is how
they are used in RTEMS).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Directly initialize the memory in the start sequence defined by start.S
instead of using a system initialization handler. This avoids using the
global variable rdb_start which used a memory location which was shared
with _ERC32_MEC_Timer_Control_Mirror. This change makes it possible to
use _Memory_Allocate() even before the system initialization is started.
Change license to BSD-2-Clause according to file history and
re-licensing agreement.
Update #3053.
|
|
|
|
|
|
| |
Initialize the stacks for all processors in one place. Do not rely on
Per_CPU_Control::interrupt_stack_high and directly use the statically
allocated interrupt stack area.
|
|
|
|
|
| |
Initialize the stacks in start.S in one place and identical to
_CPU_Context_Initialize().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the support to load the data section and rely on the boot loader. The
code is an artifact from the old erc32 days, when we would boot and execute
from ROM and the .data had to be copied over to RAM. With leon1/2/3, this is
not used anymore as a boot loader is made from the RAM image using a custom
tool (mkprom).
In SMP configurations, this support was also broken since LEON3_Boot_Cpu
(in the data section due to the -1 initialization value) was used quite
early in the start sequence.
If the data copy is really necessary, then an application can still add this
step as a very early system initialization step, since boot_card() and the
system initialization loop does not use initialized read-write data (only
read-only and BSS data). However, the SMP startup would still not work in this
case. A boot loader is a better place to load the sections.
|
| |
|
|
|
|
|
|
|
| |
Set Thread_queue_Context::timeout_absolute in
_Thread_queue_Context_set_timeout_argument() to avoid using it uninitialized.
The bug was introduced by a89ecaa1a94d49ddae7753d6b83923e9d2a00486.
|
|
|
|
|
|
|
| |
GCC originally needed this 20 years ago. No longer needed, so it
is being removed.
Closes #4391
|
|
|
|
|
|
| |
A warning was present when building RTEMS that stated that the argument
for malloc() exceeded the maximum object size. To get rid of this, I
changed many places where 'int' was being used to 'size_t'.
|
|
|
|
| |
The a72 BSPs are identical to the a53 BSPs just changing a53 to a72.
|
| |
|
|
|
|
|
|
| |
The addition of the entire *utime*() family of functions resulted
in this call returning ENOENT not ENXIO. This is better aligned
with the POSIX definition of the methods.
|
| |
|