From: Alex Schuilenburg <alexs@ecoscentric.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: eCos developers <ecos-devel@ecos.sourceware.org>
Subject: Re: eCos GNU tools 4.6.2-20120125 ready for testing
Date: Wed, 07 Mar 2012 11:58:00 -0000 [thread overview]
Message-ID: <4F574D4A.2090407@ecoscentric.com> (raw)
In-Reply-To: <4F53FF0D.80107@ecoscentric.com>
Hi Ilija,
The RedBoot issue on the STM3210E-EVAL turned out to be a non-issue.
eCos and eCosPro RedBoot are compatible. There was an eCosPro specific
issue which I had forgotten about - sorry. The board ran overnight just
over 1000 tests in different eCos configurations. There are currently 9
failures, listed according to their configuration name in our test farm.
As jld knows, when a test fails in the farm it is automatically rerun an
additional 2 times to confirm the failure is reproducible. All other
tests in these configurations passed.
ustl1: bvt05, bvt13, bvt17, sprintf2
infra1: except1, kexcept1, testintr
absent1, compile1: testintr
The eCos used was the version was dated 1 March and the configurations
script segment to create each configuration is listed below. If you
need any more info, just let me know. I unfortunately don't have the
time at the moment to export the full set of results, but hopefully this
will be enough for you to reproduce the failures. As a comparison, all
tests passed in eCosPro for the STM3210E-EVAL with the obvious exception
of the ustl1 configuration.
ustl1:
ecosconfig -i new stm3210e_eval
cat > ustl1.ecm <<EOF;
cdl_configuration eCos {
template default ;
package CYGPKG_USTL current ;
package CYGPKG_IO_FILEIO current ;
};
EOF
ecosconfig import ustl1.ecm
ecosconfig resolve
ecosconfig tree
...
infra1:
ecosconfig -i new stm3210e_eval
cat > infra1.ecm <<EOF;
cdl_configuration infra1 {
template uitron ;
package -template CYGPKG_UITRON current ;
};
cdl_component CYG_HAL_STARTUP {
user_value RAM
};
cdl_component CYGPKG_INFRA_DEBUG {
user_value 1
};
EOF
ecosconfig import infra1.ecm
ecosconfig resolve
ecosconfig tree
...
compile1:
Default build with "-Os"
absent1:
ecosconfig -i new stm3210e_eval
cat > absent1.ecm <<EOF;
cdl_configuration absent1 {
hardware stm3210e_eval ;
template uitron ;
package -template CYGPKG_UITRON current ;
};
cdl_component CYG_HAL_STARTUP {
user_value RAM
};
cdl_option CYGSEM_LIBC_EXIT_CALLS_FFLUSH {
user_value 0
};
cdl_option CYGFUN_LIBC_TIME_POSIX {
user_value 0
};
cdl_option CYGIMP_LIBC_TIME_ASCTIME_R_INLINE {
user_value 0
};
cdl_option CYGIMP_LIBC_TIME_CTIME_R_INLINE {
user_value 0
};
cdl_option CYGIMP_LIBC_TIME_GMTIME_R_INLINE {
user_value 0
};
cdl_option CYGIMP_LIBC_TIME_LOCALTIME_R_INLINE {
user_value 0
};
cdl_option CYGSEM_LIBM_USE_STDERR {
user_value 0
};
EOF
ecosconfig import absent1.ecm
ecosconfig resolve
ecosconfig tree
...
Cheers
- Alex Schuilenburg
Managing Director/CEO eCosCentric Limited
** Visit us at the ESC Expo at Design West in San Jose **
** 27-29 March, McEnery Convention Center - Stand #846 **
next prev parent reply other threads:[~2012-03-07 11:58 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 17:01 Gnutools: consideration for upgrade to GCC 4.6 Ilija Kocho
2012-01-13 18:54 ` Bernard Fouché
2012-01-13 19:39 ` Ilija Kocho
2012-01-13 19:09 ` Frank Pagliughi
2012-01-13 19:45 ` Ilija Kocho
2012-01-14 10:22 ` John Dallaway
2012-01-14 16:02 ` Sergei Gavrikov
2012-01-15 17:36 ` Grant Edwards
2012-01-15 18:42 ` Sergei Gavrikov
2012-01-15 21:39 ` Stanislav Meduna
2012-01-23 1:01 ` Jonathan Larmour
2012-01-15 22:21 ` Ilija Kocho
2012-01-23 1:07 ` Jonathan Larmour
2012-01-15 22:21 ` Ilija Kocho
2012-01-16 15:20 ` Grant Edwards
2012-01-16 20:43 ` Sergei Gavrikov
2012-01-16 21:11 ` Sergei Gavrikov
2012-01-17 9:58 ` Bernard Fouché
2012-01-17 10:38 ` Paul Beskeen
2012-01-17 12:28 ` Sergei Gavrikov
2012-01-23 0:59 ` Jonathan Larmour
2012-01-14 16:25 ` Ilija Kocho
2012-01-23 1:13 ` Jonathan Larmour
2012-01-23 18:40 ` Ilija Kocho
2012-01-23 19:29 ` Jonathan Larmour
2012-01-25 12:30 ` Alex Schuilenburg
2012-01-25 20:59 ` Ilija Kocho
2012-01-26 13:36 ` Alex Schuilenburg
2012-01-26 20:18 ` Ilija Kocho
2012-02-13 22:02 ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Ilija Kocho
2012-02-20 16:00 ` Alex Schuilenburg
2012-02-20 20:45 ` Ilija Kocho
2012-03-02 16:36 ` Alex Schuilenburg
2012-03-03 13:32 ` Ilija Kocho
2012-03-04 0:10 ` Alex Schuilenburg
2012-03-04 17:49 ` Sergei Gavrikov
2012-03-04 23:08 ` Alex Schuilenburg
2012-03-04 19:37 ` eCos GNU tools 4.6.2-20120125 ready for testing John Dallaway
2012-03-04 23:47 ` Alex Schuilenburg
2012-03-05 8:00 ` Sergei Gavrikov
2012-03-07 13:51 ` Sergei Gavrikov
2012-03-07 11:58 ` Alex Schuilenburg [this message]
2012-03-07 13:01 ` Ilija Kocho
2012-03-07 13:39 ` Sergei Gavrikov
2012-03-07 13:13 ` John Dallaway
2012-03-12 16:43 ` Alex Schuilenburg
2012-03-16 15:05 ` Alex Schuilenburg
2012-03-08 17:28 ` Alex Schuilenburg
2012-03-09 9:39 ` Ilija Kocho
2012-03-09 17:15 ` Alex Schuilenburg
2012-03-10 17:16 ` John Dallaway
2012-03-12 16:12 ` Alex Schuilenburg
2012-03-13 13:31 ` Alex Schuilenburg
2012-03-13 14:16 ` Ilija Kocho
2012-03-13 17:47 ` Sergei Gavrikov
2012-03-15 8:50 ` John Dallaway
2012-03-17 14:50 ` Sergei Gavrikov
2012-03-17 20:58 ` John Dallaway
2012-03-17 16:44 ` Stanislav Meduna
2012-03-18 19:10 ` eCos GNU tools 4.6.3-20120315 [Was Re: eCos GNU tools 4.6.2-20120125 ready for testing] Ilija Kocho
2012-04-04 12:57 ` Lambrecht Jürgen
2012-04-04 13:18 ` Ilija Kocho
2012-05-31 8:42 ` eCos GNU tools 4.6.3-20120315 and link time optimization Bernard Fouché
2012-03-05 8:30 ` eCos GNU tools 4.6.2-20120125 ready for testing Tomas Frydrych
2012-03-05 8:56 ` Tomas Frydrych
2012-03-05 9:50 ` John Dallaway
2012-03-05 9:55 ` Anders Montonen
2012-03-05 14:20 ` John Dallaway
2012-03-05 10:16 ` Ilija Kocho
2012-03-05 12:56 ` Tomas Frydrych
2012-03-03 12:58 ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Sergei Gavrikov
2012-01-17 9:37 ` Gnutools: consideration for upgrade to GCC 4.6 Tomas Frydrych
2012-01-17 16:10 ` Stanislav Meduna
2012-01-17 16:25 ` Tomas Frydrych
2012-01-17 16:45 ` Ilija Kocho
2012-01-20 14:42 ` Frank Pagliughi
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=4F574D4A.2090407@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=ilijak@siva.com.mk \
/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).