Hi Alberto
txs, can you please tell, which base you take?
john have linked yours here, so i am little confuse
http://esp32.com/viewtopic.php?f=2&t=14&#p107
perhabs he do not had valid only link to the pic.
because in some named connectors the name is difficult:
i can not controll all have no docu about - only the RTOS SDK 1.0 Src Code.
one example here can be controll and is showing here in the
base espressif RTOS SDK 1.0
SRC=
https://github.com/espressif/ESP32_RTOS ... _mux_reg.h
take a look to GPIO 15 example:
Code: Select all
..
#define PERIPHS_IO_MUX_MTDO_U (DR_REG_IO_MUX_BASE +0x3c)
#define FUNC_MTDO_U0RTS 3
#define FUNC_MTDO_GPIO15 2
#define FUNC_MTDO_HSPICS0 1
#define FUNC_MTDO_MTDO 0
..
we have U0RTS
The named pin is U0RTS
Your Pic shows U0CTS
- mist1.PNG (96.88 KiB) Viewed 26961 times
btw
U0CTS is named in RTOS SDK 1.0
Code: Select all
..
#define PERIPHS_IO_MUX_MTCK_U (DR_REG_IO_MUX_BASE +0x38)
#define FUNC_MTCK_U0CTS 3
#define FUNC_MTCK_GPIO13 2
#define FUNC_MTCK_HSPID 1
#define FUNC_MTCK_MTCK 0
..
that normaly must be PAD 16, ( GPIO13 ) but your pic shows no named pin for Uart0 CTS
have not controll all, but think there is a little mistake.
Which Base you take for naming the pads?
Because ;- ) we have Bounty Programm and perhabs the linked header file in RTOS SDK have a bug
or yours
..
Info:
RTS = Request to send
CTS = Clear to send
..
( hey i like your work so much! its fun ok! if john tell you this named pin then make a entry in bug bounty program, and john
... 3 : 0 )
best wishes
rudi
Edit:
Picture add
Info add
RTS = Request to send
CTS = Clear to send