{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":566750839,"defaultBranch":"mcupsdk_v10.4.3_main","name":"mcupsdk-FreeRTOS-Kernel","ownerLogin":"TexasInstruments","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2022-11-16T10:45:22.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/24322022?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1705115468.0","currentOid":""},"activityList":{"items":[{"before":"3baa3dd98bb98ab58337f137747559b4f2cd24db","after":"a717afdff86fd9f52945adc58ba976d25ec0d69d","ref":"refs/heads/mcupsdk_v10.6.1_main","pushedAt":"2024-01-13T02:54:01.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"venkatesan-krishnamoorthy","name":"Venkatesan Krishnamoorthy","path":"/venkatesan-krishnamoorthy","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/123382521?s=80&v=4"},"commit":{"message":"Readme.md: point to MCU+ SDK repository for documentation\n\nThis repository contains fixes for cpp compilation when used as part of\nMCU+ SDK. Point to the mcupsdk-core repository for documentation on\nusing the freertos_fat repository as a submodule.\n\nSigned-off-by: Anoop <anoop.rk@ti.com>","shortMessageHtmlLink":"Readme.md: point to MCU+ SDK repository for documentation"}},{"before":null,"after":"3baa3dd98bb98ab58337f137747559b4f2cd24db","ref":"refs/heads/mcupsdk_v10.6.1_main","pushedAt":"2024-01-13T02:51:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"venkatesan-krishnamoorthy","name":"Venkatesan Krishnamoorthy","path":"/venkatesan-krishnamoorthy","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/123382521?s=80&v=4"},"commit":{"message":"POSIX port - Switch from allowing the user to specify the stack memory itself, to allowing them to specify the stack size\n\nChange from pthread_attr_setstack() to pthread_attr_setstacksize(), and automatically adjust the stack size\nto be at least PTHREAD_STACK_MIN if it wasn't already, removing the size warning.\n\nThis permits the user to increase the pthread stack size beyond the PTHREAD_STACK_MIN default of 16384 if\ndesired, without producing a warning in the typical case where stacks are minimized for RAM limited targets.\n\nContinue to store thread paramters on the provided stack, for consistency with the MCU targets.\n\nPreviously pthread_attr_setstack() was used to enable user defined stacks.\n\nNote that:\n\n1. The stack size can still be specified by the user.\n\n2. pxPortInitialiseStack(), and pthread_addr_setstack() was failing on stacks of typical size, as\n   these are smaller than PTHREAD_STACK_MIN (16384) bytes, and printing out a series of warnings.\n   Improve usability by having the posix port automatically increase the stack size to be\n   at least PTHREAD_STACK_MIN as posix platforms have enough memory for this not to be a concern.\n\n3. Reuse of stack memory will also result in valgrind 'invalid write' errors to what is demonstrably\n   valid memory. Root cause is that Valgrind is tracking a stack pointer as the stack is used.\n   Reuse of a stack buffer results in the stack being used at its start, in an area that Valgrind thinks\n   is far away from the start of the stack. There are ways to notify Valgrind of these changes\n   however this would require linking against and calling Valgrind functions from the FreeRTOS application using\n   the posix port, https://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.clientreq.\n\n   Also, apparently it isn't permitted by posix to reuse stack memory once its been used in a pthread via pthread_attr_setstack(),\n   see https://stackoverflow.com/a/5422134","shortMessageHtmlLink":"POSIX port - Switch from allowing the user to specify the stack memor…"}},{"before":"3baa3dd98bb98ab58337f137747559b4f2cd24db","after":"4bfb9b2d707304917f35fd5e7dcf692abb3d0cb2","ref":"refs/heads/mcupsdk_rel_09.01.00_smp","pushedAt":"2024-01-13T02:28:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"venkatesan-krishnamoorthy","name":"Venkatesan Krishnamoorthy","path":"/venkatesan-krishnamoorthy","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/123382521?s=80&v=4"},"commit":{"message":"Update SMP get idle task memory for static allocation (#784)\n\n* Add static idle task memory support for SMP\r\n* Rename vApplicationMinimalIdleTask to vApplicationPassiveIdleTask\r\n* Rename the macro configUSE_MINIMAL_IDLE_HOOK to configUSE_PASSIVE_IDLE_HOOK\r\n* Update xTaskGetIdleTaskHandle for SMP\r\n* Add more check in xTaskGetIdleTaskHandle\r\n* Support configKERNEL_PROVIDED_STATIC_MEMORY for SMP\r\n\r\n---------\r\n\r\nSigned-off-by: Gaurav Aggarwal <aggarg@amazon.com>\r\nCo-authored-by: Gaurav Aggarwal <aggarg@amazon.com>\r\nCo-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com>","shortMessageHtmlLink":"Update SMP get idle task memory for static allocation (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"1885376992\" data-permission-text=\"Title is private\" data-url=\"https://github.com/FreeRTOS/FreeRTOS-Kernel/issues/784\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/FreeRTOS/FreeRTOS-Kernel/pull/784/hovercard\" href=\"https://github.com/FreeRTOS/FreeRTOS-Kernel/pull/784\">FreeRTOS#784</a>)"}},{"before":null,"after":"3baa3dd98bb98ab58337f137747559b4f2cd24db","ref":"refs/heads/mcupsdk_rel_09.01.00_smp","pushedAt":"2024-01-13T02:27:44.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"venkatesan-krishnamoorthy","name":"Venkatesan Krishnamoorthy","path":"/venkatesan-krishnamoorthy","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/123382521?s=80&v=4"},"commit":{"message":"POSIX port - Switch from allowing the user to specify the stack memory itself, to allowing them to specify the stack size\n\nChange from pthread_attr_setstack() to pthread_attr_setstacksize(), and automatically adjust the stack size\nto be at least PTHREAD_STACK_MIN if it wasn't already, removing the size warning.\n\nThis permits the user to increase the pthread stack size beyond the PTHREAD_STACK_MIN default of 16384 if\ndesired, without producing a warning in the typical case where stacks are minimized for RAM limited targets.\n\nContinue to store thread paramters on the provided stack, for consistency with the MCU targets.\n\nPreviously pthread_attr_setstack() was used to enable user defined stacks.\n\nNote that:\n\n1. The stack size can still be specified by the user.\n\n2. pxPortInitialiseStack(), and pthread_addr_setstack() was failing on stacks of typical size, as\n   these are smaller than PTHREAD_STACK_MIN (16384) bytes, and printing out a series of warnings.\n   Improve usability by having the posix port automatically increase the stack size to be\n   at least PTHREAD_STACK_MIN as posix platforms have enough memory for this not to be a concern.\n\n3. Reuse of stack memory will also result in valgrind 'invalid write' errors to what is demonstrably\n   valid memory. Root cause is that Valgrind is tracking a stack pointer as the stack is used.\n   Reuse of a stack buffer results in the stack being used at its start, in an area that Valgrind thinks\n   is far away from the start of the stack. There are ways to notify Valgrind of these changes\n   however this would require linking against and calling Valgrind functions from the FreeRTOS application using\n   the posix port, https://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.clientreq.\n\n   Also, apparently it isn't permitted by posix to reuse stack memory once its been used in a pthread via pthread_attr_setstack(),\n   see https://stackoverflow.com/a/5422134","shortMessageHtmlLink":"POSIX port - Switch from allowing the user to specify the stack memor…"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAD3rVptAA","startCursor":null,"endCursor":null}},"title":"Activity · TexasInstruments/mcupsdk-FreeRTOS-Kernel"}