From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Nagendra EM <nagendra.em@eudoramail.com>
Cc: Jonathan Larmour <jlarmour@redhat.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] How to RUN a program?
Date: Tue, 03 Jul 2001 05:15:00 -0000 [thread overview]
Message-ID: <XFMail.20010703061515.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <LFNCLJOKPPGACAAA@shared1-mail.whowhere.com>
On 03-Jul-2001 Nagendra EM wrote:
> Hi,
> Thanks for the info. I have run the make file in the examples directory, after changing the
> PKG_INSTALL_DIR and XCC as given in the manual. It has created an exe file also, but when I try
> to load it, it loads, but stops after displaying the load. After that the gdb prompt does not
> appear at all. Any comments? Any suggestions?
This doesn't tell us much more than "it didn't work".
Please send details like you did below - output from the GDB session, etc.
Then maybe we can help.
>
> waiting for your reply...
>
> Thanks and Regards,
> - Nagendra.
>
>
>
> --
>
> On Tue, 03 Jul 2001 05:59:45 Gary Thomas wrote:
>>
>>On 03-Jul-2001 Nagendra EM wrote:
>>> Hi,
>>> I was trying to run one of the sample program on my SA1110 target,
>>> after refering to the "Getting started" manual.
>>>
>>> Now,
>>> I invoke my insight-gdb by running arm-gdb. Then open up a console window (since the insight
>>> gui
>>> window gave some problem connecting). Now, I type target remote COM2, I am able to connect. I
>>> am
>>> able to load the program also. But when I say continue, it just stays there for a long time
>>> without any output. Where should I look for the output? Am I doing anything wrong?
>>>
>>> please suggest.
>>>
>>> The GDB console details pasted here...FYR
>>> ------------------------------------------------------
>>> (gdb) target remote COM2
>>> Remote debugging using COM2
>>> 0x500074c8 in ?? ()
>>>
>>> (gdb) load hello.o
>> ^^^^^^^
>>
>>You should be loading 'hello' (or 'hello.exe' on Windows). You can't
>>run an object file, only one which has been fully linked with the
>>eCos kernel.
>>
>>> Loading section .rodata, size 0x14 lma 0x0
>>> Loading section .text.main, size 0x28 lma 0x0
>>> Start address 0x0 , load size 60
>>
>>These sizes and addresses tell it all - this is not a program which
>>is ready to run (incomplete).
>>
>>> Transfer rate: 480 bits in <1 sec, 30 bytes/write.
>>>
>>> (gdb) continue
>>> Continuing.
>>> -------------------------------------------------------
>>
>
>
> Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at
> http://www.eudoramail.com
next prev parent reply other threads:[~2001-07-03 5:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 5:09 Nagendra EM
2001-07-03 5:15 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-05 22:27 Nagendra EM
2001-07-04 23:30 Nagendra EM
2001-07-04 10:16 Nagendra EM
2001-07-04 10:22 ` Jonathan Larmour
2001-07-04 3:39 Nagendra EM
2001-07-04 3:42 ` Jesper Skov
2001-07-03 10:31 Nagendra EM
2001-07-04 1:46 ` Jesper Skov
2001-07-04 5:32 ` Gary Thomas
2001-07-04 6:41 ` Jesper Skov
2001-07-04 7:30 ` Jonathan Larmour
2001-07-03 6:03 Nagendra EM
2001-07-03 5:49 Nagendra EM
2001-07-03 6:01 ` Gary Thomas
2001-07-03 0:12 Nagendra EM
2001-07-03 4:59 ` Gary Thomas
2001-07-02 22:00 Nagendra EM
2001-07-01 23:00 Nagendra EM
2001-07-02 14:27 ` Jonathan Larmour
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=XFMail.20010703061515.gthomas@cambridge.redhat.com \
--to=gthomas@cambridge.redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
--cc=nagendra.em@eudoramail.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).