public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Ricardo Andrino <ricardo_andrino@web.de>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Error in run tests
Date: Tue, 02 Dec 2003 16:38:00 -0000	[thread overview]
Message-ID: <20031202163813.GI21590@lunn.ch> (raw)
In-Reply-To: <200312021613.hB2GD6Q30319@mailgate5.cinetic.de>

On Tue, Dec 02, 2003 at 05:13:06PM +0100, Ricardo Andrino wrote:
> Hello again,
> I have now chosen the RAM start up but when i try to run the tests the program or the examples these programs hang up.See please the following:
> ***************************************************************************
> Run started
> (gdb) set height 0
> set height 0
> (gdb) set debug remote 0
> set debug remote 0
> (gdb) set remotebaud 38400
> set remotebaud 38400
> (gdb) target rdi /dev/ttyS1
> target rdi /dev/ttyS1
> Angel Debug Monitor (serial) 1.04 (Advanced RISC Machines SDT 2.5) for AT91EB40A (1.00)
> Angel Debug Monitor rebuilt on Feb 03 2002 at 16:09:59
> Serial Rate:  38400
> (gdb) load
> load
> Loading section .rom_vectors, size 0x40 lma 0xc000
> Loading section .text, size 0x6dec lma 0xc040
> Loading section .rodata, size 0x448 lma 0x12e2c
> Loading section .data, size 0x2bc lma 0x13274
> Start address 0xc040, load size 30000
> Transfer rate: 26666 bits/sec, 491 bytes/write.
> (gdb) break cyg_test_exit
> break cyg_test_exit
> Breakpoint 1 at 0xead0: file /opt/ecos/ecos-snapshot-2003-11-25/packages/infra/current/src/tcdiag.cxx, line 267.
> (gdb) break cyg_assert_fail
> break cyg_assert_fail
> Function "cyg_assert_fail" not defined.
> (gdb) break cyg_test_init
> break cyg_test_init
> Breakpoint 2 at 0xe9e0: file /opt/ecos/ecos-snapshot-2003-11-25/packages/infra/current/src/tcdiag.cxx, line 192.
> (gdb) cont
> cont
> Continuing.
> ****************************************************************************
> I don't really know why i can not run the test.It's suppose that it is easy isn't it? and that is only the beginnig!!!!!!! Oh God!!!
> 
> Any idea?

First of, do what we have all suggested. Swap to redboot. Thats how
eCos has been tested and thats the configuration we know it works
in. Its quite possible the setup you are using now the application is
using the same memory as Angel.

> Another question, i have added the Redboot package in the ecos
> configuration tool but if i clicked in Built Redboot ROM elf image,
> there are 2 error and the target.ld is not created, When i disable
> this option there is no problem why? I will need this file to
> download redboot won't i?

That is not the correct way to build Redboot. Read the documentation.

     Andrew

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

  reply	other threads:[~2003-12-02 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 16:13 Ricardo Andrino
2003-12-02 16:38 ` Andrew Lunn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-03 14:53 Ricardo Andrino
2003-12-02 14:42 Ricardo Andrino
2003-12-02 15:06 ` Andrew Lunn
2003-12-02 10:19 Ricardo Andrino
2003-12-02 10:47 ` Andrew Lunn
2003-12-02 10:53 ` Nick Garnett
2003-12-02  9:52 Ricardo Andrino
2003-12-02 10:09 ` Nick Garnett

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=20031202163813.GI21590@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=ricardo_andrino@web.de \
    /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).