How to trigger GPIO with traceTASK_SWITCHED_IN()
Posted: Thu Apr 16, 2020 1:05 pm
Hello,
I was reading about the FreeRTOS macros traceTASK_SWITCHED_IN() and traceTASK_SWITCHED_OUT() at this link from freertos.org:
https://www.freertos.org/rtos-trace-macros.html
I'd like to use the macros to drive GPIO pins to debug task behavior. I'm able to set a pin for each task with vTaskSetApplicationTaskTag.
To set the trace macros, I try to include "driver/gpio.h" at the end of "FreeRTOSConfig.h". When I try to do that, I get a lot of build errors starting with:
It seems I can't include "driver/gpio.h" in "FreeRTOSConfig.h".
Is it possible to use traceTASK_SWITCHED_IN() and traceTASK_SWITCHED_OUT() to drive GPIO pins with ESP-IDF?
Many thanks,
Dave
I was reading about the FreeRTOS macros traceTASK_SWITCHED_IN() and traceTASK_SWITCHED_OUT() at this link from freertos.org:
https://www.freertos.org/rtos-trace-macros.html
I'd like to use the macros to drive GPIO pins to debug task behavior. I'm able to set a pin for each task with vTaskSetApplicationTaskTag.
To set the trace macros, I try to include "driver/gpio.h" at the end of "FreeRTOSConfig.h". When I try to do that, I get a lot of build errors starting with:
Code: Select all
~/.espressif/tools/xtensa-esp32-elf/esp-2020r1-8.2.0/xtensa-esp32-elf/xtensa-esp32-elf/sys-include/machine/_default_types.h:41: Error: unknown opcode or format name 'typedef'
Is it possible to use traceTASK_SWITCHED_IN() and traceTASK_SWITCHED_OUT() to drive GPIO pins with ESP-IDF?
Many thanks,
Dave