usb_serial_jtag_write_bytes() doesn't always write all bytes

[jmadsenee]

I am using esp_idf V4.4. When I run usb_serial_jtag_write_bytes() in a loop to transfer data to my PC running Tera Term, it works well for random amounts of data, then only sends part of the data buffer. I try to run:

Code: Select all

for (n = 0; n < 500; n++)
{
sentbytes = usb_serial_jtag_write_bytes((char *)packet_data, 1029, 1000/portTICK_RATE_MS);
// wait for ACK
}

After some number (could be n = 10 or could be n = 234) it does not write all 1029 bytes. sentbytes always = 1029, but the number of bytes received by the PC is something less than that.

Does anyone have some idea what might be going wrong, or how to troubleshoot further?

Thanks!

[ESP_Sprite]

Is there any particular data that triggers that behaviour?

[jmadsenee]

Not as far as I can tell. I have had problems transferring a few different file types, jpg, txt, csv. Most of my testing has been with a plain text file, no formatting. It stops in random places in the middle of the text file, sending 204kB one time, 96kB then next, then 159kB, etc. Looking at the parts of files transferred, it stops at different letters, different parts of words, etc.

[jmadsenee]

A little more info: If, after the ESP32-S3 stops sending data part way through (char *)packet_data, I send a space character:

Code: Select all

usb_serial_jtag_write_bytes(" ", 1, 1000/portTICK_RATE_MS);

the remainder of packet_data is transmitted with the space appended to the end. It picked up exactly where it left off; no missing characters.

[ESP_Sprite]

What chip is this on? Any chance you can whittle down your code to the smallest project that still exhibits it and post that here?

[jmadsenee]

I am using a heavily modified ESP32-S3 Korvo-2 board with a ESP32-WROOM-1 MON16R8 module. The UART was disconnected and the USB Serial JTAG connected to the UART connector. The code is pretty complex at this point, but I can try to whittle it down.

Another thing I tried: I looked at the value being returned by xRingbufferSend() in usb_serial_jtag_write_bytes(). It doesn't indicate failure when the buffer stops sending.

[jmadsenee]

Attached is usb_serial_problem.zip the whittled down code in the FortisKap folder and test.txt, my test file. test.txt goes on an SD card on the korvo-2 board. In a terminal program (I'm using Tera Term) type "send test.txt" at the FortisKap> prompt and and start YModem receive on host.

usb_serial_problem.zip

(583.64 KiB) Downloaded 460 times

[horatio]

Serial comms can be pretty slow. I don't have a lot of experience with esp boards, but I have seen it on STM32 projects where not all the data would be transmitted, despite saying it had. 1000+ bytes is a reasonable chunk of data, and depending on the speed of your serial line, that could potentially be taking too long to send before something is cutting it off?


also do you have a scope? could you probe the lines to see if it is actually being sent or not?

[ESP_Sprite]

@horatio Note that there's no physical serial line involved here. The USB-serial-JTAG acts as USB on the side of the PC and (kinda) ESP32, but the communication is all over USB. Things like baud rate can be set, but transmissions are always as-fast-as-USB-allows.

[jmadsenee]

hi @ESP_Sprite, any ideas of what might be causing the ring buffer to stop sending? Any thoughts on further troubleshooting?