Proposal Review Request for "Add BSP for Polarfire-based Beagle" GSOC 2024 Project

2024-03-31 Thread Purva Yeshi
Hello, I am Purva Yeshi, a pre-final year Electronics and Telecommunication undergraduate from VJTI, Mumbai. I am very interested in the project "Add BSP for Polarfire-based Beagle" for GSOC 2024. I have successfully completed the Hello World task and also built the same Hello World code using the

Proposal Review Request for "Add BSP for Polarfire-based Beagle" GSOC 2024 Project

2024-03-31 Thread Purva Yeshi
Hello, I am Purva Yeshi, a pre-final year Electronics and Telecommunication undergraduate from VJTI, Mumbai. I am very interested in the project "Add BSP for Polarfire-based Beagle" for GSOC 2024. I have successfully completed the Hello World task and also built the same Hello World code using the

[Bugfix rtems-lwip 4/4] Fix crash due to link_detect_thread

2024-03-31 Thread Bernd Moessner
Within xemac_add, the link_detect_thread is set up before the ethernet interface is configured and all data structures have been set up correctly. The steps within xemac_add are basically: 1) Set up link_detect_thread 2) Initialize the interface 3) Set up the link speed / start autonegotiation 4) W

[Bugfix rtems-lwip 3/4] Correct the task prio of link_detect_thread

2024-03-31 Thread Bernd Moessner
On my side, the link_detect_thread never gets to running state. I assume that the issues with the FreeRTOS tick rate and delay definitions have never been observed as the associated thread was never running / no one requied it to run. Previously, the link_detect_thread was set to RTEMS_MAXIMUM_PRIO

[Bugfix rtems-lwip 2/4] Fix definition of vTaskDelay(x)

2024-03-31 Thread Bernd Moessner
FreeRTOS's vTaskDelay(x) is the FreeRTOS equivalent to rtems_task_wake_after(x), it suspends a task for x Ticks. The previously used sys_arch_delay(x) would add x/10 before passing it to rtems_task_wake_after. Due to the fact that portTICK_RATE_MS was set to wrong value the previous impl always cal

[Bugfix rtems-lwip 1/4] Fix definition of portTICK_RATE_MS

2024-03-31 Thread Bernd Moessner
The FreeRTOS define portTICK_RATE_MS must represent the time in ms between two system ticks. --- rtemslwip/xilinx/xlwipopts.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rtemslwip/xilinx/xlwipopts.h b/rtemslwip/xilinx/xlwipopts.h index d915c3c..23b942f 100644 --- a/rtemslwi

[Bugfix rtems-lwip 0/4] XILINX Link detect issues

2024-03-31 Thread Bernd Moessner
I had to recognize that cable plug / unplug events are not detected. This is due to the fact that the link detect thread is created, but never gets to running state due to a too high priority (255, but it seems it should be 254). In addition to that, there are some FreeRTOS defines that have not b

Re: Project Proposal feedback

2024-03-31 Thread Suraj Kumar
I am Suraj Kumar, currently interested in the project "Add Python initializer for gdb RTEMS specific support" Here is my proposal - https://docs.google.com/document/d/1VeS-QCJv5HUE4pUU8jJ-OqpYSvnffpZclXF7KbKGqAw/edit?usp=sharing I would greatly appreciate if you could review it and leave feedback