TI-RTOS 2.14.00.10 UART CALLBACK ERROR

My recommendation is not to call UART_read() within its own callback. The driver is now buffered in the background, meaning that you can now call UART_read() to get your data as needed; without needed to setup the UART for the next read. The background buffer's size is adjustable to accommodate larger amount of data if needed.
I've created a bug ID (SDOCM00117841) to create an example to demonstrate this.

This "feature" was removed in 2.12 because it was labeled as a bug due to the risk that calling UART_read() within its own callback can lead to a system or task stack overflow; which can cause some real bad issues. This depended on several factors (some non-deterministic), such as the rate in which data was received, system load, system, and task stack sizes.

Surprising, a lot of folks are requesting this to be re-enabled again so we'll provide it again in TI-RTOS 2.14.01 as "use it at your own risk". Our goal is to come up with an equation/formula that will characterize how much extra task and system stack space you will need to use this feature. As a result it will be expected that you (the user) needs to evaluate your system's worst case scenario and increase the stacks accordingly.

Hi Tom
Thank you so much for your answer.
But the CallBack think it is not working anyway.

"My recommendation is not to call UART_read () Within its own callback"
OK even in version 2.10_01_38 if you do the CallBack crashes.

Really I needed an example that works. I look then waiting some example.

Regards
Aquino

Hi
No solution?

Regards