From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22704 invoked by alias); 21 Jan 2009 22:31:59 -0000 Received: (qmail 22696 invoked by uid 22791); 21 Jan 2009 22:31:58 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from koko.iders.ca (HELO koko.iders.ca) (206.45.72.61) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Jan 2009 22:31:52 +0000 Received: from [200.123.101.231] (zen.iders.ca [200.123.101.231]) by koko.iders.ca (Postfix) with ESMTP id F37343E4017; Wed, 21 Jan 2009 16:31:49 -0600 (CST) Message-ID: <4977A254.9090700@iders.ca> Date: Wed, 21 Jan 2009 22:31:00 -0000 From: Andrew McKay User-Agent: Thunderbird 1.5.0.12 (X11/20071019) MIME-Version: 1.0 To: Jonathan Larmour CC: eCos developers Subject: Re: Redboot hanging during boot on EP9302 References: <49765D66.6090801@iders.ca> <497684C5.8020900@eCosCentric.com> In-Reply-To: <497684C5.8020900@eCosCentric.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: 2009-01/txt/msg00039.txt.bz2 Jonathan Larmour wrote: > Hi Andrew, > > You misaddressed this to ecos-devel-owner instead of ecos-devel. I've > CC'd it to ecos-devel for you in case anyone can help. Thanks, silly me. > > For what it's worth, in the 9 times out of 10 it works, is it solid? > Might it be worth trying out the eCos "heaptest" test (perhaps > increasing the iterations) to verify the stability of SDRAM in case the > timings are marginal? It appears after sending this I ran across the problem. I double checked the Errata for the EP9302 Rev2 part and found something wrong with the SDRAM controller. From Cirrus' Errata sheet: ---------------------------------------------------------------------------- When the SDRAM controller is configure for PRECHARGE ALL commnd, the actual sequence is not always issued to the SDRAM device(s). Workaround: Do a read from each SDRAM bank so that a PRECHARGE command is issued ot each bank of the SDRAM device. This will satisfy the required SDRAM initialization sequence. Due to the effectiveness and simplicity of the software workaround, no silicon fix is planned. ---------------------------------------------------------------------------- I made modifications as necessary to the SDRAM init code and all is well it appears. Thanks for your time, Andrew McKay