public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Les G. Miklosy" <lgm1@sbcglobal.net>,   ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GDB-stub in Redboot fails to handshake
Date: Thu, 06 Mar 2008 08:37:00 -0000	[thread overview]
Message-ID: <47CFACF4.5040103@mlbassoc.com> (raw)
In-Reply-To: <20080306082538.GA28635@lunn.ch>

Andrew Lunn wrote:
> On Sat, Mar 08, 2008 at 05:09:30AM -0800, Les G. Miklosy wrote:
>> Hello Gents: 
>>
>> As you can see in this gdb log file, my Sparc target running Redboot fails to 
>> recognize ($#00) the simple query commands offered by my Linux host over a 
>> serial connection. 
> 
> The redboot stub only implements a subset of the gdb protocol. 
> 
>> The target application is simply hello-world with a linked 
>> library build from ECOS version 1.0.7. Redboot is a ROMRAM bootloader also 
>> built from version 1.0.7. I can hear you smacking your foreheads asking why 
>> use V 1.0.7 , I am using this version because a board support package was 
>> built around it.
>>
>> I tried the execution of Redboot with and without a '$' to start the GDB-stub 
>> with no improvement. Any application I try to load/continue ends with a 
>> Signal Hangup.  A diff between ECOS version 2.0 and 1.0.7 shows many changes 
>> to the code particularly the part for initiating gdb-stub. Is this old 
>> version suspect? Does the solution demand an upgrade to 2.0 or shall I debug 
>> 1.0.7?
>>
>> Thanks for any guidance,
>> Les
>>
>>
>>
>> w +$Hc-1#09
>> r -
>> w $Hc-1#09
>> r <Timeout: 2 seconds>
>> w $Hc-1#09
>> r $#00
>> w +
>> r $#00
>> w +
>> r $#00
>> w +
>> r $#00
>> w +
>> r <Timeout: 2 seconds>
>>
>> ... repeats
>>
>>
>> c load
>> w $X41000000,0:#73
>> r +$OK#9a
>>
>> ... load application hello-world
>>
>>
>> Sending packet: $p42#d6...[+]Ack
>> [$][0][0][0][0][0][0][2][0][#][8][2]Packet received: 00000020
>> Sending packet: $p43#d7...[+]Ack
>> [$][4][0][0][0][0][0][5][0][#][8][9]Packet received: 40000050
>>
>> ...
>>
>> Sending packet: $C01#a4...[+]Ack
>> [$][T][0][1][4][4][:][4][0][0][1][8][c][1][c][;][0][e][:][0][0][0][0][0][0][0]
>> [0][;][#][1][0]Packet received: T0144:40018c1c;0e:00000000;
> 
> That fact that it is downloading suggests the stub is working.  
> 
> This line T0144:40018c1c;0e:00000000; indicates it has thrown an
> exception. My guess is you are downloading your hello world image over
> the top of redboot. What RAM addresses does your application image
> use? What RAM does redboot use?
> 
> Newer versions of redboot would probably give you a warning you are
> about to stomp of it, but something as old as 1.0.7 probably does not
> have the check.

Sadly, no.  Once the GDB protocol is entered, all of the checks that
RedBoot might be able to make (e.g. during the 'load' command), are
off since RedBoot is really out of the picture, only GDB is running.

-- 
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:[~2008-03-06  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 21:55 Les G. Miklosy
2008-03-06  8:26 ` Andrew Lunn
2008-03-06  8:37   ` Gary Thomas [this message]
2008-03-08  2:47 Les G. Miklosy

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=47CFACF4.5040103@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=lgm1@sbcglobal.net \
    /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).