From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Failed to launch xen on J6 evm Date: Mon, 9 Mar 2015 09:54:54 +0000 Message-ID: <1425894894.14353.68.camel@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YUuOp-0002MX-LI for xen-devel@lists.xenproject.org; Mon, 09 Mar 2015 09:54:59 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Korupol, Naveen (EXT)" Cc: "xen-devel@lists.xenproject.org" List-Id: xen-devel@lists.xenproject.org On Fri, 2015-03-06 at 20:03 +0000, Korupol, Naveen (EXT) wrote: > I am using J6 evm. What is one of them? > played with couple different u-boots Does your u-boot launch the kernel (AKA Xen in this case) in NS.HYP mode? > If there are any probable fixes/hints for bringing up XEN on J6 evm. Given where things are apparently hanging I think the first step would be to enable early printk for your platform. See docs/misc/arm/early-printk.txt and the long ifeq chain in xen/arch/arm/Rules.mk. If the UART on your platform is one of the existing ones in xen/arch/arm/arm*/debug*.inc then this is pretty easy. If not then you just need to provide two ASM macros early_uart_ready and early_uart_transmit which is pretty trivial for every UART I've ever seen -- see the existing debug*.inc for examples. Ian.