Hmm... I changed the printf to the alternate port to a uart_1_puts(XXX) and it worked. So I don't think the issue is in the simulator. It has something to do with my (ab)use of avr-libc. Can someone look at that who knows more than I do about avr-libc and see why it wouldn't push all the date down to the putchar routine on both ports?
Thanks. --joel Joel Sherrill wrote:
Hi, I have modified and committed the feedback example to try to write to both usarts. It appears there is an issue with this. Of course, it could always be me. :( I can't find a way to mix the output to the two ports to vary this. Which ever port is written first will only get a single character and then all output will go to the other one. From what I can read of a trace, it looks like no other IRQs occur on the port which gets 1 character. This can be duplicated after updating with "make do" I wish I had an idea what to suspect but I don't. How are these two separate USART instances related to one another? Any ideas where to poke?
-- Joel Sherrill, Ph.D. Director of Research & Development [email protected] On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 _______________________________________________ Simulavr-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/simulavr-devel
