public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Trenton D. Adams" <tadams@theone.dnsalias.com>
To: "'Jonathan Larmour'" <jlarmour@redhat.com>
Cc: "'eCos Disuss'" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] program doesn't work with new redboot
Date: Mon, 13 Aug 2001 08:35:00 -0000	[thread overview]
Message-ID: <001801c1240d$8371c290$090110ac@TRENT> (raw)
In-Reply-To: <3B7451EE.8ACB70E0@redhat.com>

I recompiled redboot again, and I don't get the ignoring packet error.

My program still locks up though.  I'm going to try and figure it out
myself first.  I do have a question though.

Is there any way that compilation options for redboot would affect the
running of my eCos program?

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of Jonathan
Larmour
Sent: Friday, August 10, 2001 3:28 PM
To: Trenton D. Adams
Cc: 'eCos Disuss'
Subject: Re: [ECOS] program doesn't work with new redboot


"Trenton D. Adams" wrote:
> 
> My program won't work with the new redboot I just compiled.  It does
the
> following.
> 
> $ arm-elf-gdb.exe -nw RigSystem.exe
> GNU gdb 5.0
> Copyright 2000 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=arm-elf"...
> (gdb) set remotebaud 115200
> (gdb) target remote com1
> Remote debugging using com1
> 0xe0006630 in ?? ()
> (gdb) load
> Loading section .rom_vectors, size 0x40 lma 0x20000
> Loading section .text, size 0x389c0 lma 0x20040
> Loading section .rodata, size 0x1a1b8 lma 0x58a00
> Loading section .data, size 0x1194 lma 0x72bb8
> Start address 0x20040 , load size 343372
> Ignoring packet error, continuing...

Just a download error?

> Transfer rate: 80793 bits/sec, 306 bytes/write.
> (gdb) cont
> Continuing.
> Ignoring packet error, continuing...
> Interrupted while waiting for the program.
> Give up (and stop debugging it)? (y or n) y
> (gdb)
> 
> Any ideas?

set debug remote 1

Or just... try again, it could have just been a flaky download, or is it
repeatable.

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

  parent reply	other threads:[~2001-08-13  8:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-10 13:20 Trenton D. Adams
2001-08-10 14:28 ` Jonathan Larmour
2001-08-10 22:29   ` Trenton D. Adams
2001-08-11  6:53     ` Jonathan Larmour
2001-08-13  8:35   ` Trenton D. Adams [this message]
2001-08-13  9:53     ` Jonathan Larmour
2001-08-13 13:13       ` Trenton D. Adams
2001-08-13 13:27         ` Jonathan Larmour
2001-08-13 14:10           ` Trenton D. Adams
2001-08-11 18:05 ` Mark Salter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001801c1240d$8371c290$090110ac@TRENT' \
    --to=tadams@theone.dnsalias.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).