gdb/gdbserver TQM885

gdb/gdbserver TQM885

[oparz]

Hello,
I have a problem on debugging my target board TQM885 (ELDK, Linux
2.4.25) with gdb/gdbserver . My Testprogram is a simple helloworld. The
program itself is running as expected, but its not possible to debug.
Would be very  glad, if anyone can help me. Target and Host are in
different subnets, but this is solved via route add.. command
___________________
Host running gdb:
oparz@linux:~/autoconf_tests/hello_GNU-0.1> gdb ./hello_GNU
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...Using host libthread_db
library "/lib/tls/libthread_db.so.1".

(gdb) target remote 192.168.10.232:5000
Remote debugging using 192.168.10.232:5000
Couldn't establish connection to remote target
Remote sent bad register number 40: 3000ef14;
Packet: 'T0501:7ffffed0;40:3000ef14;'

(gdb)          
__________________________
and the target running gdbserver:

root@/># gdbserver 192.168.2.21:5000 ./hello_GNU
Process ./hello_GNU created; pid = 56
Remote debugging from host 192.168.2.21
readchar: Got EOF
Remote side has terminated connection.  GDBserver will reopen the
connection.
__________________
Any help is very appreciated

Dr. Otto Parzhuber
Munich University of Applied Sciences
Fac. of Precision Engineering

Re: gdb/gdbserver TQM885

[Wolfgang Denk]

In message <3efc373ef4e6.3ef4e63efc37@compuserve.de> you wrote:
>
> I have a problem on debugging my target board TQM885 (ELDK, Linux
> 2.4.25) with gdb/gdbserver . My Testprogram is a simple helloworld. The
> program itself is running as expected, but its not possible to debug.
...
> Host running gdb:
> oparz@linux:~/autoconf_tests/hello_GNU-0.1> gdb ./hello_GNU
> GNU gdb 6.3

That's wrong. You cannot use a native x86 GDB to debug a PowerPC
system.

> Remote sent bad register number 40: 3000ef14;
> Packet: 'T0501:7ffffed0;40:3000ef14;'

Here it's telling you that it has problems to understand the other
architecture.

> Any help is very appreciated

Use the ppc_8xx-gdb that comes with the ELDK instead. And make sure to
read the DULG, especially the hints about setting
solib-absolute-prefix

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
There's no sense in being precise  when  you  don't  even  know  what
you're talking about.                             -- John von Neumann

gdb/gdbserver TQM885

[oparz]

Hello
many thanks for this immediate answer! The problem is solved.

Its always better to read the manual before asking.

Dr. Otto Parzhuber
Munich University of Applied Sciences
Fac of Precision Engineering

Linux doesn't boot on Vertex4 based board.

[Leonid]

Hi:

I'm trying to port Linux on Vertex4 board, similar to Xilinx ML403
(PPC405 hard core). The main differences between my board and ML403 are:

- I'm using UARTLITE, not UART16550 core.
- I have only 32M of PLB_SDRAM (ML403 got 64M of DDR).
- Flash is not in the end of the address space (see boot snapshot
below).
- I have TEMAC instead of EMAC.
- On my board PPC405 is running on 100MHz vs ML403 300MHz.

I can be somewhat confused regarding ML403 characteristics since I don't
have actual ML403 yet - will be getting it in several days.

I successfully ported ML403 u-boot to my board, but couldn't get kernel
to boot. I tried linux-xilinx-26 from Monta Vista server, 2.6.19.2 from
DENX and last 2.6.20 from kernel.org. Latest one already has uartlite
ported, for previous two I tried to port myself. Below please find
typical u-boot output (I enabled DEBUG in cmd_boot file):

U-Boot> run akanfs
TFTP from server 192.168.0.141; our IP address is 192.168.0.213
Filename 'LM200/rel/1.0.1-20/uImage'.
Load address: 0x1000000
Loading:
#################################################################
=20
#################################################################
         #######################################
done
Bytes transferred =3D 862398 (d28be hex)
## Booting image at 01000000 ...
   Image Name:   Linux-2.6.20
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    862334 Bytes =3D 842.1 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Current stack ends at 0x01F966A0 =3D> set upper limit to 0x00800000
## cmdline at 0x007FFF00 ... 0x007FFF9C
memstart    =3D 0x00000000
memsize     =3D 0x02000000
flashstart  =3D 0x22000000
flashsize   =3D 0x00400000
flashoffset =3D 0x00000000
sramstart   =3D 0x00000000
sramsize    =3D 0x00000000
bootflags   =3D 0x00000000
procfreq    =3D    100 MHz
plb_busfreq =3D    100 MHz
ethaddr     =3D 00:01:02:03:FD:71
IP addr     =3D 192.168.0.213
baudrate    =3D 115200 bps
No initrd
## Transferring control to Linux (at address 00000000) ...

I realize that can be 1001 reasons for such behavior, yet I'd appreciate
any ideas you can share with me. I tried use early serial output... no
success.

Thanks,

Leonid.