Comments on: Good old printf() (continued) http://blog.flyingpic24.com/2009/09/30/good-old-printf-continued/ Programming 16 and 32-bit microcontrollers in C. Tue, 07 Feb 2012 23:56:45 +0000 http://wordpress.org/?v=2.2.1 By: c.pergiel http://blog.flyingpic24.com/2009/09/30/good-old-printf-continued/#comment-291 c.pergiel Wed, 30 Dec 2009 16:13:29 +0000 http://blog.flyingpic24.com/2009/09/30/good-old-printf-continued/#comment-291 I am glad I stopped by. I just started a new project: porting some code I wrote a few years ago for an AVR Atmega processor to a new PIC32. Having printf available should make my job much easier. I am glad I stopped by. I just started a new project: porting some code I wrote a few years ago for an AVR Atmega processor to a new PIC32. Having printf available should make my job much easier.

]]> By: pcwood21 http://blog.flyingpic24.com/2009/09/30/good-old-printf-continued/#comment-284 pcwood21 Tue, 20 Oct 2009 07:05:54 +0000 http://blog.flyingpic24.com/2009/09/30/good-old-printf-continued/#comment-284 If you define and configure a baud rate for UART1 in your code, the printf and UART output are run with delay, as it should to properly simulate. The printf command will take the proper cycles to operate. This can mess with stimulus inputs to the UART. I had a printf statement in a receive ISR when I encountered this. I scratched my head for some time until I figured it out by placing breakpoints and watching it work fine without the printf. It wasn't exiting the ISR before the next input byte arrived, and it dropped the rest of the data. If you define and configure a baud rate for UART1 in your code, the printf and UART output are run with delay, as it should to properly simulate. The printf command will take the proper cycles to operate. This can mess with stimulus inputs to the UART. I had a printf statement in a receive ISR when I encountered this. I scratched my head for some time until I figured it out by placing breakpoints and watching it work fine without the printf. It wasn’t exiting the ISR before the next input byte arrived, and it dropped the rest of the data.

]]>