A bit of speculation:
1. Perhaps the read loop gets interrupted by another task? Try wrapping the loop in taskENTER_CRITICAL/taskEXIT_CRITICAL calls.

2. Perhaps you are observing on card buffering? Maybe test with a different SD card.

Look for an ESP-Prog board. For more detail also read through Espressif's JTAG debugging guide. The ESP-Prog uses an FT2232H USB bridge chip, so you can also use a simple breakout board with an FT2232H or FT232H chip. Other JTAG adapter options that can be used with OpenOCD: https://openocd.org/doc ...

You need to connect a debug probe to the jtag pins, see https://docs.espressif.com/projects/esp ... -jtag.html

As mentioned, use a hardeware peripheral to generate the step pulses:
https://docs.espressif.com/projects/esp-idf/en/v5.3.1/esp32/api-reference/peripherals/mcpwm.html

Also use a stepper driver board such as A4988 (cheap) or DRV8825 (more features) for fancy functionality such as micro stepping and ...

In the ISA summary for LX architectures, there is a section (10.1.4 Argument passing) that states:
All arguments consist of an integral number of 4-byte words. Thus, the minimum argument size is one word. Integer values smaller than a word (that is, char and short) are stored in the least ...

To see more debug information add -d to the openocd command line. Hopefully the cause will be revealed in the more information dense output.

Just a guess - is an I2C bus error causing a stall in communication? Are you tracking the status of each I2C call? Does the problem persist after a power cycle to all components (since this will clear the I2C state of all I2C components)? Do you ensure that the I2C communication between the two ...

Can you trace TX & RX signals at the Esp32 when the radio is switched on? There may be stray noise that interferes with the reception of the serial data. At this low baud rate you don't need a fancy scope.

As a side note: the differences in generated assembly between the two tools are due in part to different scanning algorithms. See e.g. this StackExchange discussion: https://reverseengineering.stackexchange.com/a/2581

All my COM ports are working good but when I connect both in my computer occurs an error.

Not a lot of detail to work with. What is the error message? What software are you using to communicate with the serial ports?