[ECOS] error connecting to GDB.. (need some more..help)

[ECOS] error connecting to GDB.. (need some more..help)

[Sateesh Soman]

Hi,
I have a similar problem of connecting to the target through GDB using serial.

> Sending packet: $Hc-1#09...Sending packet:
> $Hc-1#09...Sending packet: $Hc-1#09..
> Sending packet: $Hc-1#09...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Sending packet: $qC#b4...Sending packet:
> $qC#b4...Sending packet: $qC#b4...Sendi
> ng packet: $qC#b4...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Sending packet: $qOffsets#4b...Sending packet:
> $qOffsets#4b...Sending packet: $q
> Offsets#4b...Sending packet: $qOffsets#4b...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Couldn't establish connection to remote target
> Malformed response to offset query, timeout
> (gdb)
I have checked both my ports and they are working fine. 
Could you please tell me how this could be resolved?

Here is what I have done.
I have tried connecting GDB in two ways:
1. I have first got the o/p on HyperTerminal and then I disconnect and connect the GDB on the port.
2. I don't open the Hyperterminal et all, I test my target uing ping and when my target replies, I know its booted and try connecting to it through GDB. 

I am able to get the RedBoot> prompt on both the HyperTerminals when I connected to both the COM ports one at a time. Does this confirm that I can connect to the GDB using this port..?

In both the above cases, I get the same error. I have surfed through the mailing lists if some one got a similar kind of error, but I couldn't find a satisfactory reply.

I am using V2.0.2 ConfigTool with latest eCos package (dt: 28-06-01) and my target is a PC. Host is running WinNT. I have built redboot with importing floppy.ecm.

Thanks in Advance,
Sateesh.

____________________________________________________
Buy Feng Shui Package for Rs. 151/- only, at http://shopping.rediff.com/shopping/fengshui_mailer.htm

[ECOS] RE: error connecting to GDB.. (need some more..help)

[Gary Thomas]

On 03-Jul-2001 Sateesh  Soman wrote:
> Hi,
> I have a similar problem of connecting to the target through GDB using serial.
> 
>> Sending packet: $Hc-1#09...Sending packet:
>> $Hc-1#09...Sending packet: $Hc-1#09..
>> Sending packet: $Hc-1#09...Timed out.
>> Timed out.
>> Timed out.
>> Ignoring packet error, continuing...
>> Sending packet: $qC#b4...Sending packet:
>> $qC#b4...Sending packet: $qC#b4...Sendi
>> ng packet: $qC#b4...Timed out.
>> Timed out.
>> Timed out.
>> Ignoring packet error, continuing...
>> Sending packet: $qOffsets#4b...Sending packet:
>> $qOffsets#4b...Sending packet: $q
>> Offsets#4b...Sending packet: $qOffsets#4b...Timed out.
>> Timed out.
>> Timed out.
>> Ignoring packet error, continuing...
>> Couldn't establish connection to remote target
>> Malformed response to offset query, timeout
>> (gdb)
> I have checked both my ports and they are working fine. 
> Could you please tell me how this could be resolved?
> 
> Here is what I have done.
> I have tried connecting GDB in two ways:
> 1. I have first got the o/p on HyperTerminal and then I disconnect and connect the GDB on the
> port.
> 2. I don't open the Hyperterminal et all, I test my target uing ping and when my target replies,
> I know its booted and try connecting to it through GDB. 
> 
> I am able to get the RedBoot> prompt on both the HyperTerminals when I connected to both the COM
> ports one at a time. Does this confirm that I can connect to the GDB using this port..?
> 
> In both the above cases, I get the same error. I have surfed through the mailing lists if some
> one got a similar kind of error, but I couldn't find a satisfactory reply.
> 
> I am using V2.0.2 ConfigTool with latest eCos package (dt: 28-06-01) and my target is a PC. Host
> is running WinNT. I have built redboot with importing floppy.ecm.
> 

Try connecting via hyperterm and typing '$Hc-1#09' by hand.  You should get
something like this: +$OK#9a  (Note, you won't seen anything until the '+'
comes back).  If this works when typed slowly, I would think that your target
can't keep up with data at 38400 when it comes in bursts.  If that is the
case, then you could try rebuilding RedBoot for the target to run GDB at a
slower baudrate.

[ECOS] booting from floppy - target intel ix86 pc

[Srinivasan Sriram]

I'm stuck. Can anyone help me out?

I want to create a boot floopy.
In my build tree , I run -

ecosconfig new pc

ecos.ecc is generated.
I modify the configuration file,
CYG_HAL_STARTUP = FLOPPY
CYGSEM_HAL_ROM_MONITOR =1
I disable all GDB options in the .ecc file.

Then, I run
ecosconfig tree

Then
make

The make process halts with the following error
message.
I paste the last few lines
 -------

make[1]: Entering directory
`/home/ecos/ecos-1.3.1/newecos/hal/i386/arch/v1_3_1'
i386-elf-gcc -Wp,-MD,vectors.tmp 
-I/home/ecos/ecos-1.3.1/newecos/install/include
-I/home/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1
-I/home/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/src
-I/home/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/tests
-I. -Wall -Wpointer-arith -Wstrict-prototypes
-Winline -Wundef -Woverloaded-virtual -g -O2
-ffunction-sections -fdata-sections -fno-rtti
-fno-exceptions -fvtable-gc -finit-priority -c -o
/home/ecos/ecos-1.3.1/newecos/install/lib/vectors.o
/home/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/src/vectors.S
/tmp/ccZ6T5rh.s: Assembler messages:
/tmp/ccZ6T5rh.s:1227: Error: Rest of line ignored.
First ignored character is `3'.make[1]: ***
[/home/ecos/ecos-1.3.1/newecos/install/lib/vectors.o]
Error 1
make[1]: Leaving directory
`/home/ecos/ecos-1.3.1/newecos/hal/i386/arch/v1_3_1'
make: *** [build] Error 2 

----------

What other option in the .ecc files should be set or
reset to generate the build tree successfully?

Thanks
Kavita

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Re: [ECOS] booting from floppy - target intel ix86 pc

[Jonathan Larmour]

Srinivasan Sriram wrote:
> 
> I'm stuck. Can anyone help me out?
> 
> I want to create a boot floopy.
> In my build tree , I run -
> 
> ecosconfig new pc
> 
> ecos.ecc is generated.
> I modify the configuration file,
> CYG_HAL_STARTUP = FLOPPY
> CYGSEM_HAL_ROM_MONITOR =1
> I disable all GDB options in the .ecc file.

No, you need to configure with the "stubs" template., i.e.

ecosconfig new pc stubs

Alternatively you could update to anonymous CVS and use RedBoot, and get
prebuilt binaries from http://sources.redhat.com/ecos/boards/pcmobo.html

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

[ECOS] booting from floppy - target intel ix86 pc

[Srinivasan Sriram]

Hello!
I'm sorry I wasn't very clear the first time.

My intention is to disable remote debugging, load my
hello program on the floppy and boot and run from the
floppy and not remote debugging...something like ....

dd conv=sync if=/home/ecos/ecos-1.3.1/temp/hello.bin
of=/dev/fd0

Strangely I get error while running the make command
for the build tree.

ecosconfig new pc
set startup to floppy.
resolve conflicts.
ecosconfig tree
make

I'm unable to figure out the error during the make -
THE LAST FEW LINES OF THE MAKE ERROR IS FOLLOWS. CAN
ANYONE HELP ME FIGURE IT OUT????

make[1]: Leaving directory
`/home/kavita/ecos/ecos-1.3.1/myecos/hal/common/v1_3_1'
make -r -C hal/i386/arch/v1_3_1
/home/kavita/ecos/ecos-1.3.1/myecos/install/lib/vectors.o
make[1]: Entering directory
`/home/kavita/ecos/ecos-1.3.1/myecos/hal/i386/arch/v1_3_1'
i386-elf-gcc -Wp,-MD,vectors.tmp 
-I/home/kavita/ecos/ecos-1.3.1/myecos/install/include
-I/home/kavita/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1
-I/home/kavita/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/src
-I/home/kavita/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/tests
-I.
-Wall -Wpointer-arith -Wstrict-prototypes -Winline
-Wundef -Woverloaded-virtual -g -O2
-ffunction-sections -fdata-sections -fno-rtti
-fno-exceptions -fvtable-gc -finit-priority -c -o
/home/kavita/ecos/ecos-1.3.1/myecos/install/lib/vectors.o
/home/kavita/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/src/vectors.S
/tmp/ccHNTIng.s: Assembler messages:
/tmp/ccHNTIng.s:1229: Error: Rest of line ignored.
First ignored character is `3'.
make[1]: ***
[/home/kavita/ecos/ecos-1.3.1/myecos/install/lib/vectors.o]
Error 1
make[1]: Leaving directory
`/home/kavita/ecos/ecos-1.3.1/myecos/hal/i386/arch/v1_3_1'
make: *** [build] Error 2  

Thanks



--- Jonathan Larmour <jlarmour@redhat.com> wrote:
> Srinivasan Sriram wrote:
> > 
> > I'm stuck. Can anyone help me out?
> > 
> > I want to create a boot floopy.
> > In my build tree , I run -
> > 
> > ecosconfig new pc
> > 
> > ecos.ecc is generated.
> > I modify the configuration file,
> > CYG_HAL_STARTUP = FLOPPY
> > CYGSEM_HAL_ROM_MONITOR =1
> > I disable all GDB options in the .ecc file.
> 
> No, you need to configure with the "stubs"
> template., i.e.
> 
> ecosconfig new pc stubs
> 
> Alternatively you could update to anonymous CVS and
> use RedBoot, and get
> prebuilt binaries from
> http://sources.redhat.com/ecos/boards/pcmobo.html
> 
> Jifl
> -- 
> Red Hat, Rustat House, Clifton Road, Cambridge, UK.
> Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous
> Huxley || Opinions==mine
> Come to the Red Hat TechWorld open source conference
> in Brussels!
> Keynotes, techie talks and exhibitions   
http://www.redhat-techworld.com/


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Re: [ECOS] booting from floppy - target intel ix86 pc

[Jonathan Larmour]

Srinivasan Sriram wrote:
> 
> My intention is to disable remote debugging, load my
> hello program on the floppy and boot and run from the
> floppy and not remote debugging...something like ....

Okay, for a start don't enable CYGSEM_HAL_ROM_MONITOR then.
 
> make[1]: Leaving directory
> `/home/kavita/ecos/ecos-1.3.1/myecos/hal/common/v1_3_1'
> make -r -C hal/i386/arch/v1_3_1
> /home/kavita/ecos/ecos-1.3.1/myecos/install/lib/vectors.o
> make[1]: Entering directory
> `/home/kavita/ecos/ecos-1.3.1/myecos/hal/i386/arch/v1_3_1'
> i386-elf-gcc -Wp,-MD,vectors.tmp
> -I/home/kavita/ecos/ecos-1.3.1/myecos/install/include
> -I/home/kavita/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1
> -I/home/kavita/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/src
> -I/home/kavita/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/tests
> -I.
> -Wall -Wpointer-arith -Wstrict-prototypes -Winline
> -Wundef -Woverloaded-virtual -g -O2
> -ffunction-sections -fdata-sections -fno-rtti
> -fno-exceptions -fvtable-gc -finit-priority -c -o
> /home/kavita/ecos/ecos-1.3.1/myecos/install/lib/vectors.o
> /home/kavita/ecos/ecos-1.3.1/packages/hal/i386/arch/v1_3_1/src/vectors.S
> /tmp/ccHNTIng.s: Assembler messages:
> /tmp/ccHNTIng.s:1229: Error: Rest of line ignored.
> First ignored character is `3'.

You should find out what this line is. Do this by going into
/home/kavita/ecos/ecos-1.3.1/myecos/hal/i386/arch/v1_3_1 and typing the
above i386-elf-gcc line, but also add "--save-temps". You should then be
pointed at a line number in a file that is kept after the compilation
finishes - the above /tmp/ccGNTIng.s file will always be deleted.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/