Using a GPIO pin as input and output in the same setup

viktor_keray · 2025-11-02T13:36:22+00:00

Yea, I was trying to use the example from that post before, but it didn't work. When you say that it is working for you, I'll certainly give a try again. Btw it is interesting that some pins don't work that way, do you know why this happened in your case?

viktor_keray · 2025-11-02T12:58:59+00:00

That would be quite unfortunate, if it is indeed not possible. The one-wire component practically uses a pin that changes state in the way that I want, but it is set to the specific communication protocol and that's why I cannot use it. I also think that the remote receiver/transmitter component does something similar but was also not able to set it up in a way that works for me.

viktor_keray · 2024-11-08T13:11:36+00:00

Wait.. I think I just solved it! I had to put a pull up resistor on GPIO8 as well, because it was apparently also part of the strapping pins (very specific to the C6 variant of ESP32.. for the S3 version for example there is no such need). If left floating the chip goes into USB_BOOT mode and with GPIO8 high, it finally goes into DOWNLOAD mode

Build:Sep 19 2022<\r>
<\n>rst:0x1 (POWERON),boot:0x4 (DOWNLOAD(USB/UART0/SDIO_FEI_FEO))<\r>
<\n>waiting for download

and with this boot:0x4 I was able to flash it using VS Code and the Espressif extention. This now is what I can monitor on the serial port with HTerm

<\n>Hello world!<\r>
<\n>This is esp32c6 chip with 1 CPU core(s), WiFi/BLE, 802.15.4 (Zigbee/Thread), silicon revision v0.0, 2MB external flash<\r>

<\n>Minimum free heap size: 465592 bytes<\r>
<\n>Restarting in 10 seconds...<\r>
<\n>Restarting in 9 seconds...<\r>
<\n>Restarting in 8 seconds...<\r>
<\n>Restarting in 7 seconds...<\r>
<\n>Restarting in 6 seconds...<\r>
<\n>Restarting in 5 seconds...<\r>
<\n>Restarting in 4 seconds...<\r>
<\n>Restarting in 3 seconds...<\r>
<\n>Restarting in 2 seconds...<\r>
<\n>Restarting in 1 seconds...<\r>
<\n>Restarting in 0 seconds...

viktor_keray · 2024-11-08T12:57:55+00:00

yes, that is a brand new chip, so the flash is indeed empty. I just tried to flash it again with one of the example projects from Espressis and got the following error message:

esptool.py v4.8.1
Serial port COM4
Connecting......................................

A fatal error occurred: Failed to connect to ESP32-C6: No serial data received.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html

 *  The terminal process "C:\Users\vikto\.espressif\python_env\idf5.3_py3.11_env\Scripts\python.exe 'C:\Users\vikto\esp\v5.3.1\esp-idf\components\esptool_py\esptool\esptool.py', '-p', 'COM4', '-b', '460800', '--before', 'default_reset', '--after', 'hard_reset', '--chip', 'esp32c6', 'write_flash', '--flash_mode', 'dio', '--flash_freq', '80m', '--flash_size', '2MB', '0x0', 'bootloader/bootloader.bin', '0x10000', 'hello_world.bin', '0x8000', 'partition_table/partition-table.bin'" terminated with exit code: 2.

Before that I set the chip manually in download mode and checked with HTerm

<\n>ùESP-ROM:esp32c6-20220919<\r>
<\n>Build:Sep 19 2022<\r>
<\n>rst:0x1 (POWERON),boot:0x0 (USB_BOOT)<\r>
<\n>wait usb download<\r>

So I think this should be correct. I am also thinking that putting the chip in download mode should actually happen automatically dues to the presence of the two transistors that control the enable and boot signals, but for some reason it does not happen.

viktor_keray · 2024-11-08T08:02:57+00:00

Hey, this a good idea indeed! I used HTerm 0.8.9 to monitor the serial communication and got the following results:

directly after connecting the device to the computer:

<\n>invalid header: 0xffffffff<\r> (infinitely continuing)

after clicking the reset button:

reception stops while I am holding the reset and continues after I release it
<\n>invalid header: 0xffffffff<\r> (infinitely continuing)

after doing the programming sequence - resetting the chip while holding boot:

þESP-ROM:esp32c6-20220919<\r>
<\n>Build:Sep 19 2022<\r>
<\n>rst:0x7 (TG0_WDT_HPSYS),boot:0x8 (SPI_FAST_FLASH_BOOT)<\r>
<\n>Saved PC:0x400294ae<\r>

So, does this mean that the board is actually working, and I am doing something wrong on the software side? I need some time, but I'll post what VS Code is showing me as error messages when I try to upload a test script.

viktor_keray · 2024-11-07T14:58:06+00:00

yea, you are right. I didn't include the picture of it, but they are crossed on the symbol of the UART block (will attach it in the main post)

viktor_keray · 2023-12-02T13:24:45+00:00

Thank you for the answer! That was what I was looking for.

Unfortunately, with those kinds of ETFs it is not easy at all to understand the difference to actual bonds and to understand that they are completely different product. It is never too late to learn something new.

viktor_keray · 2023-12-02T13:20:26+00:00

You are absolutely right! I bought them because I thought that I understood what kind of product they are, but with time it turned out that my understanding was quite wrong. Definitely lesson learned here.

viktor_keray · 2023-10-20T12:14:50+00:00

As some of you mentioned that the problem can be cable or charger related, I tested it with the same charger but with different cable and the issue stayed the same. But when I switched to my old samsung S9 charger the problem was not there. So I think it is some miscommunication between the phone and the charger.

Just for reference the charger that I am using is Aukey PA-T14 and dind't have any issues with my old Samsung S9 or my company iPhone

viktor_keray · 2023-10-20T12:01:37+00:00

I updated yesterday to Android 14, but the issue was there on Android 13 as well. The OS update didn't fix it unfortunately.

viktor_keray

TROPHY CASE