From: Nick Barnes <Nick.Barnes@pobox.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] spurious interrupt on EDB7211
Date: Wed, 21 Jun 2000 08:17:00 -0000 [thread overview]
Message-ID: <29340.961600682@raven.ravenbrook.com> (raw)
Running tests (any tests) on my EDB7211, I get
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
just after the CS8900 is initialized. Any ideas?
Nick Barnes
(gdb) set remotebaud 38400
(gdb) target remote com1
Remote debugging using com1
0xe0006880 in ?? ()
(gdb) load
Loading section .rom_vectors, size 0x60 lma 0x8000
Loading section .text, size 0x1e88c lma 0x8060
Loading section .rodata, size 0xac3 lma 0x268ec
Loading section .data, size 0x97c lma 0x273b0
Start address 0x8060 , load size 130347
Transfer rate: 27441 bits/sec, 305 bytes/write.
(gdb) break cyg_test_exit
Breakpoint 1 at 0xa318: file //D/PROGRA~1/REDHAT~1/eCos/packages/infra/v1_3_1/src/tcdiag.cxx, line 116.
(gdb) break cyg_assert_fail
Function "cyg_assert_fail" not defined.
(gdb) break cyg_test_init
Breakpoint 2 at 0xa220: file //D/PROGRA~1/REDHAT~1/eCos/packages/infra/v1_3_1/src/tcdiag.cxx, line 62.
(gdb) cont
Continuing.
Network stack using 65536 bytes for misc space
65536 bytes for mbufs
131072 bytes for mbuf clusters
Init device 'edb7xxx'
cs8900 init
CS8900 - type: 630E, rev: 700
CS8900 - status: 12D6 (EEPROM present)
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
Spurious Interrupt!!! - vector: 13, data: 0
--
FreeBSD 2.2.8-RELEASE: up 22 days, 23:40
next reply other threads:[~2000-06-21 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-21 8:17 Nick Barnes [this message]
2000-06-21 8:24 ` 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=29340.961600682@raven.ravenbrook.com \
--to=nick.barnes@pobox.com \
--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).