Hello,
I work with embOS V3.20g for M16C62P with Tasking IDE 3.1r1 Patch5.
(Unfortunately this combination isn’t supported anymore by Segger.)
Our application is using all three UARTs of the M16C uC with a speed of 115.2 kBaud.
Receiving and transmitting is done interrupt driven.
The interrupt priority level of rx and tx interrupt for UART0 is 7.
All interrupts in the application are marked with .
The total system load shown by embOSView is round about 15%.
But for all that from time to time an overrun error for UART0 occurs. And sometimes even communication completely stops. Software re-initialization of UART0 can’t solve the problem. Only a reset of M16C enables communication again.
Any idea? Can this be a hardware problem of M16C?
Waiting for any comments.
Best regards
Hermann
I work with embOS V3.20g for M16C62P with Tasking IDE 3.1r1 Patch5.
(Unfortunately this combination isn’t supported anymore by Segger.)
Our application is using all three UARTs of the M16C uC with a speed of 115.2 kBaud.
Receiving and transmitting is done interrupt driven.
The interrupt priority level of rx and tx interrupt for UART0 is 7.
All interrupts in the application are marked with .
The total system load shown by embOSView is round about 15%.
But for all that from time to time an overrun error for UART0 occurs. And sometimes even communication completely stops. Software re-initialization of UART0 can’t solve the problem. Only a reset of M16C enables communication again.
Any idea? Can this be a hardware problem of M16C?
Waiting for any comments.
Best regards
Hermann