From: Anthony Massa <amassa@logici.com>
To: "Jonathan Larmour (E-mail)" <jlarmour@redhat.co.uk>
Cc: "eCos (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Re: RedBoot
Date: Fri, 27 Apr 2001 15:06:00 -0000 [thread overview]
Message-ID: <281963D01A08D511A5D700A0C9AC979A04EF02@EXCHANGE> (raw)
>Perhaps the cygwin tools aren't in the path. Have you installed the .reg
>file mentioned in "Updated configuration tools for Windows" at
> http://sources.redhat.com/ecos/anoncvs.html ?
I'll give that a try. I didn't notice the reg file back when I switched to
ConfigTool 1.3.1.2.
>> Not being able to run the tests, I tried to get more insight as to where
my
>> application was failing. I find that it is failing in the function
>> quicc_eth_init in if_quicc.c. This is called from cyg_net_init, in the
for
>> loop after the thread (cyg_netint) is created and started. I have had
some
>> troubles with GDB crashing while stepping through various parts of the
>> quicc_eth_init routine - once it crashed when stepping over
HAL_DCACHE_SYNC.
>> It seems to have problems with the cyg_drv_interrupt_unmask function
call.
>Looking at it, the problem may be that the interrupts are set up so near
>the start. This means that any interrupts received before the init function
>finishes could lead to problems because the rest of the driver hasn't been
>initialised. And if RedBoot had been using the eth device, interrupts
>_would_ already be enabled.
>Try setting up the interrupt handling much closer to the end, or perhaps
>just try turning off interrupts throughout that function just to see if
>that helps.
I'll move the interrupt creation and unmasking to the end of the
quicc_eth_init function and see what happens. I'm not sure about that
because I have seen it fail at various points through that routine. If that
doesn't work I'll give globally turning off interrupts a try and see where
that leads - although, won't that have an effect on GDB's communication?
I'm a little confused how the Ethernet switch over occurs since I'm
debugging over the Ethernet port as well. Basically, RedBoot is receiving
debug packets from GDB over the Ethernet port while I am stepping through
the quicc_eth_init routine to setup control of the same Ethernet port for
the application.
--Anthony
next reply other threads:[~2001-04-27 15:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 15:06 Anthony Massa [this message]
2001-04-27 15:25 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 10:04 Anthony Massa
2001-04-26 21:44 Anthony Massa
2001-04-27 11:32 ` Jonathan Larmour
2001-04-25 21:59 [ECOS] RedBoot Anthony Massa
2001-04-26 4:15 ` Hugo Tyson
2001-04-23 12:35 [ECOS] RedBoot Anthony Massa
2001-04-23 12:47 ` Jonathan Larmour
2001-04-23 12:09 [ECOS] RedBoot Jonathan Larmour
2001-04-24 8:02 ` [ECOS] Anthony Massa
2001-04-24 8:11 ` [ECOS] Re: RedBoot Jonathan Larmour
2001-04-24 8:13 ` [ECOS] RedBoot Anthony Massa
2001-04-24 8:30 ` Hugo 'NOx' Tyson
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=281963D01A08D511A5D700A0C9AC979A04EF02@EXCHANGE \
--to=amassa@logici.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@redhat.co.uk \
/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).