The problem I am having with these modules is that the original/old version of firmware resets the attached ESP32 target device every time I try to connect to the serial port.
This happens with "idf.py monitor" as well as when using "Serial" or "Putty" on macOS.
And the reset makes it impossible to investigate the status of the target device at random times over a long term monitoring/debugging session.
I forked the latest esp-usb-bridge repo, created a config for the pins of the ESPLink board and built a new version of latest firmware.
Whilst trying to figure out how to flash the new firmware I found the message in #5 referring to the 6 micro sized pads at the bottom of the USB-C connector.
In order to determine whether it is viable to try and update the firmware on these boards I need some info.
a) Can I please have the 6 pins identified by function?
b) Is there some kind of standard header than could be used to connect to these pins thus avoiding having to solder 6x discreet wires to the six pins?
The problem I am having with these modules is that the original/old version of firmware resets the attached ESP32 target device every time I try to connect to the serial port.
This happens with "idf.py monitor" as well as when using "Serial" or "Putty" on macOS.
And the reset makes it impossible to investigate the status of the target device at random times over a long term monitoring/debugging session.
I forked the latest esp-usb-bridge repo, created a config for the pins of the ESPLink board and built a new version of latest firmware.
Whilst trying to figure out how to flash the new firmware I found the message in #5 referring to the 6 micro sized pads at the bottom of the USB-C connector.
In order to determine whether it is viable to try and update the firmware on these boards I need some info.
a) Can I please have the 6 pins identified by function?
b) Is there some kind of standard header than could be used to connect to these pins thus avoiding having to solder 6x discreet wires to the six pins?