| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Updates #4661
|
|
|
|
|
|
| |
ATSAM_CONSOLE_DEVICE_INDEX and ATSAM_CONSOLE_DEVICE_TYPE have to be
integers like suggested by their description. Otherwise it's not
possible to select (for example) USART2 as console device.
|
|
|
|
|
|
|
| |
Nucleo does not have any SDRAM, so 0 size is the only possible right
choice here.
Sponsored-By: Precidata
|
|
|
|
|
|
|
| |
Nucleo does not have any SDRAM so default linkage to SDRAM does not make
any sense here.
Sponsored-By: Precidata
|
|
|
|
|
|
|
|
| |
This is the default configuration of the board out of the box.
Any other possible/supported configuration requires soldering,
so definitely not out of the box experience.
Sponsored-By: Precidata
|
|
|
|
|
|
|
|
|
| |
This patch adds stm32h747i-disco-m4 BSP variant and puts it in sync
with the stm32h747i-disco BSP variant hardware support. That means,
only USART 1, 2 and UART 8 are enabled. Also SDRAM 2 is set to 32MB,
SDRAM 1 size is set to 0.
Sponsored-By: Precidata
|
|
|
|
|
|
|
|
|
| |
This means:
SDRAM 1: 0
SDRAM 2: 32 MB
Sponsored-By: Precidata
|
|
|
|
|
|
|
|
| |
This patch disables all U(S)ARTs which are not supported by the board
itself and its provided connectors. That means only USART1 and 2
and UART8 are enabled.
Sponsored-By: Precidata
|
|
|
|
| |
Sponsored-By: Precidata
|
|
|
|
|
|
|
|
|
| |
This means:
SDRAM 1: 0
SDRAM 2: 32 MB
Sponsored-By: Precidata
|
|
|
|
|
|
|
| |
This patch disables all U(S)ARTs which are not supported by the board
itself and its provided connectors.
Sponsored-By: Precidata
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is minimalist configuration for the stm32h757i-eval-m4 BSP provided
here. The only general enhancement worth mention is a flash origin address
configuration which is needed for simplification as M4 core boots
from second flash bank which starts at 0x8100000 by default. The boot
address of the core may be changed by using STM32CubeProgrammer. If done
so then also BSP configuration needs to be changed accordingly.
As the BSP variant is running on M4 core, there is also more configuration
changes required here. E.g. boot core and ABI (compilation flags)
in comparison with stm32h757i-eval BSP. On the other hand, C code is shared
completely with this BSP variant.
Sponsored-By: Precidata
|
|
|
|
|
|
|
| |
This is done in preparation for future Cortex-M4 based BSP variants
which do not provide cache at all.
Sponsored-By: Precidata
|
|
|
|
|
|
|
|
|
| |
This means:
SDRAM 1: 0
SDRAM 2: 32 MB
Sponsored-By: Precidata
|
|
|
|
| |
Sponsored-By: Precidata
|
|
|
|
| |
Sponsored-By: Precidata
|
|
|
|
|
|
|
| |
This patch disables all U(S)ARTs which are not supported by the board
itself and its provided connectors.
Sponsored-By: Precidata
|
|
|
|
|
|
|
|
|
|
| |
This is minimalist configuration for the stm32h757i-eval BSP provided
here. The only general enhancement worth mention is boot core
configuration which is needed here as this is the first dual-core board
supported by stm32h7 BSP family and we need to choose boot core in order
to get C files compiling well.
Sponsored-By: Precidata
|
|
|
|
| |
Update #2349.
|
|
|
|
|
|
| |
Also adjust BSP spec file to make it buildable with board files.
Sponsored-By: Precidata
|
|
|
|
|
|
| |
Also adjust BSP spec file to make it buildable with board files.
Sponsored-By: Precidata
|
|
|
|
|
|
| |
Also adjust BSP spec file to make it buildable with board files.
Sponsored-By: Precidata
|
|
|
|
|
|
| |
The patch is done in preparation for stm32h7 BSP tree refactoring.
Sponsored-By: Precidata
|
|
|
|
| |
Close #4645.
|
| |
|
|
|
|
|
|
|
|
| |
Separate the Interrupt Manager implementation from the generic Arm GICv3
support. Move parts of the Arm GICv3 support into a new header file. This
helps to support systems with a clustered structure in which multiple GICv3
instances are present. For example, two clusters of two Cortex-R52 cores where
each cluster has a dedicated GICv3 instance.
|
| |
|
| |
|
| |
|
|
|
|
| |
Making this BSP a small memory target is a bit coarse and could be improved.
|
|
|
|
|
| |
The patch is needed due to smaller SRAM and completely disabled
SDRAM on the BSP variant.
|
| |
|
|
|
|
| |
Caveat: SDRAM 1 is completely disabled for now.
|
| |
|
| |
|
|
|
|
| |
function
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Make the task configuration reusable.
Update #3716.
|
|
|
|
|
|
|
| |
Add SMP-specifc SMP_FATAL_MULTITASKING_START_ON_NOT_ONLINE_PROCESSOR
fatal error. This fatal error helps to diagnose a broken SMP startup
sequence. Without this error a context switch using the NULL pointer
for the thread control block happens which may be difficult to debug.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test source code is generated from specification items
by the "./spec2modules.py" script contained in the
git://git.rtems.org/rtems-central.git Git repository.
Please read the "How-To" section in the "Software Requirements Engineering"
chapter of the RTEMS Software Engineering manual to get more information about
the process.
Update #3716.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test source code is generated from specification items
by the "./spec2modules.py" script contained in the
git://git.rtems.org/rtems-central.git Git repository.
Please read the "How-To" section in the "Software Requirements Engineering"
chapter of the RTEMS Software Engineering manual to get more information about
the process.
Update #3716.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test source code is generated from specification items
by the "./spec2modules.py" script contained in the
git://git.rtems.org/rtems-central.git Git repository.
Please read the "How-To" section in the "Software Requirements Engineering"
chapter of the RTEMS Software Engineering manual to get more information about
the process.
Update #3716.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test source code is generated from specification items
by the "./spec2modules.py" script contained in the
git://git.rtems.org/rtems-central.git Git repository.
Please read the "How-To" section in the "Software Requirements Engineering"
chapter of the RTEMS Software Engineering manual to get more information about
the process.
Update #3716.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test source code is generated from specification items
by the "./spec2modules.py" script contained in the
git://git.rtems.org/rtems-central.git Git repository.
Please read the "How-To" section in the "Software Requirements Engineering"
chapter of the RTEMS Software Engineering manual to get more information about
the process.
Update #3716.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test source code is generated from specification items
by the "./spec2modules.py" script contained in the
git://git.rtems.org/rtems-central.git Git repository.
Please read the "How-To" section in the "Software Requirements Engineering"
chapter of the RTEMS Software Engineering manual to get more information about
the process.
Update #3716.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test source code is generated from specification items
by the "./spec2modules.py" script contained in the
git://git.rtems.org/rtems-central.git Git repository.
Please read the "How-To" section in the "Software Requirements Engineering"
chapter of the RTEMS Software Engineering manual to get more information about
the process.
Update #3716.
|