Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, the high read latency on UART-A (ttyLP3) and UART-C (ttyLP2) compared to UART-B (ttyLP0) on the Colibri-IMX8X could be due to several factors. Here are some potential areas to investigate and steps to consider:
-
UART Configuration: Double-check the configuration settings for UART-A and UART-C. Ensure that the termios settings are correctly applied and consistent with those of UART-B. Pay special attention to the
c_cflag
,c_iflag
,c_oflag
, andc_lflag
settings. -
Driver and Kernel: There might be differences in how the kernel or the UART driver handles these specific UART interfaces. Check if there are any known issues or patches related to UART handling in the BSP version you are using (BSP 7.0).
-
Hardware Differences: Since you are using a custom carrier board, verify if there are any hardware differences or additional components (e.g., RS-485 transceivers) that might affect the performance of UART-A and UART-C.
-
System Load and Interrupt Handling: Although you mentioned there is no other load on the system, ensure that the interrupt handling for these UARTs is not being delayed or blocked by other processes. You might want to check the system’s interrupt configuration and priorities.
-
Testing with Different Drivers: If possible, test with different UART drivers or configurations to see if the issue persists. This might help identify if the problem is driver-related.
-
Consult Toradex Support: Since this issue is critical for your application, consider reaching out to Toradex support for further assistance. They might have more insights or specific patches for the Colibri-IMX8X platform.
If these steps do not resolve the issue, further investigation into the specific hardware and software environment might be necessary.
Please, also check if these links can help you solve your problem: