Re: [PATCH 2/2] aarch64/versal: Support DDRMC0 region 0 and 1

On 22/7/2022 4:35 pm, chr...@rtems.org wrote: > +void bsp_r1_heap_extend(void); > +void bsp_r1_heap_extend(void) > +{ > + const aarch64_mmu_config_entry* r1 = _r1_region[0]; > + if (false && r1->begin != r1->end) { Hmmm, I left a check in while debugging something and removing the false is

[PATCH 2/2] aarch64/versal: Support DDRMC0 region 0 and 1

From: Chris Johns - Support DDRMC0 region 0 up to 2G in size - Support DDRMC0 region 1 with DDR memory greater than 2G up to the DDRMC0 max amount - Extend the heap with region 1's memory Closes #4684 --- bsps/aarch64/xilinx-versal/include/bsp.h | 9

[PATCH 1/2] basp/aarch64: Make the unexpected sections origin address 64bit

From: Chris Johns Update #4684 --- bsps/aarch64/shared/start/linkcmds.base | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsps/aarch64/shared/start/linkcmds.base b/bsps/aarch64/shared/start/linkcmds.base index bcdf4715d7..f4639bd990 100644 ---

versal: Support DDRMC0 region 0 and 1

The Versal's DDRMC0 supports two separate regions. Region 0 is from 0 up to 2G where the Versal's hard IP regions start. DDR memory above the 2G mark is moved to region 1 and its base address is in the A64 address space. The patch will place all memory up to 2G in region 0 and if more is present

[PATCH v4 4/7] bsps/stm32f4: Add GPIO implementation for STM32F4

--- bsps/arm/stm32f4/gpio/gpio.c | 555 ++ bsps/arm/stm32f4/include/bsp.h| 4 - bsps/arm/stm32f4/include/bsp/stm32f4_gpio.h | 37 ++ bsps/arm/stm32f4/include/bsp/stm32f4_hal.h| 17 + bsps/arm/stm32f4/start/bspstart.c | 7 +-

[PATCH v4 5/7] bsps: Update license text

This patch updates the license text of GPIO API files and STM32F4 GPIO files. --- bsps/arm/stm32f4/gpio/gpio.c| 35 +++ bsps/arm/stm32f4/include/bsp/stm32f4_gpio.h | 27 --- bsps/include/bsp/gpio2.h| 37 +

[PATCH v4 6/7] bsps/stm32f4: Add missing GPIO functionality

--- bsps/arm/stm32f4/gpio/gpio.c| 32 + bsps/arm/stm32f4/include/bsp/stm32f4_gpio.h | 20 + 2 files changed, 52 insertions(+) diff --git a/bsps/arm/stm32f4/gpio/gpio.c b/bsps/arm/stm32f4/gpio/gpio.c index efc005bd9f..ac4d3b4f56 100644 ---

[PATCH v4 7/7] bsps/stm32f4: Fix GPIO port guards and ISR bug

Changes GPIO port guards from variant to #ifdef of ports. Fixed ISR memory-leak bug. Changed GPIO functions to extern and added comments for them. --- bsps/arm/stm32f4/gpio/gpio.c| 182 bsps/arm/stm32f4/include/bsp/stm32f4_gpio.h | 167 ++ 2

[PATCH v4 1/7] bsps/stm32f4 Include STM32F4 HAL

This patch is too large so I cannot send via email. Please find it here: https://github.com/dtbpkmte/GSoC-2022-RTEMS/commit/098ca07151bb9186c7681c45f8474cf1441acb40 --- .../stm32f4/hal/Legacy/stm32f4xx_hal_can.c| 1679 .../stm32f4/hal/Legacy/stm32f4xx_hal_eth.c| 2307 +

[PATCH v4 0/7] *** New GPIO API and implementation for STM32F4 BSP ***

Dear all, These patches add a new GPIO API that aims at portability. GPIO of STM32F4 BSP has been implemented using this API. The sample application code can be found at https://github.com/dtbpkmte/GSoC-2022-RTEMS-Sample-Apps. The newest branch is stm32f4-gpio. v2: - Made

[PATCH v4 2/7] bsps/arm: Integrate and build STM32F4 HAL

This patch is too large so I cannot send via email. Please find it here: https://github.com/dtbpkmte/GSoC-2022-RTEMS/commit/e21e1fa527da67533f797ed3dc6fc70cf245725b --- .gitignore| 1 + bsps/arm/include/cmsis_compiler.h | 266 +

[PATCH v4 3/7] bsps: Add GPIO API

This is the new GPIO API. The header file is gpio2.h. --- bsps/include/bsp/gpio2.h| 526 bsps/shared/dev/gpio/gpio.c | 189 + spec/build/bsps/obj.yml | 2 +- 3 files changed, 716 insertions(+), 1 deletion(-) create mode 100644

RE: [PATCH] Arm/raspberrypi.h: Added relevant headers for the bcm2711

Hi Noor,Following up with some additional thoughts:My approach for development for this BSP would be to focus on getting it working on a GitHub fork of the RTEMS repo. It could be messy while you are getting it working, but that is the fun part, in my opinion. If you need help or advice, you could

Re: Integrating the Formal Methods part of Qualification

Dear RTEMS developers, thanks for the feedback below - I want to wrap this up and move to the next step. I propose to produce a complete draft of a formal methods section for the Software Engineering manual in rtems-docs This will add a "Formal Verification" section just after the existing

Re: [PATCH 1/2] basp/aarch64: Make the unexpected sections origin address 64bit

Has this patch been tested with ILP32? I suspect that this line might need to get yanked out to a shared lp64 linkcmds.base and a shared ilp32 linkcmds.base or this line pulled up into the bsp-specific linkcmds variants. Kinsey On 7/22/2022 01:35, chr...@rtems.org wrote: From: Chris Johns

Re: [PATCH] score: Remove PRIORITY_PSEUDO_ISR thread priority

On 21.07.22 16:20, Joel Sherrill wrote: On Thu, Jul 21, 2022 at 12:53 AM Sebastian Huber > wrote: Hello Gedare and Joel, On 15.07.22 10:43, Sebastian Huber wrote: > The uniprocessor schedulers had some special case logic for the

Re: [PATCH] Arm/raspberrypi.h: Added relevant headers for the bcm2711

Hey Alan, Sorry for the late reply. So here's my plan. I initially thought of editing the raspberrypi.h and making it compatible for every RPi bsp. But I think I'll just be working on Aarch64 only. So I'll define everything related to bcm2711, not bcm283x. And After I complete with RPi4 bsp, we

RE: [PATCH] Arm/raspberrypi.h: Added relevant headers for the bcm2711

Hi Noor,The plan works for me. Focus on Aarch64 and we can try to merge/consolidate headers after that.I don’t mind looking at GitHub branches to review work in progress. Is that OK with everyone else?Thanks,Alan  From: Noor AmanSent: Friday, July 22, 2022 11:10 AMTo: Alan CudmoreCc: