From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32517 invoked by alias); 1 Mar 2007 06:08:12 -0000 Received: (qmail 32506 invoked by uid 22791); 1 Mar 2007 06:08:12 -0000 X-Spam-Check-By: sourceware.org Received: from www.mcmanis.com (HELO www.mcmanis.com) (66.125.189.29) by sourceware.org (qpsmtpd/0.31) with SMTP; Thu, 01 Mar 2007 06:08:07 +0000 Received: (qmail 84459 invoked from network); 1 Mar 2007 06:08:06 -0000 Received: from unknown (HELO manowar.mcmanis.com) (192.168.110.32) by 192.168.110.40 with SMTP; 1 Mar 2007 06:08:06 -0000 X-Orig-IP: 192.168.110.32 Message-Id: <6.1.2.0.2.20070228220517.0494bec0@192.168.110.40> X-Sender: X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Thu, 01 Mar 2007 06:08:00 -0000 To: ECOS Discussion Group From: Chuck McManis In-Reply-To: <45E41ECA.8010405@mlbassoc.com> References: <45E2F53A.7090403@mlbassoc.com> <6.1.2.0.2.20070226203615.0447f8b8@192.168.110.40> <45E41ECA.8010405@mlbassoc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Proper Thread Environment (was Re: [ECOS] SPI usage) X-SW-Source: 2007-03/txt/msg00002.txt.bz2 Hmm, I'm getting closer, kind of. At 04:06 AM 2/27/2007, Gary Thomas wrote: > Your problem is not with the form of your code; it's fine. >The problem has to do with the console device. The default console >device is the debug device, normally provided by RedBoot via the >virtual vector interface. This interface is not interrupt driven, >thus when you ask to read from it, everything comes to a grinding >halt. To avoid this, you need to set up your console stream to >an interrupt driven device, which will require enabling the appropriate >serial driver. So after much trial and tribulation (why would ANYONE layout a 10 pin IDC connector for a 9 pin serial port with pin 1 - 1, 2-2, 3-3, etc. It makes using off the shelf IDC connectors impossible!) I've got a second serial port on my box that I can talk to. So how do I make *that* stdin/stdout (or their equivalent) for my application? I'd like to maintain the flexibility of having the Redboot serial port which I can connect to and run GDB on. The documentation for the serial driver is not much help, I'm looking in the C-library documentation at the moment but if someone knows off the top of their head, please let me know... --Chuck -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss