summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* tmfine01: Convert to JSON dataSebastian Huber2024-01-153-4270/+239
| | | | | This avoids a dependency on the non-standard libxml2 module. Reorder test cases according to expected performance.
* tmcontext01: Convert to JSON dataSebastian Huber2024-01-153-317/+181
| | | | This avoids a dependency on the non-standard libxml2 module.
* tmcontext01: Improve timing measurements for sparcSebastian Huber2024-01-151-16/+12
| | | | | Use a SPARC-specific method to flush the register windows. This improves the timing measurements.
* tmcontext01: Prevent optimizationsSebastian Huber2024-01-151-12/+3
| | | | | The previous method to prevent optimizations no longer worked at least with GCC 13. Disable intra-procedural optimizations.
* libio: Clean up usage of rtems_termios_device_modeKinsey Moore2024-01-1022-34/+39
| | | | | | | | | | | | This cleans up outputUsesInterrupts usage with rtems_termios_device_mode enum values. The outputUsesInterrupts member was typed as an int, named as if it were a boolean value, and used as if it were a rtems_termios_device_mode enum. In this patch, values assigned to outputUsesInterrupts have been converted to the corresponding rtems_termios_device_mode enum value, conversions from deviceOutputUsesInterrupts have been made explicit, and uses of rtems_termios_device_mode enum values with deviceOutputUsesInterrupts have been converted to booleans.
* bsps/aarch64/cache: Clean up unused fuctionsKinsey Moore2024-01-101-27/+2
| | | | | | | | | When the CPU_CACHE_SUPPORT_PROVIDES_RANGE_FUNCTIONS definition was added to AArch64 cache management, it obsoleted the *_1_data/instruction_line functions. These have been removed since they are no longer referenced. The AArch64_instruction_cache_inner_shareable_invalidate_all function is only used when RTEMS_SMP is defined, so only define it in that circumstance.
* cpukit/dosfs: Jump to correct error handlerKinsey Moore2024-01-101-1/+1
| | | | | | | When encountering an error during filesystem creation, fat_fd must be cleaned up appropriately once the file is opened. There was an opportunity for a resource leak due to jumping to the incorrect error handling label.
* Revert "Include Xilinx support files also for Zynq7000"Joel Sherrill2024-01-091-2/+0
| | | | | | This reverts commit d1d3ceb502cf4075c28a052b36630125387e1026. Per discussions on devel@ and Discord.
* xparameters.h: fix typo in commentBernd Moessner2024-01-081-1/+1
|
* Include Xilinx support files also for Zynq7000Bernd Moessner2024-01-051-0/+2
|
* cpukit/dosfs: Cast away ignored returnKinsey Moore2024-01-051-1/+1
| | | | | An error is already being reported. Checking the return value of this function is not useful.
* testsuites/fstests: Add JFFS2 NAND support testsKinsey Moore2023-12-2212-0/+502
| | | | | | This adds a second set of JFFS2 tests running on top of a simulated NAND backend to ensure that interactions with delayed writes operate as expected.
* cpukit/jffs2: Revert to non-granular lockingKinsey Moore2023-12-226-27/+61
| | | | | | | | | | Revert JFFS2 to non-granular locking. This makes the superblock available to the delayed work that it owns so that delayed work processing can ensure that shared resources are being exclusively accessed. This change only affects NAND systems. Moving forward with granular locking will require a significant investment of time in producing a test harness that doesn't require hardware such that this can get a reasonable amount of test coverage.
* fstests/tftpfs: Use rtems_test_run()Sebastian Huber2023-12-191-56/+2
|
* libtest: Change verbosity to normalSebastian Huber2023-12-191-1/+1
| | | | | A verbose verbosity is not required for normal test suite runs. It may be used to debug test cases.
* doxygen: CONFIGURE_JFFS2_DELAYED_WRITE_TASK_PRIORITYSebastian Huber2023-12-191-1/+29
| | | | | | Document CONFIGURE_JFFS2_DELAYED_WRITE_TASK_PRIORITY. Update #4961.
* tm27: Add TM27_INTERRUPT_VECTOR_ALTERNATIVESebastian Huber2023-12-195-6/+51
| | | | | | | | | | | 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.
* tm27: Add optional TM27_INTERRUPT_VECTOR_DEFAULTSebastian Huber2023-12-194-2/+27
| | | | | | | Let the BSP define TM27_INTERRUPT_VECTOR_DEFAULT to more efficiently and reliably get the TM27 default interrupt vector. Update #3716.
* ftpd: Fix set but not used warningSebastian Huber2023-12-191-1/+0
|
* bsps/xnandpsu: Allow manipulation of BBTKinsey Moore2023-12-142-0/+87
| | | | | | 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.
* bsps/xnandpsu: Constrain block erasure to deviceKinsey Moore2023-12-141-0/+4
| | | | | | 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.
* bsps/xnandpsu: Mark correct reserved blocksKinsey Moore2023-12-141-0/+4
| | | | | | | 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.
* bsps/xnandpsu: Write BBT to correct locationKinsey Moore2023-12-141-0/+5
| | | | | When writing out the Bad Block Table, write it to the targeted device and ensure the block is appropriately mapped to the targeted device.
* bsps/xnandpsu: Detect missing BBTsKinsey Moore2023-12-141-0/+3
| | | | | Mark the BBT descriptor as invalid before scanning to ensure that missing BBTs are detected and written correctly if necessary.
* bsps/xnandpsu: Read correct BBT sizeKinsey Moore2023-12-141-0/+4
| | | | | | 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.
* bsps/xnandpsu: Fix BBT mapping functionsKinsey Moore2023-12-141-0/+32
| | | | | | | | | | | | | | | | | | | | | | | 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
* bsps/zynqmp/jffs2: Use BBT information directlyKinsey Moore2023-12-141-1/+23
| | | | | | | | 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.
* bsps/arm/stm32f4: Enable USART RX interruptsJacob Killelea2023-12-142-7/+65
| | | | | | | | | | | | | | | 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.
* libtest: Fix test printer in rtems_test_run()Sebastian Huber2023-12-141-2/+11
| | | | | Route the test output through T_vprintf() only while the test suite runs. Otherwise, the begin/end of test message may not show up.
* psxftw01: Simplify and use rtems_test_run()Sebastian Huber2023-12-141-56/+6
|
* libtest: Set test printer in rtems_test_run()Sebastian Huber2023-12-141-3/+11
| | | | Route the test output through T_vprintf().
* ftpd: Make socket timeout optionalSebastian Huber2023-12-141-9/+4
| | | | This feature is not supported by lwIP.
* rtems-fdt: Fix node property access on 64bitChris Johns2023-12-141-1/+1
|
* libmisc/shell: Work around tmux bug in row and columnChris Johns2023-12-131-25/+125
| | | | | | | | | - Extend the timeout to 150 msec for long remote sessions - Improve the performance of the detection Closes #4975 Closes #4977
* build: Fix default valueSebastian Huber2023-12-121-1/+1
|
* bsp/tms570: Do not use POM for internal flashSebastian Huber2023-12-061-3/+2
|
* bsp/tms570: Improve POM handlingSebastian Huber2023-12-065-2/+14
| | | | | | Place the vector table in the start section so that the overlay can be avoided if we execute from internal flash. The problem is that when the POM is enabled, the ECC cannot be enabled for the internal flash.
* bsp/tms570: Adjust BSP_OSCILATOR_CLOCKSebastian Huber2023-12-061-0/+5
|
* bsp/tms570: Fix debug console baud settingSebastian Huber2023-12-061-1/+1
|
* bsp/tms570: Use internal RAM for fast dataSebastian Huber2023-12-061-1/+1
|
* bsp/tms570: Add TMS570LC4357 supportSebastian Huber2023-12-063-0/+32
|
* bsp/tms570: Add TMS570_VARIANTSebastian Huber2023-12-062-0/+23
|
* bsp/tms570: Use 0x for hex constantsSebastian Huber2023-12-061-8/+8
|
* bsp/tms570: Replace TMS570_MMR_SELECT_GMII_SELSebastian Huber2023-12-062-1/+9
| | | | | Replace TMS570_MMR_SELECT_GMII_SEL with TMS570_MMR_SELECT_MII_MODE and TMS570_MMR_SELECT_RMII_MODE.
* bsp/tms570: Add pin configuration variantsSebastian Huber2023-12-062-46/+133
| | | | | | | Rearrange pin function bit fields to allow the clearing of all function bits through TMS570_PIN_AND_FNC(). Move implementation details to source file.
* bsp/tms570: Enable cache manager implementationSebastian Huber2023-12-061-1/+2
|
* bsp/tms570: Export -mbe32 to pkg-configSebastian Huber2023-12-061-0/+1
|
* bsps/arm: BSP_START_VECTOR_ADDRESS_TABLE_ALIGNMENTSebastian Huber2023-12-063-1/+29
| | | | | Add the BSP option BSP_START_VECTOR_ADDRESS_TABLE_ALIGNMENT to optionally define an alignment of the vector address table begin.
* build: Add assert-in-set option actionSebastian Huber2023-12-061-0/+8
|
* ZYNQ7000: Add support PYNQ, PicoZed, MicroZed, ZYBO and ZYBO Z7Bernd Moessner2023-11-2821-2/+171
| | | | | | | | | | | | | This patch adds basic support for the following boards: xilinx_zynq_pynq - PYNQ Z1 / Z2 xilinx_zynq_microzed - MicroZed 7010 / 7020 xilinx_zynq_picozed - PicoZed 7010 / 7015 / 7020 / 7030 xilinx_zynq_zybo - ZYBO xilinx_zynq_zybo_z7 - ZYBO Z7-10 / Z7-20 N.b. Arty Z7-20 is basically a PYNQ Z1 - different board color and updated Eth PHY.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-20 04:29:52 +0000