From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Trenton D. Adams" To: "'Cristiano Ligieri Pereira'" , Subject: RE: [ECOS] Debug messages through serial communication port Date: Wed, 29 Aug 2001 09:54:00 -0000 Message-id: <000a01c130ab$23613ac0$090110ac@TRENT> References: X-SW-Source: 2001-08/msg00910.html I have the same problem. It doesn't bother me that much so I haven't bothered to figure out why it's happening. I have a series of diag_printfs with cyg_thread_delays in between. It appears as if all the cyg_thread_delays are run through first, and then the diag_printfs. I don't know why this would happen, but it does. Is this similar to your problem? -----Original Message----- From: ecos-discuss-owner@sources.redhat.com [ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of Cristiano Ligieri Pereira Sent: Wednesday, August 29, 2001 12:06 AM To: ecos-discuss@sourceware.cygnus.com Subject: [ECOS] Debug messages through serial communication port Hi folks, I'm using a bunch of diag_printf messages in order to debug my application running on my new XScale board port. After printing some messages the systems freezes for a while and then continues executing. It looks like some buffer gets full and time is taken to flush it. For a very simple application, which basically loops forever and prints some messages after every tick (using cyg_thread_delay(1)) this is happening. The same application running on the iPaq works fine (and I'm also sending messages through the serial in a 1 tick basis). Any guess on what might be causing my system to freeze? Is there any buffer in which diag_printf messages are put into? Thanks, Cristiano. ------------------------------------------------------------ Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira