[ECOS] gdb problem

[ECOS] gdb problem

[Ram Sudhir Tadavarthi]

Hello,

Aim:
To get the gdb debugger working 

Target environment:
Platform : Motorola PQ2FADS-ZU Board
Processor: MPC 8280 (predecessor of MPC 8260) Clock frequency : 100MHz

I have built a hello world eCos RAM application (hello.elf,hello.srec from
hello.c). If I load the hello.srec from redboot monitor via tftp and execute
it with "go" command. 

The output on the console is

Init device '/dev/ttydiag'
Init tty channel: 38170
Init device '/dev/haldiag'
HAL/diag SERIAL init
Hello, world!


I tried to load and run the image(hello.elf) over gdb(via network) with the
following commands

$ powerpc-eabi-gdb -nw hello.elf
GNU gdb 5.3 (eCosCentric)
Copyright 2002 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 "--host=i686-pc-cygwin --target=powerpc-eabi"...
(gdb) target remote 192.168.20.238:9000
Remote debugging using 192.168.20.238:9000
0xfff16534 in ?? ()
(gdb) load
Loading section .text, size 0x170e0 lma 0x20000
Loading section .rodata, size 0xb30 lma 0x370e0
Loading section .data, size 0x754 lma 0x37c10
Start address 0x20000, load size 99172
Transfer rate: 72125 bits/sec, 508 bytes/write.
(gdb) continue
Continuing.


And I don't see the output on the console.I wonder why the same RAM
application which runs via redboot load doesn't work with gdb.

I hope it isn't problem with eCos configuration.For reference the "ecc" file
is available at

http://www.yousendit.com/transfer.php?action=download&ufid=DCB915D05E9624A8

I will be obliged if anyone can give me a hint or reference/pointer how to
make gdb work with my application.

Thanks a lot,
Ram


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] gdb problem

[Andrew Lunn]

On Thu, May 18, 2006 at 11:45:32AM +0200, Ram Sudhir Tadavarthi wrote:
> Hello,
> 
> Aim:
> To get the gdb debugger working 
> 
> Target environment:
> Platform : Motorola PQ2FADS-ZU Board
> Processor: MPC 8280 (predecessor of MPC 8260) Clock frequency : 100MHz
> 
> I have built a hello world eCos RAM application (hello.elf,hello.srec from
> hello.c). If I load the hello.srec from redboot monitor via tftp and execute
> it with "go" command. 
> 
> The output on the console is
> 
> Init device '/dev/ttydiag'
> Init tty channel: 38170
> Init device '/dev/haldiag'
> HAL/diag SERIAL init

Try disabling these messages. The ethernet gdb stub can get itself
into knots if it is asked to output messages too soon during booting. 

     Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

AW: [ECOS] gdb problem

[Ram Sudhir Tadavarthi]

Hi,

Thanks a lot for the response.

>> Hello,
>> 
>> Aim:
>> To get the gdb debugger working 
>> 
>> Target environment:
>> Platform : Motorola PQ2FADS-ZU Board
>> Processor: MPC 8280 (predecessor of MPC 8260) Clock frequency : 100MHz
>> 
>> I have built a hello world eCos RAM application (hello.elf,hello.srec
>from
>> hello.c). If I load the hello.srec from redboot monitor via tftp and
>execute
>> it with "go" command. 
>> 
>> The output on the console is
>> 
>> Init device '/dev/ttydiag'
>> Init tty channel: 38170
>> Init device '/dev/haldiag'
>> HAL/diag SERIAL init
>
>Try disabling these messages. The ethernet gdb stub can get itself
>into knots if it is asked to output messages too soon during booting. 

I have disabled the messages but still the same response, no messages on
console.

GNU gdb 5.3 (eCosCentric)
Copyright 2002 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 "--host=i686-pc-cygwin --target=powerpc-eabi"...
(gdb) target remote 192.168.20.238:9000
Remote debugging using 192.168.20.238:9000
0xfff16534 in ?? ()
(gdb) load
Loading section .text, size 0x17068 lma 0x20000
Loading section .rodata, size 0xaa0 lma 0x37068
Loading section .data, size 0x754 lma 0x37b08
Start address 0x20000, load size 98908
Transfer rate: 65938 bits/sec, 507 bytes/write.
(gdb) break main
Breakpoint 1 at 0x205f0: file hello.c, line 5.
(gdb) continue
Continuing.


and the network still works(checked with ping). Any other hint please?

Thank you,
Ram


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

AW: [ECOS] gdb problem

[Ram Sudhir Tadavarthi]

Hi,

>> The output on the console is
>> 
>> Init device '/dev/ttydiag'
>> Init tty channel: 38170
>> Init device '/dev/haldiag'
>> HAL/diag SERIAL init
>
>Try disabling these messages. The ethernet gdb stub can get itself
>into knots if it is asked to output messages too soon during booting. 

I have disabled the messages but still the same response, no messages on
console.

GNU gdb 5.3 (eCosCentric)
Copyright 2002 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 "--host=i686-pc-cygwin --target=powerpc-eabi"...
(gdb) target remote 192.168.20.238:9000
Remote debugging using 192.168.20.238:9000
0xfff16534 in ?? ()
(gdb) load
Loading section .text, size 0x17068 lma 0x20000
Loading section .rodata, size 0xaa0 lma 0x37068
Loading section .data, size 0x754 lma 0x37b08
Start address 0x20000, load size 98908
Transfer rate: 65938 bits/sec, 507 bytes/write.
(gdb) break main
Breakpoint 1 at 0x205f0: file hello.c, line 5.
(gdb) continue
Continuing.


and network still works(checked with ping).

The follwing hal components are included in the RAM application


#ifndef CYGONCE_PKGCONF_HAL_H
#define CYGONCE_PKGCONF_HAL_H
/*
 * File <pkgconf/hal.h>
 *
 * This file is generated automatically by the configuration
 * system. It should not be edited. Any changes to this file
 * may be overwritten.
 */

/***** proc output start *****/
#include <pkgconf/system.h>
#include CYGBLD_HAL_TARGET_H
#ifdef   CYGBLD_HAL_VARIANT_H
#include CYGBLD_HAL_VARIANT_H
#endif
#include CYGBLD_HAL_PLATFORM_H
/****** proc output end ******/
#define CYGPKG_HAL_COMMON 1
#define CYGFUN_HAL_COMMON_KERNEL_SUPPORT 1
#define CYGPKG_HAL_EXCEPTIONS 1
#define CYGINT_HAL_SUPPORTS_MMU_TABLES 0
#define CYGINT_HAL_SUPPORTS_MMU_TABLES_0
#define CYGPKG_HAL_COMMON_INTERRUPTS 1
#define CYGNUM_HAL_COMMON_INTERRUPTS_STACK_SIZE 4096
#define CYGNUM_HAL_COMMON_INTERRUPTS_STACK_SIZE_4096
#define CYGPKG_HAL_COMMON_CONTEXT 1
#define CYGSEM_HAL_ENABLE_DCACHE_ON_STARTUP 1
#define CYGSEM_HAL_DCACHE_STARTUP_MODE COPYBACK
#define CYGSEM_HAL_DCACHE_STARTUP_MODE_COPYBACK
#define CYGSEM_HAL_ENABLE_ICACHE_ON_STARTUP 1
#define CYGPKG_HAL_DEBUG 1
#define CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT 1
#define CYGNUM_HAL_DEBUG_GDB_PROTOCOL_RETRIES 0
#define CYGNUM_HAL_DEBUG_GDB_PROTOCOL_RETRIES_0
#define CYGNUM_HAL_DEBUG_GDB_PROTOCOL_TIMEOUT 500
#define CYGNUM_HAL_DEBUG_GDB_PROTOCOL_TIMEOUT_500
#define CYGDBG_HAL_CRCTABLE_LOCATION RAM
#define CYGDBG_HAL_CRCTABLE_LOCATION_RAM
#define CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT 1
#define CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE 1
#define CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE 1
#define CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_RESET 1
#define CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_VERSION 1
#define CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_DELAY_US 1
#define CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_CACHE 1
#define CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_DATA 1
#define CYGSEM_HAL_VIRTUAL_VECTOR_DIAG 1
#define CYGINT_HAL_PLF_IF_INIT 0
#define CYGINT_HAL_PLF_IF_INIT_0
#define CYGINT_HAL_PLF_IF_IDE 0
#define CYGINT_HAL_PLF_IF_IDE_0

#endif


Is there any mistake in the configuration? Kindly let me know if I miss to
provide any required information. 

Any help is highly appreciated.

Thank you,
Ram


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss