public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dirk Husemann <hud@zurich.ibm.com>
To: "Dave B. Sharp" <daveb_sharp@yahoo.ca>
Cc: Andrew Lunn <andrew@lunn.ch>,
	eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Serial support for arm board
Date: Tue, 01 Nov 2005 13:19:00 -0000	[thread overview]
Message-ID: <43676B5A.1090201@zurich.ibm.com> (raw)
In-Reply-To: <20051101131411.3264.qmail@web32911.mail.mud.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 3870 bytes --]

Dave B. Sharp wrote:

>No, but even if I had would that have not been cleared
>with a reboot?
>  
>
no, GDB will set the breakpoint on loading. so, if you staid connected, 
did a reset of the board and then reloaded the image, you'd end up with 
the breakpoint set again.

what i usually do is set breakpoints at cyg_user_start and 
cyg_assert_fail before doing the continue.

    cheers,
    dirk

>   Dave
> 
>--- Dirk Husemann <hud@zurich.ibm.com> wrote:
>
>  
>
>>Dave B. Sharp wrote:
>>
>>    
>>
>>>I've compiled and done everything in link you sent:
>>>      
>>>
>>>arm-gdb main
>>>target remore ....
>>>load ...
>>>continue
>>>continuing
>>>
>>>when I do the continue it seem to hang waiting for
>>>      
>>>
>>the
>>    
>>
>>>target to connect. When I <cntl-c> out it reports
>>>interupted while waiting for the program
>>>Give up (and stop debugging it?) (y or n)
>>>Am I missing something? Do I need to write a stub
>>>      
>>>
>>for
>>    
>>
>>>my program or is the one in Redboot sufficient?
>>> 
>>>
>>>      
>>>
>>hmm...not sure whether you did that, but did you set
>>a breakpoint? at 
>>least from the summary above it looks like you
>>didn't...
>>
>>    dirk
>>
>>    
>>
>>> Cheers
>>>  Dave
>>>
>>>--- Andrew Lunn <andrew@lunn.ch> wrote:
>>>
>>> 
>>>
>>>      
>>>
>>>>On Thu, Oct 27, 2005 at 03:33:09PM -0400, Dave B.
>>>>Sharp wrote:
>>>>   
>>>>
>>>>        
>>>>
>>>>>I have been looking for gdb with Redboot to no
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>avail,
>>>>   
>>>>
>>>>        
>>>>
>>>>>however I beleive I am about to find out
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>otherwise.
>>>>   
>>>>
>>>>        
>>>>
>>>>>Can  you point me to some info and, can I use gdb
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>in
>>>>   
>>>>
>>>>        
>>>>
>>>>>"exec" mode, since at that point I beleive there
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>will
>>>>   
>>>>
>>>>        
>>>>
>>>>>no longer be any Redboot support 
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>You don't need to use exec mode. Just connect with
>>>>gdb then use gdb to
>>>>load the application into ram, set breakpoints and
>>>>use gdbs go command
>>>>to set it running.
>>>>
>>>>
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>http://ecos.sourceware.org/docs-latest/user-guide/using-commandline-testcase.html
>>    
>>
>>> 
>>>
>>>      
>>>
>>>>       Andrew
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>
>>>	
>>>
>>>	
>>>		
>>>      
>>>
>>__________________________________________________________
>>
>>    
>>
>>>Find your next car at http://autos.yahoo.ca
>>>
>>> 
>>>
>>>      
>>>
>>-- 
>>Dr Dirk Husemann, Pervasive Computing, IBM Research,
>>Zurich Research Lab
>>	hud@zurich.ibm.com ---
>>http://www.zurich.ibm.com/~hud/
>>       PGP key:
>>http://www.zurich.ibm.com/~hud/contact/PGP
>>  PGP Fingerprint: 983C 48E7 0A78 A313 401C  C4AD
>>3C0A 278E 6431 A149
>>	     Email only authentic if signed with PGP key.
>>
>>Appended to this email is an electronic signature
>>attachment. You can
>>ignore it if your email program does not know how to
>>verify such a
>>signature. If you'd like to learn more about this
>>topic, www.gnupg.org
>>is a good starting point.
>>
>>
>>    
>>
>
>
>
>	
>
>	
>		
>__________________________________________________________ 
>Find your next car at http://autos.yahoo.ca
>
>
>  
>


-- 
Dr Dirk Husemann, Pervasive Computing, IBM Research, Zurich Research Lab
	hud@zurich.ibm.com --- http://www.zurich.ibm.com/~hud/
       PGP key: http://www.zurich.ibm.com/~hud/contact/PGP
  PGP Fingerprint: 983C 48E7 0A78 A313 401C  C4AD 3C0A 278E 6431 A149
	     Email only authentic if signed with PGP key.

Appended to this email is an electronic signature attachment. You can
ignore it if your email program does not know how to verify such a
signature. If you'd like to learn more about this topic, www.gnupg.org
is a good starting point.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-11-01 13:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 18:20 Dave B. Sharp
2005-10-27 18:27 ` Gary Thomas
2005-10-27 18:40   ` Dave B. Sharp
2005-10-27 18:47     ` Gary Thomas
2005-10-27 18:57       ` Dave B. Sharp
2005-10-27 19:02         ` Andrew Lunn
2005-10-27 19:33           ` Dave B. Sharp
2005-10-27 20:58             ` Andrew Lunn
2005-10-31 19:25               ` Dave B. Sharp
2005-11-01 10:26                 ` Dirk Husemann
2005-11-01 13:14                   ` Dave B. Sharp
2005-11-01 13:19                     ` Dirk Husemann [this message]
2005-10-27 19:03         ` Gary Thomas
2005-10-27 19:23           ` Dave B. Sharp
2005-10-27 19:28             ` Gary Thomas
2005-10-27 20:16               ` Dave B. Sharp

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=43676B5A.1090201@zurich.ibm.com \
    --to=hud@zurich.ibm.com \
    --cc=andrew@lunn.ch \
    --cc=daveb_sharp@yahoo.ca \
    --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).