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 52CC6C433F5 for ; Sat, 1 Jan 2022 21:53:33 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 5B2A482F3E; Sat, 1 Jan 2022 22:53:31 +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="Y0YZV8lQ"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id C48A38111F; Sat, 1 Jan 2022 22:53:29 +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 D03EB82F3E for ; Sat, 1 Jan 2022 22:53:26 +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=pali@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 988CF603E0; Sat, 1 Jan 2022 21:53:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C5B15C36AE7; Sat, 1 Jan 2022 21:53:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1641074003; bh=KYft1GVD+koevwabylwcm1KQFzzFLuD/+a2jXe9wQJI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Y0YZV8lQjUnFYHK8YF2MUgQCGsUYoBnEfXn1C16MhSsoV4aw8S9r+bAKKEavLd6dW ziN5ztZBVVdvsHdgIk3tzcJP4AK+hBat8Z8rQrK98iGgDB+YvFaJZh0Yyb7wKcVXFy 1pDb/q/jMpaQRH6oxKVytKUkmwa5R5bxH465hlKh34nDM/VB37eo4eBLkbMr5zqQQc JOH7il1pL29WYGj8iZBrjheWLgD9WoNTgBv7cKkD3vjHXOsC7dkLOUXaBJb6neuIbo v9zN4Lcl79lLLEecq1M1s/ki3AtdV90m/UQhhcHtUWmHL1Qp1vDK8Cbc+IFYqg+j5V L88HmZRkZ4zqw== Received: by pali.im (Postfix) id 78A10881; Sat, 1 Jan 2022 22:53:21 +0100 (CET) Date: Sat, 1 Jan 2022 22:53:21 +0100 From: Pali =?utf-8?B?Um9ow6Fy?= To: Tony Dinh Cc: Marek =?utf-8?B?QmVow7pu?= , U-Boot Mailing List , Stefan Roese , Tom Rini Subject: Re: kwboot: Marvell Dove UART booting Message-ID: <20220101215321.ryncu7girojzoeya@pali> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 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 Sunday 26 December 2021 13:41:03 Tony Dinh wrote: > Follow up on the UART booting session before. > > Thanks for the advice about the Reset Strapping documentation. I've > extracted the attachment 88AP510_Reset_Strapping.xls from the HW Spec > for Dove at: > https://www.kernel.org/doc/html/latest/arm/marvell.html > > Listed below are the Boot Modes that are relevant to this subject > (there are other Boot Modes for SATA, NAND but we are not interested > in those): > > 0x00 Direct boot from SPI > 0x01 Boot from SPI with 3 address cycles > 0x02 Boot from SPI with 4 address cycles > 0x0E Boot from UART0 using Xmodem > 0x0F Boot from UART1 using Xmodem > 0x10 Open BootROM debug prompt on UART0 > 0x11 Open BootROM debug prompt on UART1 > > So it does look like the jumper on this HP T5335z is actually to put > the box into BootROM debug mode using 0x10. And from there, we can use > 0x0E to put the BootROM into UART0 booting mode. > > Oddly, I've also tried booting from SPI while at the BootROM debug > prompt, but have not been successful with either 0x00, 0x01, or 0x02. > I was hoping that it would make testing easier if I could run "Boot > from SPI" to boot into Linux without having to remove the jumper. And which hex mode is activated when jumper is not set to that Debug prompt UART mode? You should be able to check current mode by reading 0xD00D0214 address which should contain latched sample at reset value. E.g. in U-Boot by 'md 0xD00D0214 1' command.