As the button is pressed to disable latch Q2 the power remains ON because U10 remains on as long as the button is pressed.
Is that what's happening?

Yes but that wasn't my problem. When I press the button ESP32 is getting 3.3V but the code inside it is not running.

 

Yes but that wasn't my problem. When I press the button ESP32 is getting 3.3V but the code inside it is not running.

Then the code is the problem.
My routine would be when the Disp button is first pressed and powers up the mcu the first line of code would enable the Q2 latch.
Then goes to a sub routine loop that waits for the button release before proceeding.
Now gpio18 is polled waiting for the next button press which goes to another sub routine loop releasing latch Q2 and when the button is released power will disconnect

 

Yes but that wasn't my problem. When I press the button ESP32 is getting 3.3V but the code inside it is not running.

No but the code works when I connect the gate of the mosfet directly to ground using external jumper wires.

 

Then the mosfet is not fully on with the Q2 latch.

 

Then Q2 is not latched.

Yes, the reason Q2 is not latched because the code of esp32 is not running. Because at the very starting of my esp32 code I have written the code to turn the gpio connected to the base of transistor Q2 to turn on. I highly believe the esp32 core is resetting itself due to the current draw. But I don't know how to resolve it hahaha

 

It's not any current draw unless you have something wired incorrectly.

 

It's not any current draw unless you have something wired incorrectly.

The problem can be simple, the gpio connected to button is configured as INPUT with an internal pull up. But there's a diode present just before the IO, so I'm not sure what's causing the issue.

Btw the circuit I have there is from this video, nothing was changed.

 

What else is connected to the output of the LDO?

 

What else is connected to the output of the LDO?

Here's my schematics

 

Here's my schematics

For now only ESP32 is connected.

 

Then I'm still thinking it's a code problem.
Can you do a test code to confirm?

 

Then I'm still thinking it's a code problem.
Can you do a test code to confirm?

I'm using esp-idf to flash my initial code, Arduino IDE isn't cutting well for my use. Let me try to write a a very clean script with no additional Wifi stuff and confirm again.

 

Can you do a test code to confirm?

Guys, a huge apologies from my side. It is INDEED a problem with my code, I was testing a firmware which has lot of other stuff like wifi related and some where it's using this exact GPIO pin.

I have written a clean code as below

#include "freertos/FreeRTOS.h"

#include "freertos/task.h"

#include "esp_system.h"

#include "driver/gpio.h"

#include "esp_log.h"

#define BUTTON_GPIO 18

#define POWER_LATCH 40

#define DISP_PWR_CTRL 16

static const char *TAG = "GPIO_TOGGLE";

void app_main() {

    // Configure the power latch GPIO as output

    gpio_config_t power_latch = {

        .pin_bit_mask = (1ULL << POWER_LATCH),

        .mode = GPIO_MODE_OUTPUT,

        .pull_up_en = GPIO_PULLUP_DISABLE,

        .pull_down_en = GPIO_PULLDOWN_DISABLE,

        .intr_type = GPIO_INTR_DISABLE

    };

    ESP_ERROR_CHECK(gpio_config(&power_latch));

    gpio_set_level(POWER_LATCH, 1);

    // Configure the button GPIO as input

    gpio_config_t button_gpio_config = {

        .pin_bit_mask = (1ULL << BUTTON_GPIO),

        .mode = GPIO_MODE_INPUT,

        .pull_up_en = GPIO_PULLUP_ENABLE,

        .pull_down_en = GPIO_PULLDOWN_DISABLE,

        .intr_type = GPIO_INTR_DISABLE

    };

    ESP_ERROR_CHECK(gpio_config(&button_gpio_config));

    // Configure the LED GPIO as output

    gpio_config_t led_gpio_config = {

        .pin_bit_mask = (1ULL << DISP_PWR_CTRL),

        .mode = GPIO_MODE_OUTPUT,

        .pull_up_en = GPIO_PULLUP_DISABLE,

        .pull_down_en = GPIO_PULLDOWN_DISABLE,

        .intr_type = GPIO_INTR_DISABLE

    };

    ESP_ERROR_CHECK(gpio_config(&led_gpio_config));

    int led_state = 0;

    int last_button_state = 1; // Assume button is not pressed initially

    while (1) {

        // Read the button state

        int button_state = gpio_get_level(BUTTON_GPIO);

        // Check if the button state has changed

        if (button_state == 0 && last_button_state == 1) {

            // Toggle the LED state

            led_state = !led_state;

            gpio_set_level(DISP_PWR_CTRL, led_state);

            ESP_LOGI(TAG, "Button pressed, LED toggled to %d", led_state);

            // Debounce delay

            vTaskDelay(pdMS_TO_TICKS(200)); // 200 ms delay

        }

        // Update the last button state

        last_button_state = button_state;

        // Small delay to avoid busy-waiting

        vTaskDelay(pdMS_TO_TICKS(10));

    }

}

and now everything works fine, sorry for the trouble and confusion caused, you guys are amazing with the help.

 

Can you now see how much simpler a single mechanical, "alternate Action" push button switch would be?????

 

Can you now see how much simpler a single mechanical, "alternate Action" push button switch would be?????

The switch requirements changed in post #26

 

The switch requirements changed in post #26

OK, and quite correct. Of course, there do exist circuits to get around that issue, often called "auto-start circuits".
But in most industrial systems, not much is supposed to start up when power switches on. Safety rules.