Re: [ECOS] eCos tools binary installation under Cygwin

["Ling Su" <lingsu at palmmicro dot com>]

Hi, Jifl,

Do you ever meet following errors when you run pci1.exe test, following is
what I met even I use the most updated cvs release, it is the same as
before. The PCI bus scan failed for a SIGBUS bus error...Could you please
take a look? Thanks!

Regards,
-Ling

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
(gdb) set remotebaud 38400
(gdb) target remotebaud /dev/ttyS0
Undefined target command: "remotebaud /dev/ttyS0".  Try "help target".
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
0x80003a50 in ?? ()
(gdb) load
Loading section .rom_vectors, size 0xb4 lma 0x80100000
Loading section .text, size 0xd8b0 lma 0x801000b4
Loading section .ctors, size 0x28 lma 0x8010d964
Loading section .dtors, size 0x14 lma 0x8010d98c
Loading section .rodata, size 0x7c9c lma 0x8010d9a0
Loading section .data, size 0xa204 lma 0x80115640
Start address 0x801000a4 , load size 129088
Transfer rate: 27176 bits/sec, 502 bytes/write.
(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 3]

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

    GDB is unable to find the start of the function at 0x80104820
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 0x80104820 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.
0x80104820 in ?? ()
    at
/opt/ecos_cvs/ecos/packages/language/c/libc/startup/current/src/cstartup.cxx
:98
98
CYGBLD_ATTRIB_INIT_PRI(CYG_INIT_LIBC);(gdb)