Serial2.write

[0x0fe]

Hello,
I noticed something strange, i used your core since it has the fixes for Serial.available, but i noticed something rather strange. I used CH32X035, Serial (which is attached to Serial1) is working fine for debug (i did not test receive), i also have a device on UART2 (PA2 PA3).
On Serial2, the receive works fine, no problem, but whenever i use Serial2.write, it sends the datas to Serial (Serial1) instead of Serial2. Do you have an idea of what could cause this? i digged into the core sources but there is quite a bit of wrappers layers and it is unclear where exactly is Serial2.write hooked to the actual low level USART_SendData

[0x0fe]

Oh, i see the problem

write calls uart_debug_write which is hardcoded to whatever serial was set for debug, which is not correct as soon as we have more than 1 instance.

[maxint-rd]

In PR 201 of the WCH core I added support for two simultaneous UARTS. It also includes PR 180, which addresses that specific issue (of using uart_debug_write instead of correct hardware).

My PR only implements interrupts for two UARTs, no more than that. The PR by @jobitjoseph supports up to 8 UARTs. Updating my PR to also support the maximum number is still on my wish list, but there's other things I also still want to do, so I may not get to do it until I have a direct need for it.