Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3F5A532E.1040707@macdonnell.ca> Date: Sat, 06 Sep 2003 15:35:42 -0600 From: Creighton MacDonnell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Problem with COM1 port from with GDB 5.3 under Cygwin 1.5.3-1 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I upgraded my Cygwin installation two days ago (Thursday, September 4) to the new 1.5.3-1 version, from the previous 1.3.?-? version. This broke a self-compiled (under the previous 1.3.?-? version of Cygwin) version of GDB compiled for "arm-elf" that I use. It seems to me that GDB simply fails to communicate with the COM1 serial when trying to make an "RDI" (Angel Debug) connection. I have recompiled my GNU tools with the with the new version of Cygwin, but I have the same problem. I do not have any Cygwin programs handy that I can use to try to use the COM1 port in some other way. If someone can suggest a simple test, I will try it. Can other people use the COM1 port OK with the new Cygwin? === Unfortunately, I did not back up my Cygwin folder before doing the upgrade - too trusting I guess. Is there an archive somewhere with all of the old stuff that can be used to resinstall the old version? Fortunately, I still have some of the old modules, though - enough to run GDB under the old Cygwin. From this I know that the problem is not with the target board or the serial port on my PC. Thanks. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/