public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Bernd Schuster" <schuster_bernd@gmx.net>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] GDB stub support
Date: Mon, 17 Dec 2012 17:25:00 -0000	[thread overview]
Message-ID: <20121217172456.214150@gmx.net> (raw)

Hi, 

unfortunately I couldn`t get GDB working as expected. 

At the moment, I`m able to run Redboot at my target system - mips32 24kc processor as ROMRAM version. When redboot starts, I`m able to see all messages from the redboot bootloader by my serial port ttyS0 (configurated with 115200 baud). After that redboot starts my application which is located at the addr 0x800400BC by a short boot script. 

Now, I`m trying to add GDB support by using the same serial interface ttyS0. I`m not totally sure if that could be already the problem, because my application also puts some messages to this serial interface. 

When I enable GDB with the following commands I can see that cutecom - terminal programm - will go from the open to the close state. That`s seems a correct behaviour to me. Furthermore I got a very small message on the serial terminal - something like that: 

RedBoot> 
RedBoot>+$#00

Here are the steps from the console: 

xxxxx@xxxxx:~/../build/obj> mipsisa32-elf-gdb myProgramm.elf
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=mipsisa32-elf"...
(gdb) set remotebaud 115200
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...

I hope anyone of you have some hints / information solving the problem. 

best regards
Bernd



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

             reply	other threads:[~2012-12-17 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 17:25 Bernd Schuster [this message]
2012-12-17 19:01 ` [ECOS] " John Dallaway
2012-12-17 21:04   ` Bernd Schuster
2012-12-18  8:39     ` Bernd Schuster
2012-12-18  8:45       ` Bernd Schuster
2012-12-18 10:28     ` John Dallaway
2012-12-18 11:56       ` Bernd Schuster
2012-12-18 12:09       ` Bernd Schuster

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=20121217172456.214150@gmx.net \
    --to=schuster_bernd@gmx.net \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).