-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB-JTAG pin19 and pin20 to be used as GPIO #10587
Comments
Idk if it is possible at all to get this restricted GPIOs glitch free. In short not possible with Arduino "only" |
There should be no problem using pins 20 and 19 from S3. |
I placed |
It doesn't work like that (it can't be defined in the sketch). Maybe @Jason2866 can help it. |
i am using platformio on vs code, below is my platformio.ini data |
This:
uses any Arduino version Platformio founds. You don't know if this is the latest. I highly doubt.
The board you have specified use this settings
for sure wrong regarding USB. To help what exactly S3 variant does you have. |
|
16MB QIO Flash and 8MB OPI PSRAM |
i placed the following contents on the platformio.ini file but i think USB-JTAG didnot disable, board_build.arduino.memory_type = qio_opi build_flags = i wrote the follwing line in void loop, here pin20 worked as gpio, pin20 blinking but impact other other code, other code didnot run. did you get the point where it stuck? thanks |
@muzahid13 Therefore, should we close this issue? |
but if i dont use pin19 and 20 as gpio, my other code works good. only impact appeared on other code when i use pin19 and 20 as GPIO. /*******************************************************************************
#include <Arduino.h> #define TX1_PIN 17 #define TX_PIN 43 #include <Arduino_GFX_Library.h> /* More dev device declaration: https://github.com/moononournation/Arduino_GFX/wiki/Dev-Device-Declaration */ /* More data bus class: https://github.com/moononournation/Arduino_GFX/wiki/Data-Bus-Class */ /* More display class: https://github.com/moononournation/Arduino_GFX/wiki/Display-Class */ Arduino_ESP32RGBPanel bus = new Arduino_ESP32RGBPanel(
#endif /* !defined(DISPLAY_DEV_KIT) /
/*******************************************************************************
/* Display flushing */ #if (LV_COLOR_16_SWAP != 0) lv_disp_flush_ready(disp); void my_touchpad_read(lv_indev_drv_t *indev_driver, lv_indev_data_t *data)
} void setup() ledcSetup(0, 300, 8); //ledcAttach(uint8_t pin, uint32_t freq, uint8_t resolution); ledcWrite(0, 255); /* Screen brightness can be modified by adjusting this parameter. (0-255) */ #endif // Init touch device screenWidth = gfx->width();
// Serial0.println("Setup done"); } uint32_t preMillis_Sent = 0; uint8_t CDbelongTo[32]= {0x02, 0x29, 0x03, 0xE9, 0x37,'A','d','h','a','m','A','d','h','a','m','A','d','h','a','m','A',0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0xF6}; void loop() pinMode(20,OUTPUT); for the above code my lvgl code is stuck when pin20 is active as GPIO but if i remove pin20 gpio code, my lvgl code is working good. could you please help to solve this? |
Board
esp32-s3
Device Description
i am using esp32-s3 based LVGL 7 inch display. I need to use the USB-JTAG pin19 and pin20 as gpio. i already prepared the PCB. i just made high and low pin20 at regular interval, then i noticed that it impacted on other code, i am using visual studio code platformio and framework: arduino.how can i disbale usb-jtag in platformio and framework arduino. my code is completed, i stuck on pin19 and pin20 to be gpio. thanks
Hardware Configuration
GPIO pin19 and pin20 are connected to max485 D-enable and R-enable pin. so those pin shoudl be used as GPIO pin
Version
latest master (checkout manually)
IDE Name
PlatformIO
Operating System
Windows11
Flash frequency
40Mhz
PSRAM enabled
yes
Upload speed
115200
Description
pin19 and pin20 must be used as GPIO. when i enable PIN19 and 20 as GPIO, the code impact on other portion like the mcu is hanged
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: