From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Anthony Massa" To: Cc: , Subject: RE: [ECOS] Serial Console Date: Tue, 20 Jun 2000 08:22:00 -0000 Message-id: <000801bfdaca$dd9c4c00$0c0cbcc0@machine1dsktp.cts.com> References: X-SW-Source: 2000-06/msg00217.html I have tried this method. I connected hyperterminal and tried to get output from the program. I load the program into RAM using EPPC-bug firmware and then enter the GO command to get it to execute the downloaded ecos code. The first line in my cyg_user_start is a printf. I tried changing this to diag_printf and even using cyg_io_write using the /dev/ser1 (SMC1 port). However, I still cannot get output from the target MBX board. Do you have an .ecc configuration that you were able to get running without GDB on a target MBX board? Do you know what else I should enable/disable in the ecos configuration that I might be overlooking? -----Original Message----- From: jskov@redhat.com [ mailto:jskov@redhat.com ] Sent: Tuesday, June 20, 2000 6:40 AM To: amassa@cts.com Cc: jlarmour@redhat.co.uk; ecos-discuss@sourceware.cygnus.com Subject: Re: [ECOS] Serial Console >>>>> "amassa@cts" == amassa@cts com writes: amassa@cts> Is there a way to communicate from a terminal or GDB to amassa@cts> the serial code directly. What I want to do is to be able amassa@cts> to enter commands from a terminal and have a task running amassa@cts> on my target get the command and parse it out. You need to do it from a terminal as GDB does not allow you to send out data (well, you could use the maintenance command if you really want to go through GDB). As for the target side, launch a thread which opens /dev/ser0 or similar and read in characters. Parse them whichever way you want. If you want a line-based interface you could use /dev/tty0 instead (I think). Jesper