|
|||||||||||||||
FreeRTOS Support ArchiveThe FreeRTOS support forum is used to obtain active support directly from Real Time Engineers Ltd. In return for using our top quality software and services for free, we request you play fair and do your bit to help others too! Sign up to receive notifications of new support topics then help where you can.
Loading
FreeRTOSV7.4.0 Atmega32 running only one taskPosted by shoeb on April 13, 2013 Hello, I have created a couple of tasks to blink some LED's connected to output port of Atmega32. I am using STK500. But I am able to run only one task. I am not sure the other task is even getting created. I checked with several stack sizes from minimal to 500 bytes for each task. Still does not help. I do not have any debugger to check the code at run time I am using AvrStudio 4.14 for development. Appreciate all your help thanks... RE: FreeRTOSV7.4.0 Atmega32 running only one taskPosted by Dave on April 13, 2013 Check the return value of xTaskCreate() to know if the task is being created, and invest in a debugger. I think you can run the code in the AVR simulator without a debugger. RE: FreeRTOSV7.4.0 Atmega32 running only one taskPosted by shoeb on April 17, 2013 Thanks for replying, I will be doing that. I checked with creating on only one task and it does what it is supposed to do. Task 1 by itself toggles the LED's as it should. Task 2 by itself toggles as it should. But when I want to create both of them only of them is created. I am not able to understand if I am overflowing the stack or is there something to do with the interrupts? Or am I missing any macro that I should configure before compiling. Thanks. RE: FreeRTOSV7.4.0 Atmega32 running only one taskPosted by shoeb on April 21, 2013 Hi, Both the tasks are created I verified using Simulation in AvrStudio debugger. But only one of them is running. The low priority task. Please help. The high priority task never seems to be executed. RE: FreeRTOSV7.4.0 Atmega32 running only one taskPosted by Richard on April 22, 2013 Please first check that your tick interrupt is executing. You can do this quite simply by either setting a break point in vTaskIncrementTick() (in task.c) or by inspecting the xTickCount variable when the application has been running for a while. xTickCount should not be zero after a tick interrupt has executed. If the tick interrupt is executing please post the outline of your tasks here. Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|
|||||||||||||||
NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.
Meet Richard Barry and learn about running FreeRTOS on RISC-V at FOSDEM 2019
Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.
View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.
FreeRTOS and other embedded software careers at AWS.
