From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B770BC433EF for ; Wed, 5 Jan 2022 09:10:55 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 69F4980FDD; Wed, 5 Jan 2022 10:10:53 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.b="tA/sSfL0"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id D8188830D9; Wed, 5 Jan 2022 10:10:51 +0100 (CET) Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 22AA080FDD for ; Wed, 5 Jan 2022 10:10:49 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=kabel@kernel.org Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 935C76163B; Wed, 5 Jan 2022 09:10:47 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C1131C36AEB; Wed, 5 Jan 2022 09:10:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1641373847; bh=7Ej+upXSMpCGA4sXRoGTD62lFasHSB1qV2pp7FMDgYM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=tA/sSfL0HMtI2+mNNH4QoT5mdgmlfmLYwd/hFuyr0tpCv4SiIjgZRb/yM6+eE0I1m u8jadiyH4f5yG3ytpwm8QWYOYTr/i68M9Tkql7eGqHQ4ikzOVBx1QOq/73lEIernBS M7uX4mWkxzIN1WdHLN2r9XMoK1znl6qVgN7pY8u0dRIvdbFTPiKzSQS4F0CkWZxoPf Qxiu7hydB0P/nIizHC0CyGgAFme0DSghawlN5ExMSLoio0+EA5a71Cxc9CLFvx0t9w hW68+EuIXBEDMcBsYXZZiRdbUx0Clz5s0k1X+lqyooKY7QWSocDAJo36agr8n9Mfkw uDlpb297KrhCw== Date: Wed, 5 Jan 2022 10:10:41 +0100 From: Marek =?UTF-8?B?QmVow7pu?= To: Chris Packham Cc: Chris Packham , Stefan Roese , Baruch Siach , Pavol =?UTF-8?B?Um9ow6Fy?= , u-boot , Mario Six , Dennis Gilmore , Kostya Porotchkin , Marek =?UTF-8?B?QmVow7pu?= Subject: Re: [PATCH u-boot-marvell] PLEASE TEST ddr: marvell: a38x: fix SPLIT_OUT_MIX state decision Message-ID: <20220105101041.600c2f75@thinkpad> In-Reply-To: References: <20220104202827.9120-1-kabel@kernel.org> X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.38 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean On Wed, 5 Jan 2022 11:10:51 +1300 Chris Packham wrote: > Hi Marek, >=20 > On Wed, Jan 5, 2022 at 9:28 AM Marek Beh=C3=BAn wrote: > > > > From: Marek Beh=C3=BAn > > > > Hello, > > > > continuing my last discussion with Chris [1] about this, could you > > please test this change? (For Chris, mainly on your x530, since last > > time you said it hanged your board in SPL.) =20 >=20 > I still get a hang after "Returning to BootROM (return address > 0xffff05c4)... " (after the DDR training). Hi Chris, would it be possible for me to connect to a computer to which the x530 is connected via UART so that I can debug it? Could you prepare such an environment? It would also need a mechanism to reset the board remotely somehow. I prepared a similar remote debugging environment for Marvell when they were solving some issues for us. If not, then I guess we will just have to send debugging code and results back and forth. Marek