Issue created by Zebulun Barnett: https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/work_items/24
## Summary With the default `tskIDLE_PRIORITY` priority of `RTEMS_MAXIMUM_PRIORITY` (255) it appears the "link" (link_detect_thread) never runs since it has the same priority as the idle threads. When I changed the priority to 254, it starts running but then it ends up taking up all the idle time of the CPU it's on. `vTaskDelay(LINK_DETECT_THREAD_INTERVAL / portTICK_RATE_MS)` https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/blob/main/embeddedsw/ThirdParty/sw_services/lwip211/src/contrib/ports/xilinx/netif/xadapter.c?ref_type=heads#L462 ends up working out to be 0 since `LINK_DETECT_THREAD_INTERVAL` is 1000 and `portTICK_RATE_MS` is some multiple of 1000 so the division always results in 0. I'm guessing https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/blob/main/rtemslwip/xilinx/xlwipopts.h?ref_type=heads#L32 `#define portTICK_RATE_MS (rtems_clock_get_ticks_per_second() * 1000)` should have been `#define portTICK_RATE_MS (rtems_clock_get_ticks_per_second() / 1000)` instead? -- View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/work_items/24 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/4-0p2bu4ue3goe34s8uvnf4gip1-m/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
