From: Alexey Shusharin <mrfinch@mail.ru>
To: albert prasetyo <prasetyoalbert@gmail.com>
Cc: "Paul D. DeRocco" <pderocco@ix.netcom.com>,
ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ecos application problem
Date: Fri, 24 Aug 2007 04:57:00 -0000 [thread overview]
Message-ID: <1187931235.10148.4.camel@killix> (raw)
In-Reply-To: <f231b81a0708231930x3dee2fddmc8343230057611a2@mail.gmail.com>
Hi Albert
I think you should look at eCos documentation about COMM channels:
http://ecos.sourceware.org/docs-latest/ref/hal-calling-if.html
regards
Alexey
Ð ÐÑн, 24/08/2007 в 10:30 +0800, albert prasetyo пиÑеÑ:
> Hi Paul;
> Thanks for the reply. According to your remarks, is it means that
> I need to exclude GDB stubs in HAL (redboot template)?
> (i.e. disable CYDBG_HAL_DEBUG_GDB_INCLUDE_STUBS)
> I tried to do that but the output is still the same.
> I communicate with the board using hyperterminal.
> Thank you for your attention.
>
> Regards;
> Albert P
>
> On 8/24/07, Paul D. DeRocco <pderocco@ix.netcom.com> wrote:
> > > From: albert prasetyo
> > >
> > > I am a newbie in redboot and ecos. Currently I am developing
> > > redboot for AT91RM9200 board (ARM9). I am able to develop
> > > redboot (RAM) version for this board but unable to run the
> > > application (app.srec).
> > >
> > > Source code of app.srec:
> > > #include <stdio.h>
> > >
> > > int main(void)
> > >
> > > {
> > >
> > > printf("1\n");
> > >
> > > return 0;
> > >
> > > }
> > >
> > >
> > > This is the message generated by redboot:
> > >
> > > RedBoot> load -m y
> > > CCEntry point: 0x21000040, address range:
> > > 0x21000000-0x210086c4 xyzModem - CRC mode,
> > > 2(SOH)/102(STX)/0(CAN) packets, 4 retries
> > > RedBoot> go
> > > $O310A#24
> > >
> > > It somehow managed to print '1' but in ASCII mode. I don't
> > > know where my configuration goes wrong. Any help is much appreciated.
> >
> > That's a GDB packet, containing your output in hex (310A is "1\n"). This is
> > what you get when your program is sharing an interface with the GDB stubs.
> > If you communicated with the board using GDB, and loaded and ran the app
> > that way, GDB would display your output correctly in its console pane. Or if
> > you sent your output to a different device, it would look normal.
> >
> > --
> >
> > Ciao, Paul D. DeRocco
> > Paul mailto:pderocco@ix.netcom.com
> > >
> > > Thanks in advance;
> > > Albert P
> > >
> > > --
> > > Before posting, please read the FAQ:
> > > http://ecos.sourceware.org/fom/ecos
> > > and search the list archive:
> > > http://ecos.sourceware.org/ml/ecos-discuss
> > >
> >
> >
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-08-24 4:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 11:28 albert prasetyo
2007-08-23 22:47 ` Paul D. DeRocco
[not found] ` <029201c7e5d3$ce0bd2d0$887ba8c0@PAULD>
2007-08-24 2:30 ` albert prasetyo
2007-08-24 3:53 ` Paul D. DeRocco
2007-08-24 6:06 ` Sergei Gavrikov
2007-08-27 5:53 ` albert prasetyo
2007-08-27 6:28 ` Sergei Gavrikov
2007-09-01 9:35 ` albert prasetyo
2007-09-01 17:49 ` Sergei Gavrikov
2007-09-03 3:58 ` albert prasetyo
2007-09-03 7:05 ` Sergei Gavrikov
2007-09-04 3:27 ` albert prasetyo
2007-08-24 4:57 ` Alexey Shusharin [this message]
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=1187931235.10148.4.camel@killix \
--to=mrfinch@mail.ru \
--cc=ecos-discuss@sources.redhat.com \
--cc=pderocco@ix.netcom.com \
--cc=prasetyoalbert@gmail.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).