public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: Input from debug console
Date: Thu, 30 Jun 2016 17:52:00 -0000	[thread overview]
Message-ID: <nl3m6r$u1f$1@ger.gmane.org> (raw)
In-Reply-To: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02CA18FD@exchange>

On 2016-06-30, Michael W. Ellis <mellis@pesa.com> wrote:
>> -----Original Message-----
>> From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
>> owner@ecos.sourceware.org] On Behalf Of Michael W. Ellis
>> Sent: Thursday, June 30, 2016 9:54 AM
>> To: ecos-discuss@ecos.sourceware.org
>> Subject: [ECOS] Input from debug console
>> 
>> My application calls diag_printf() to display information to the debug
>> console using serial port 0 of my processor.  I would like to be able
>> to implement some simple diagnostics that are initiated through the
>> console port.  Is it possible to accept input from the console?  If
> so,
>> how is this done?
>
> Correction - I'm using the AT91SAM9260 processor and the debug console
> uses a serial port connected to the Debug Unit instead of serial port 0.
> The console device name is "/dev/ttydiag".  Without writing new drivers,
> is it possible to get simple input from this port?

Does your eCos HAL profide hal_if_diag_read_char()?  I thought that
was pretty standard.  I modified my HAL to also provide a non-blocking
version of that call -- it only required writing a few lines of code.

-- 
Grant





-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      parent reply	other threads:[~2016-06-30 17:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 13:29 [ECOS] cyg_flag_timed_wait doesn't seem to work as expected Michael W. Ellis
2016-05-27 15:53 ` AW: " Richard Rauch
2016-05-27 16:31 ` Nick Garnett
2016-05-27 20:46   ` Michael W. Ellis
2016-06-16 13:26 ` [ECOS] eCos Configuration Tool clewan and rebuild Michael W. Ellis
2016-06-16 17:09   ` [ECOS] " Grant Edwards
2016-06-16 21:18     ` Michael W. Ellis
2016-06-16 21:41       ` Grant Edwards
2016-06-16 23:05         ` Alex Schuilenburg
2016-06-17  4:05           ` AW: " Richard Rauch
2016-06-17 10:10             ` Alex Schuilenburg
2016-06-18 12:01               ` AW: " Richard Rauch
2016-06-18 13:20                 ` Alex Schuilenburg
2016-06-30 14:53         ` [ECOS] Input from debug console Michael W. Ellis
2016-06-30 16:01           ` Michael W. Ellis
2016-06-30 16:09             ` Evgeniy Dushistov
2016-06-30 17:52             ` Grant Edwards [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='nl3m6r$u1f$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).