Thank you, I'd gone blind! Much appreciated.

I've made a right mess of migrating from 5.5 to 6.0 and have lost track of edits that I've done. My current issue is that I cannot get rid of an error being thrown every time I pass arguments to esp_timer_create. The IDE only seems happy when it's esp_timer_create() with no arguments, which clearly ...

Ok that's a vague title so let's expand on that.

INPUT1 is a light gate, 1 when intact, 0 when broken and wired to a GPIO digital input.
There are 4 separate light gates in the real case, but I'll just take one for simplicity.

I'm interested in two attributes:
1) When did the beam get broken?
2 ...

Perfect, thanks!

It's this block of code below that's causing the problem, but I don't know why. Switched to VS Code to ensure there was no environment issue going on that I couldn't find.

/*gpio_config_t io_conf1;
io_conf1.intr_type = GPIO_INTR_DISABLE;//disable interrupt
io_conf1.mode = GPIO_MODE_INPUT;
io ...

To add some more information:

- I've confirmed the monitor is at 115200
- I've tried different usb ports and cables (all flash fine, all give no serial output)
- I've tried manually resetting the board with the terminal running

Hi all, I assume I'm doing something stupid but I can't figure it out at the minute. Using Espressif-IDE, DOIT Devkit v1 ESP32. Whilst my program runs absolutely fine I can't get any printf output to the terminal - I get all the flash and boot information but then it stops at the green line below ...

I'm an idiot, I never called pin_setup() within main. Thanks for driving me to look closer at my code, the fact that the #define was still actioned threw me off. Cheers.

I've commented out the majority of my code but still get the same behaviour - permanent high without the gpio_set_direction(), working as intended with. Copy paste of my code below.

#include <inttypes.h>
#include <stdio.h>
#include <freertos/FreeRTOS.h>
#include <freertos/task.h>
#include <sys ...

I can check again but given the addition of a gpio_set_direction() then works it must be executing the first code block to understand what AMBER_LIGHT1 is. Because it works fine with just the addition of that direction call I'll triple (quadruple?) check I have no conflicting definition for GPIO5 ...