Age | Commit message (Collapse) | Author |
|
|
|
This fixes the build for all other BSPs.
|
|
The CFLAGS influence the entire build. Using them for tests is madness. The
funny defines affected the rtems_board_support_package() directive.
|
|
|
|
Import ISVV testsuite from
CSW-RTEMSISVV-2022-TSP-05453_1-rtems-smp-isvv-iva-test-procedures.zip
with an SHA256 hash of
fdbe9ee336fd29da42ea7a0b8de558a369e7b3e0a2009b9a5c500f00fa960b88
|
|
|
|
|
|
|
|
|
|
If the CSafeLoader is available, load only the necessary build items.
This considerably speeds up the build setup time if the CSafeLoader is
used.
|
|
This makes it more obvious that this is an item UID.
|
|
Move the item cache handling to a ItemCache class. Implement this class
depending on the availability of CSafeLoader.
|
|
The CSafeLoader uses the C libyaml libary to considerably speed up the
loading of YAML files.
|
|
|
|
|
|
|
|
Make tests for libdl configurable since they are currently not
reproducible, see #4941.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These memory benchmark programs are not supposed to run. Instead, they
can be analysed on the host system to measure the memory usage of
features. See the membench module of rtems-central.
Update #3716.
|
|
The goal of the RTEMS pre-qualification activity #3701 is a specified
and validated subset of RTEMS. For users of the pre-qualified subset of
RTEMS it is important to not accidentally use not pre-qualified
features. One way to achieve this, is to build only the sources of the
pre-qualified feature set. This customized build is enabled by the new
build configuration option RTEMS_QUAL. If it is enabled, then only the
pre-qualified subset of RTEMS is built and installed.
Building with RTEMS_QUAL enable is currently only supported for the
sparc/leon3 BSP family. To support an RTEMS_QUAL enabled build, changes
in the CPU port and the BSP are required to only use features of the
pre-qualified feature set.
Update #4963.
|
|
Move the RTEMS test printer and rtems_test_exit() to separate files, to
remove dependencies from the begin/end test messsage support.
Update #4963.
|
|
Update #4925.
|
|
Document CONFIGURE_JFFS2_DELAYED_WRITE_TASK_PRIORITY.
Update #4961.
|
|
The TM27 support may define TM27_INTERRUPT_VECTOR_ALTERNATIVE to provide
an alternative software generated interrupt request which is raised by
_TM27_Raise_alternative() and cleared by _TM27_Clear_alternative().
Both functions shall return an RTEMS status code. This interrupt vector
may be used to test the interrupt controller support on targets which do
not provide generic software generated interrupts.
Update #3716.
|
|
Let the BSP define TM27_INTERRUPT_VECTOR_DEFAULT to more efficiently and
reliably get the TM27 default interrupt vector.
Update #3716.
|
|
|
|
Expose functions to directly manipulate the bad block table (BBT). These
functions are necessary to correct possible BBT corruption caused by
bugs in the BBT management layer.
|
|
The XNandPsu_EraseBlock function takes a target device and a block
offset for erasure. Ensure the block offset is within the size of the
target device.
|
|
When marking the trailing blocks on a device as reserved for Bad Block
Table usage, ensure that the correct blocks are marked. This resolves an
off-by-one error that was marking one block too low and leaving the last
block in the device unmarked.
|
|
When writing out the Bad Block Table, write it to the targeted device
and ensure the block is appropriately mapped to the targeted device.
|
|
Mark the BBT descriptor as invalid before scanning to ensure that
missing BBTs are detected and written correctly if necessary.
|
|
The Bad Block Table is a per-device catalog of the dispositions of each
block in the device. Only read enough data to determine the dispositions
of blocks for the device being read.
|
|
The xnandpsu driver includes functionality to map back and forth between
the flash-based BBT and the memory-based BBT with the values in each
being a bitwise inversion of each other. This resolves several bugs in
this process and simplifies the inversion from operating on the block
representation to operating on the entire BBT entry (4 blocks, 2 bits
per block, one byte total).
Bugs resolved in XNandPsu_ConvertBbt():
* The calculation of memory BBT entry offset was off by a factor of 4
* The entry offset into the flash BBT has been removed since each flash
BBT directly describes the flash space it is contained within and has
no reference to other devices in the chip
Bugs resolved in XNandPsu_WriteBbt():
* The BBT length calculated was reduced to NumTargetBlocks from
NumBlocks since only the relevant portion of the in-memory BBT should
be written to the flash-based BBT space
* An offset was applied to values retrieved from the in-memory BBT so
that only the relevant portion was converted and written to the
flash-based BBT
|
|
The XNandPsu_IsBlockBad() function is insufficient for JFFS2 to
determine whether a block is usable since the function does not report
reserved blocks. JFFS2 is also unable to use the last 4 blocks of each
target attached to the NAND controller since they are reserved for the
Bad Block Table (BBT), but not necessarily marked as such.
|
|
Hi all, this is my first email patch submission and my first contribution to RTEMS, so please give any
feedback you have!
This patch enables interrupt driven data reception on USART ports on
STM32F4 series chips. This feature is gated behind the config flag
BSP_CONSOLE_USE_INTERRUPTS. If this flag is not set to True, the older
polling implementation will be used. I tested this feature on STM32F401CE
(blackpill) and STM32 Nucleo F411RE boards, with both capable of keeping
up with a 115200 baud continous data stream. With the older polling
implementation, both would drop bytes at 9600 baud. In addition, I
updated the implementation of usart_set_attributes to support changing
the baud rate of the USART port based on the input speed.
|
|
Route the test output through T_vprintf() only while the test suite
runs. Otherwise, the begin/end of test message may not show up.
|
|
|
|
Route the test output through T_vprintf().
|
|
This feature is not supported by lwIP.
|
|
|
|
- Extend the timeout to 150 msec for long remote sessions
- Improve the performance of the detection
Closes #4975
Closes #4977
|
|
|
|
|