I too am trying to make a simple device that has bulk in and out with some custom descriptors.
That link looks most encouraging yet, I'll see what I can do.
But if you did make progress, that would be great.
Search found 14 matches
- Wed Nov 26, 2025 3:47 pm
- Forum: General Discussion
- Topic: TinyUSB Vendor class device
- Replies: 7
- Views: 8295
- Thu Oct 02, 2025 11:40 am
- Forum: ESP-IDF
- Topic: ESP32S3 proper UART Serial/JTAG usage
- Replies: 10
- Views: 10159
Re: ESP32S3 proper UART Serial/JTAG usage
Hmm usb_serial_jtag_read_bytes is working, so using that for now. Sorry to bother.
- Thu Oct 02, 2025 11:24 am
- Forum: ESP-IDF
- Topic: ESP32S3 proper UART Serial/JTAG usage
- Replies: 10
- Views: 10159
Re: ESP32S3 proper UART Serial/JTAG usage
It's now 2025, and I am trying to get two way console on and ESP32-S3 using the USB (serial/JTAG).
This is *not* working for me, sadly, and I am, struggling to find any resources to explain it.
Any clues would be appreciated.
This is *not* working for me, sadly, and I am, struggling to find any resources to explain it.
Any clues would be appreciated.
- Tue Sep 23, 2025 2:46 pm
- Forum: General Discussion
- Topic: ESP32-S3-USB-OTG Dev Board to Flash another ESP32-S3
- Replies: 5
- Views: 3435
Re: ESP32-S3-USB-OTG Dev Board to Flash another ESP32-S3
You say that worked, but what was the answer.
I am doing something similar to make a factory flasher and ATE, and just trying to get to putting in download mode now over USB.
Can you post what worked?
I am doing something similar to make a factory flasher and ATE, and just trying to get to putting in download mode now over USB.
Can you post what worked?
- Thu Dec 19, 2024 9:21 am
- Forum: Report Bugs
- Topic: Random boot failure depending on .flash.text size
- Replies: 8
- Views: 24880
Re: Random boot failure depending on .flash.text size
I have started seeing the same. It went away (probably because I was adding log lines).
I can confirm, just adding a log line fixed it. i.e. many builds, fullclean, checking sdkconfig, etc, no help, add one log line, and fine.
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce2810,len:0xdc
load ...
I can confirm, just adding a log line fixed it. i.e. many builds, fullclean, checking sdkconfig, etc, no help, add one log line, and fine.
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce2810,len:0xdc
load ...
- Thu Jul 08, 2021 1:02 pm
- Forum: ESP-IDF
- Topic: mbedtls definitely corrupting memory using dynamic buffers
- Replies: 0
- Views: 1790
mbedtls definitely corrupting memory using dynamic buffers
Cloned new esp-idf lastest today 2021-08-21, git show says commit c13afea635adec735435961270d0894ff46eef85
I have tracked down to esp-idf/components/mbedtls/port/dynamic/esp_mbedtls_dynamic_impl.c line 380
Allocates 637 bytes in my case, when freed there is data written past the end of the buffer ...
I have tracked down to esp-idf/components/mbedtls/port/dynamic/esp_mbedtls_dynamic_impl.c line 380
Allocates 637 bytes in my case, when freed there is data written past the end of the buffer ...
- Wed Jun 30, 2021 10:43 am
- Forum: ESP-IDF
- Topic: TLS memory leak
- Replies: 0
- Views: 2018
TLS memory leak
ESP IDF commit c13afea635adec735435961270d0894ff46eef85
I have mqtt with reconnect over TLS. However, if the connection fails uncleanly it loses around 5k of RAM and eventually says it cannot connect.
Does TLS have a memory leak?
E.g.
E (2564535) MQTT_CLIENT: mqtt_message_receive: transport ...
I have mqtt with reconnect over TLS. However, if the connection fails uncleanly it loses around 5k of RAM and eventually says it cannot connect.
Does TLS have a memory leak?
E.g.
E (2564535) MQTT_CLIENT: mqtt_message_receive: transport ...
- Fri Jan 10, 2020 5:49 pm
- Forum: ESP IoT Solution
- Topic: esp_image: invalid segment length 0xffffffff
- Replies: 11
- Views: 48814
Re: esp_image: invalid segment length 0xffffffff
FYI, I had this, and it was caused by TCP closing the OTA early on and hence an invalid image, which in turn was caused by low dynamic memory. I only had 15k of free memory and that was not enough - but no clue or warning from debug logs to tell me why TCP had closed the connection!
- Thu Aug 29, 2019 12:14 pm
- Forum: ESP-IDF
- Topic: MQTT client hanging on stop/destroy after connect fail
- Replies: 1
- Views: 3815
MQTT client hanging on stop/destroy after connect fail
v4.1-dev-104-gaa087667d
If MQTT fails to connect (in this case it is cert parse issue), then trying esp_mqtt_client_stop or esp_mqtt_client_destroy just hang!
This is how MQTT failed, for reference. Probably my mistake in the cert.
[Codebox]E (4543) esp-tls: mbedtls_x509_crt_parse returned -0x2780 ...
If MQTT fails to connect (in this case it is cert parse issue), then trying esp_mqtt_client_stop or esp_mqtt_client_destroy just hang!
This is how MQTT failed, for reference. Probably my mistake in the cert.
[Codebox]E (4543) esp-tls: mbedtls_x509_crt_parse returned -0x2780 ...
- Thu Aug 29, 2019 10:58 am
- Forum: ESP-IDF
- Topic: Cannot build boot loader (esp_efuse_utility_burn_efuses missing esp_clk_apb_freq)
- Replies: 8
- Views: 10603
Re: Cannot build boot loader (esp_efuse_utility_burn_efuses missing esp_clk_apb_freq)
OK menuconfig works on linux but not on Mac