public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] spurious interrupt on EDB7211
@ 2000-06-21  8:17 Nick Barnes
  2000-06-21  8:24 ` Gary Thomas
  0 siblings, 1 reply; 2+ messages in thread
From: Nick Barnes @ 2000-06-21  8:17 UTC (permalink / raw)
  To: ecos-discuss

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* RE: [ECOS] spurious interrupt on EDB7211
  2000-06-21  8:17 [ECOS] spurious interrupt on EDB7211 Nick Barnes
@ 2000-06-21  8:24 ` Gary Thomas
  0 siblings, 0 replies; 2+ messages in thread
From: Gary Thomas @ 2000-06-21  8:24 UTC (permalink / raw)
  To: Nick Barnes; +Cc: ecos-discuss

On 21-Jun-00 Nick Barnes wrote:
> 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?
> 

Did you install CygMon or the basic GDB stubs?   If CygMon, try stubs.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-06-21  8:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-06-21  8:17 [ECOS] spurious interrupt on EDB7211 Nick Barnes
2000-06-21  8:24 ` Gary Thomas

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).