public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos developers <ecos-devel@ecos.sourceware.org>
Subject: Re: eCos GNU tools 4.6.2-20120125 ready for testing
Date: Mon, 12 Mar 2012 16:12:00 -0000	[thread overview]
Message-ID: <4F5E204B.5040402@ecoscentric.com> (raw)
In-Reply-To: <4F5B8C70.4080208@dallaway.org.uk>

John,

On 2012-03-10 17:16, John Dallaway wrote:
> Hi Alex
>
> Alex Schuilenburg wrote:
>
>> I have finally got a limping version of RedBoot generated from anoncvs
>> running on this platform in our test farm, and it does run tests
>> generated from anoncvs ecos.  Unfortunately both ethernet and flash
>> support for this board appears broken, so lwip and bsd testing is out. 
> Just to be sure, did you set
> CYGHWR_HAL_ARM_LPC24XX_EA2468_DATA_BUS_WIDTH == 32 in both the RedBoot
> and eCos test application builds for use with your Embedded Artists
> LPC2468-32 OEM board?

Yes and both anoncvs builds (32 bit and thumb) have

echo cdl_option CYGHWR_HAL_ARM_LPC24XX_EA2468_DATA_BUS_WIDTH { user_value 32 } | ecosconfig import /dev/stdin

as part of their build script.  Don't be misled by the target name
ea_lpc2468_32 as I just added this as an alias to ecos.db for the board
so it would be easier to simply add into the farm without having to
create a new platform and board.

> Very little has changed in the HAL and driver packages for the ea2468
> target since the port was first contributed, although the LPC2xxx
> ethernet driver has been extended for use with LPC17xx parts.

On a hunch following the above remarks I rebuilt RedBoot without
ethernet support.  The same "heaptest" test that failed in the farm
passes on this newer RedBoot on a second board I have in the office.
Previously, when it came up it complained:

+
LPC2XXX_ETH: Initialising 0xFFE00000
LPC2XXX_ETH - Warning! ESA unknown
LPC2XXX_ETH: 12:34:56:78:9a:bc
No network interfaces found

RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN - built 18:10:14, Mar  7 2012


Now it gives no such complaints. It could be down to the boards though
because we know one of these boards was a bit fragile when run in the
farm last time, although we think it was for resetting only and we
thought it was the one I have here that was fragile. 

Alternatively, unless there is an undocumented ethernet option for
configuring ethernet support for RedBoot for this board, ethernet
support could have suffered bitrot since the extension for LPC17xx parts
and this *may* be affecting the test results. The ethernet is connected
to the board in the farm.

We will hopefully swap the boards over tomorrow in the farm so some of
these failures will start passing.  The timeouts are killing progress. I
will restart the tests in the farm which will clean up tests like
"heaptest" which appear effected by either the "faulty ethernet RedBoot"
or the board and will re-run "heaptest" once I have replaced RedBoot
when I get this board back to confirm which is at fault (board or RedBoot).

Cheers
-- Alex

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  *


  reply	other threads:[~2012-03-12 16:12 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
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 [this message]
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=4F5E204B.5040402@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).