From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15182 invoked by alias); 12 Mar 2012 16:12:34 -0000 Received: (qmail 15169 invoked by uid 22791); 12 Mar 2012 16:12:32 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 12 Mar 2012 16:12:07 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 50AA62F7800A; Mon, 12 Mar 2012 16:12:06 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NIyl+GkMIlF; Mon, 12 Mar 2012 16:12:04 +0000 (GMT) Message-ID: <4F5E204B.5040402@ecoscentric.com> Date: Mon, 12 Mar 2012 16:12:00 -0000 From: Alex Schuilenburg User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: John Dallaway CC: eCos developers Subject: Re: eCos GNU tools 4.6.2-20120125 ready for testing References: <4F106345.4080902@siva.com.mk> <4F11574D.9070002@dallaway.org.uk> <4F11AC54.7000902@siva.com.mk> <4F1CB41C.90900@jifvik.org> <4F1DA9A0.5070702@siva.com.mk> <4F1FF5AD.4010901@ecoscentric.com> <4F39887A.5050905@siva.com.mk> <4F50F700.5080902@ecoscentric.com> <4F521D6A.4010500@siva.com.mk> <4F52B2C8.4010809@schuilenburg.org> <4F53C46B.4090502@dallaway.org.uk> <4F53FF0D.80107@ecoscentric.com> <4F574D4A.2090407@ecoscentric.com> <4F58EC32.9070103@ecoscentric.com> <4F5B8C70.4080208@dallaway.org.uk> In-Reply-To: <4F5B8C70.4080208@dallaway.org.uk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2012-03/txt/msg00026.txt.bz2 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 *