From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26323 invoked by alias); 6 Feb 2013 09:47:56 -0000 Received: (qmail 26303 invoked by uid 22791); 6 Feb 2013 09:47:55 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-la0-f41.google.com (HELO mail-la0-f41.google.com) (209.85.215.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 06 Feb 2013 09:47:50 +0000 Received: by mail-la0-f41.google.com with SMTP id fo12so1135757lab.28 for ; Wed, 06 Feb 2013 01:47:48 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.104.199 with SMTP id gg7mr25634046lab.14.1360144068203; Wed, 06 Feb 2013 01:47:48 -0800 (PST) Received: by 10.152.145.72 with HTTP; Wed, 6 Feb 2013 01:47:48 -0800 (PST) Date: Wed, 06 Feb 2013 09:47:00 -0000 Message-ID: From: Andreas Stenius To: ecos-discuss@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1 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: [ECOS] Serial communication issues X-SW-Source: 2013-02/txt/msg00006.txt.bz2 Hi, I've been struggling with this for a few days now, and are initially looking for anyone that recognizes any of this, or maybe have some insights to what may be going on. I'm working on a project based on a custom hardware fitted with a AT91R40008, at 40Mhz. The application is debugged using GDB connected with a JTAG dongle to the board, and this works fine. However, when the application is running from flash using a ROM configuration, I have issues on /dev/ser1. I have a console running on /dev/termios0 (connected to /dev/ser0), and this runs fine in both RAM and ROM. The issues on ser1 is that after I send a request (two bytes) the reply is not always received correctly (or at all, not sure which yet). However, whenever I enable some diagnostic printouts around the calls to cyg_io_write/cyg_io/read, it works ok, so as soon as I affect the timing of the send/read calls, it works. The reply is always consistent and correct on the wire (confirmed with oscilloscope). I have setup ser1 to operate in a non-blocking mode (and no termios on this channel). I'll dig in deeper trying to solve this, just wanted to throw this out here in case someone recognizes any of this.. ;) Oh, and running a eCos version from cvs, 2012-05-27. //Andreas -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss