From mboxrd@z Thu Jan  1 00:00:00 1970
From: SimonH <simon.hoinkis@codethink.co.uk>
Date: Tue, 09 Dec 2014 18:19:42 +0000
Subject: [U-Boot] U-Boot on nyan-big via legacy boot
In-Reply-To: <CAPnjgZ0=zoOrSxAUg76kvsSY4KXgYPARmRHu8=h_9e18KFOWEw@mail.gmail.com>
References: <54807914.7020703@codethink.co.uk>	<54807C82.3020904@codethink.co.uk>
	<CAPnjgZ0=zoOrSxAUg76kvsSY4KXgYPARmRHu8=h_9e18KFOWEw@mail.gmail.com>
Message-ID: <54873D3E.5000607@codethink.co.uk>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Simon,

On 04/12/14 15:53, Simon Glass wrote:
 >> [715.979284 HC 0xd2]
 >
 > This is a reboot command - EC_CMD_REBOOT_EC. I wonder how/why your
 > U-Boot might issue that command?

 From my investigation, Coreboot is issuing this reboot command, because 
the Coreboot payload (which in my case is U-Boot) for some reason isn't 
valid. With CONFIG_PANIC_HANG defined there is no UART output from the 
EC at all.
Is a prepended SPL needed before the U-Boot+DTB payload?

When flashing U-Boot from the Chromium OS branch it gives some UART 
output but freezes because SPI and MMC driver are not working properly 
("emerge-nyan chromeos-u-boot").
Is this the best starting point to develop a working U-Boot?

Regards,
Simon