summaryrefslogtreecommitdiffstats
path: root/bsps (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* bsp/tms570: The TMS570LC4357 has no TCRAM modulesSebastian Huber2024-01-152-0/+6
| | | | Update #4982.
* bsp/tms570: Initialize SRAM on demandSebastian Huber2024-01-151-10/+27
| | | | Update #4982.
* bsp/tms570: Use asm code for tms570_memory_init()Sebastian Huber2024-01-151-14/+21
| | | | | | Make sure that we do not use the stack for this function. Update #4982.
* bsp/tms570: Honor DBGRST for TMS570LC4357Tyler Miller2024-01-152-0/+22
| | | | Update #4982.
* bsp/tms570: Remove reset source handlingSebastian Huber2024-01-151-47/+0
| | | | | | Do not clear SYSESR and let the application handle the reset source. Update #4982.
* bsp/tms570: Add HCLKCNTL registerTyler Miller2024-01-151-2/+4
| | | | Update #4982.
* bsp/tms570: TMS570LC4x Errata DEVICE#60Tyler Miller2024-01-151-2/+7
| | | | Update #4982.
* bsp/tms570: Add errata SSWF021#45 handlingSebastian Huber2024-01-154-0/+437
| | | | Update #4982.
* bsp/tms570: Conditionalize TMS570LS3137 errataSebastian Huber2024-01-151-0/+4
| | | | Update #4982.
* bsp/tms570: Simplify expressionSebastian Huber2024-01-151-11/+12
| | | | Update #4982.
* bsp/tms570: Add TMS570LC4357 power supportTyler Miller2024-01-152-5/+25
| | | | Update #4982.
* bsp/tms570: Add TMS570LC4357 pin config supportTyler Miller2024-01-153-39/+12
| | | | Update #4982.
* bsp/tms570: Remove double pin configurationTyler Miller2024-01-151-10/+0
| | | | | | | | | Do not set pins to the default function before the actual setting is applied. If a pin setting needs to be done in a certain order, then this should be done explicitly through multiple calls to tms570_bsp_pinmmr_config(). Update #4982.
* bsp/tms570: Add tms570_pbist_run_and_check()Tyler Miller2024-01-153-54/+33
| | | | Update #4982.
* bsp/tms570: Add TMS570LC4357 PBIST supportTyler Miller2024-01-151-19/+32
| | | | Update #4982.
* bsp/tms570: Fix PBIST clock enableSebastian Huber2024-01-151-2/+2
| | | | | | Bit 1 of the PACT is reserved (writes have no effect). Update #4982.
* bsp/tms570: Add TMS570LC4357 BSP variantsSebastian Huber2024-01-152-0/+54
| | | | Update #4982.
* bsp/tms570: Add linkcmds.memorySebastian Huber2024-01-159-89/+19
| | | | | | | Remove obsolete tms570ls3137_hdk_with_loader BSP variant. With the new memory origin/size build options this variant is no longer required. Update #4982.
* bsp/tms570: Avoid vector overlay memory regionSebastian Huber2024-01-153-9/+24
| | | | | | | Reserve the space in a section. This makes it possible to use a common memory region definition. Update #4982.
* bsp/tms570: Add TM27 supportSebastian Huber2024-01-151-1/+128
| | | | Update #4982.
* bsp/tms570: Avoid spurious interruptsSebastian Huber2024-01-151-2/+10
| | | | Update #4982.
* bsp/tms570: Implement interrupt is enabled/pendingSebastian Huber2024-01-151-6/+40
| | | | Update #4982.
* bsp/tms570: Implement set/get interrupt prioritySebastian Huber2024-01-152-53/+140
| | | | Update #4982.
* bsp/tms570: Avoid errno for debug consoleSebastian Huber2024-01-151-1/+1
| | | | Update #4982.
* bsp/tms570: Fix bsp_reset()Sebastian Huber2024-01-151-1/+9
| | | | Update #4982.
* bsp/tms570: Rename tms570_initialize_and_clear()Sebastian Huber2024-01-153-3/+3
| | | | | | | Rename tms570_initialize_and_clear() in tms570_pom_initialize_and_clear(). Update #4982.
* bsp/tms570: Add bsp_restart()Sebastian Huber2024-01-152-0/+44
| | | | Update #4982.
* bsp/tms570: Use new pin defineSebastian Huber2024-01-151-1/+1
| | | | Update #4982.
* bsp/tms570: Relicense to BSD-2-ClauseSebastian Huber2024-01-1572-183/+1232
| | | | | | | | | Change license to BSD-2-Clause according to file history and contributor agreements. Add Doxygen file comments. Update #3053. Update #3707. Update #4982.
* bsp/tms570: Remove empty <bsp/tms570-vim.h>Sebastian Huber2024-01-152-49/+1
| | | | Update #4982.
* bsp/tms570: Remove empty <bsp/tms570-sci.h>Sebastian Huber2024-01-156-48/+56
| | | | Update #4982.
* bsp/tms570: Remove empty <bsp/tms570-rti.h>Sebastian Huber2024-01-153-48/+2
| | | | Update #4982.
* bsps/arm: Use shared empty bsp_start_hook_0()Sebastian Huber2024-01-157-29/+42
| | | | Update #4982.
* libio: Clean up usage of rtems_termios_device_modeKinsey Moore2024-01-1018-30/+34
| | | | | | | | | | | | 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.
* xparameters.h: fix typo in commentBernd Moessner2024-01-081-1/+1
|
* tm27: Add optional TM27_INTERRUPT_VECTOR_DEFAULTSebastian Huber2023-12-192-0/+3
| | | | | | | Let the BSP define TM27_INTERRUPT_VECTOR_DEFAULT to more efficiently and reliably get the TM27 default interrupt vector. Update #3716.
* 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-141-7/+63
| | | | | | | | | | | | | | | 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.
* 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
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-24 04:38:13 +0000