public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Cristiano Ligieri Pereira <cpereira@ics.uci.edu>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Frequency scaling and serial interface...
Date: Wed, 25 Jul 2001 10:57:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.20.0107251040430.338-100000@washoe.ics.uci.edu> (raw)

Hi all,

I have an application in which I'm scaling the frequency of compaq ipaq.
I'm also sending messages to GDB (via serial) in order to debug my code. I
can scale the frequency from any level to any level without any problem
for a while and I verify it by means of messages on the console.
Sometimes, however, after a while (10 minutes or more) I either stop
receiving messages on the console or I receive the following message:

"gdb_config:4: Error in sourced command file:
 Reply contains invalid hex digit -2"

I'm assuming that my application is crashing and I've been trying to
modify it for a fews two days without any change in the output (i.e,
unsuccessfully :-( ). Looking carefully in the SA-1110 developer's Manual
I've noticed that changing the core frequency makes the LCD controller,
all serial controllers, the DMA controller and the OS timer to stop.
^^^^^^^^^^^^^^^^^^

Now I'm wondering if the messages are not coming due to this 'stop' in the
serial controller and consequently my application is not actually crashing
(which is gonna be great) but only the communication IPAQ/HOST is being
stopped. Is is possible? I mean, is this a reasonable explanation? If so,
does anyone have a suggestion on how to get away from this problem?

Thanks,
Cristiano.

------------------------------------------------------------
Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira

                 reply	other threads:[~2001-07-25 10:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.SOL.4.20.0107251040430.338-100000@washoe.ics.uci.edu \
    --to=cpereira@ics.uci.edu \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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).