public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: 'Gary Thomas' <gthomas@redhat.com>
Cc: "Ecos-List (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Ctrl-C/Break with RedBoot, GDB and TCP
Date: Thu, 26 Oct 2000 11:35:00 -0000	[thread overview]
Message-ID: <5AF611D83988D4118ACF00E0B10400540557E6@mr-intranet.sdesigns.net> (raw)

> -----Original Message-----
> From: Gary Thomas [ mailto:gthomas@redhat.com ]
> Subject: RE: [ECOS] Ctrl-C/Break with RedBoot, GDB and TCP
[...]
> > So How do we do that ? 
> 
> Does your application include the TCP/IP stack?

No. (Not yet).
 
[...]
 
> If you don't have TCP/IP included in your application, then 
> any interrupts
> from the ethernet device should come into the system via the "default"
> interrupt handler.  This handler should call into RedBoot 
> appropriately.
> 
> Finally, your application needs to have CYGSEM_USE_HAL_MONITOR set for
> any of this to work properly (IIRC).

I think I need CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT too.

I've dome some printf'ing too and the problem is probably the
hal_saved_interrupt_state variable which is used in hal_ctrlc_isr (file
hal_if.c) as an argument to cyg_hal_user_break.

(By the way this variable is declared as a 'struct HAL_SavedRegisters*' and
is transtyped to a 'CYGADDRWORD*' when passed to cyg_hal_user_break which in
turn trantype its argument to plain 'HAL_SavedRegisters*' not a struct... So
far I've only found one arch that defined HAL_SavedRegisters as a struct,
but all define it as a type. It won't compile if you try to access a member
of the struct)

Thanks

-- 
Fabrice Gautier
fabrice_gautier@sdesigns.com 

             reply	other threads:[~2000-10-26 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-26 11:35 Fabrice Gautier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-25  1:22 Fabrice Gautier
2000-10-25  5:07 ` Gary Thomas

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=5AF611D83988D4118ACF00E0B10400540557E6@mr-intranet.sdesigns.net \
    --to=fabrice_gautier@sdesigns.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gthomas@redhat.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).