This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Re: How can I run ecos test case with ecos configuration tool(GUI)- GDB arguments are not excuted? Thanks a lot


Hi:
 I tried to use the ecos configuration tool comes with ecos ver 2.0b1, I
made a custom platform as:

Command prefix:
arm-elf

Arguments for GDB:
set height 0
set debug remote 0
set remotebaud %b
target remote %p
load
break cyg_test_exit
break cyg_assert_fail
break cyg_test_init
cont
set cyg_test_is_simulator=0
cont
bt

Inferior:
arm-elf-gdb -nw %e

Prompt:
(gdb)

when click the run test, the arm-elf-gdb -nw is called but the Arguments for
GDB is not called in my custom platform. but for a pre-defined platform such
as: e7t I can see the Arguments for GDB are called. why not for the custom
platform I defined? Thanks a lot.

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of John Dallaway
Sent: 14 June 2003 16:35
To: jameshq@liverpool.ac.uk
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: How can I run ecos test case with ecos configuration
tool(GUI)? Thanks a lot


Hi Qiang

You wrote:

>   I have ported ecos to some custom platforms and I would like to run
> throught the ecos test case with ecos configuration tool. I have
> followed the instruction described in the ecos user guide.
> Builds-->Library/Tests, then Tools-->Run Tests, a dialogue prompted
> for adding the new platform, so I add the command prefix as: arm-elf.
> when came to the run test case dialogue all tests listed in the window
> are with .exe  extension, but in the /install tree/tests/xxx all the
> tests have been built without .exe extension. so when I click the Run
> button, error message came out: xxx.exe file is not a file. I tried
> renamming the test file to have the .exe extension and click the Run
> button again, it came out some other error message, if I try to use
> "Add" to add test files, the dialogue for adding test files always has
> a *.exe extension. Where is .exe came from?  I am using ecos
> configuration tool 2.11.

The configtool you are using assumes that Cygwin-hosted GNU tools always add
a .exe suffix to executable files. This is not the case for recent GNU
cross toolchains in their default configurations. Use the configtool which
ships with eCos 2.0 and all should be well.

> BTW how should I set the add platform? (Command prefix, Arguments for
> GDB, Inferior, Prompt?)

Use another hardware platform of the same architecture as an example.

John Dallaway
eCosCentric Limited


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


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]