From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesper Skov To: Ilan Ovadia Cc: ecos-discuss@sourceware.cygnus.com Subject: Re: [ECOS] Running ECOS using the PPC simulator Date: Mon, 26 Apr 1999 02:30:00 -0000 Message-id: <14116.12897.338880.502437@lassi.cygnus.co.uk> References: <37242E45.FBE42C97@abstract.co.il> <37242E45.FBE42C97@abstract.co.il> X-SW-Source: 1999-04/msg00015.html >>>>> "Ilan" == Ilan Ovadia writes: Ilan> Hi, I've build an environment for the PowerPC using the Ilan> configuration tool (PowerPC architecture, minimal simulator). Using the default configuration? Ilan> I tried to execute one of the tests by: [snip] Here's the GDB output when I do it: lassi:> powerpc-eabi-gdb -nw install/tests/kernel/bin_sem0 GNU gdb 4.17-ecos-98r1p4 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. This version of GDB is supported for customers of Cygnus Solutions. Type "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=powerpc-eabi"... (gdb) target sim -f /local/ecc/ecc/ecc/hal/powerpc/sim/current/runtime/tree Size of register r0 (0) incorrect (1 instead of 4))Connected to the simulator. (gdb) load (gdb) r Starting program: /local/ecc/build/sim-powerpc/install/tests/kernel/bin_sem0 PASS: EXIT: The warning about register size can be ignored. Ilan> and the program never returned. A program never returns. If you just want the GDB prompt back, you could set a breakpoint at cyg_test_exit before starting the test. Or you can break execution. When I press C-c after the above output, I get: Program received signal SIGINT, Interrupt. cyg_test_exit () at /local/ecc/ecc/ecc/infra/current/src/tcdiag.cxx:100 100 ; Current language: auto; currently c++ (gdb) I don't see the problem you reported when running the clock0 test. Notice that the problematic address is in ROM space. The PowerPC simulator can only run tests configured for the minimal simulator, and these are normally loaded at address 0x4000. Perhaps you ran a test configured for the Cogent board by mistake? Thanks, Jesper