This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

eCos PCI driver for NECvrc4373


Hello,

With a lot of persons' help, finally I can run the eCos-1.3.1 on my NEC
vr4373 board. Because my job is quite related to a PCI board, I tried to
test the PCI driver, acutally I run the "pci1.exe", unfortnately there is a
Bus error, following I post the log messages, is this normal, or something
buggy in eCos?

Thanks!

Regards,
-Ling

<<<Log message for pci1.exe>>>
==========================================================
(gdb) break cyg_test_exit
Breakpoint 1 at 0x80106fb8: file
//D/PROGRA~1/REDHAT~1/eCos/packages/infra/v1_3_1/src/tcdiag.cxx, line 115.
(gdb) break cyg_assert_fail
Function "cyg_assert_fail" not defined.
(gdb) break cyg_test_init
Breakpoint 2 at 0x80106e6c: file
//D/PROGRA~1/REDHAT~1/eCos/packages/infra/v1_3_1/src/tcdiag.cxx, line 62.
(gdb) cont
Continuing.
[New thread 1]
[Switching to thread 1]

Breakpoint 2, cyg_test_init ()
    at //D/PROGRA~1/REDHAT~1/eCos/packages/infra/v1_3_1/src/tcdiag.cxx:62
62 }
Current language:  auto; currently c++
(gdb) set cyg_test_is_simulator=0
Address of symbol "cyg_test_is_simulator" is unknown.
(gdb) cont
Continuing.
Found device on bus 0, devfn 0x00:
 Note that board is active. Probed sizes and CPU addresses invalid!
 Device configuration failed - device already enabled
 Vendor    0x1033 [NEC][NEC Corporation]
 Device    0x001A [UNKNOWN]
 Command   0x0146, Status 0x0280
 Class/Rev 0x06800001 [Bridge Device][Other][]
 Header 0x11FF0E
 SubVendor 0x1111, Sub ID 0xFF19
 BAR[0]    0x1C000000 / probed size 0x00000000 / CPU addr 0x1111FF15
 BAR[1]    0x80000000 / probed size 0x00000000 / CPU addr 0x00000000
 BAR[2]    0x00000000 / probed size 0x00000000 / CPU addr 0x1111FF16
 BAR[3]    0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
 BAR[4]    0x00000000 / probed size 0x00000000 / CPU addr 0x1111FF17
 BAR[5]    0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
 Wired to HAL vector 11
[New thread 2]

Program received signal SIGBUS, Bus error.
[Switching to thread 2]
warning: Warning: GDB can't find the start of the function at 0x80104e7c.

    GDB is unable to find the start of the function at 0x80104e7c
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x80104e7c for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
0x80104e7c in ?? ()
    at
//D/PROGRA~1/REDHAT~1/eCos/packages/io/common/v1_3_1/src/ioinit.cxx:60
60 static cyg_io_init_class _cyg_io_init
CYGBLD_ATTRIB_INIT_PRI(CYG_INIT_IO);
(gdb) *** 20:05:26 Run complete
=================================================


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]