From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Gardet Date: Mon, 27 Jul 2015 18:39:16 +0200 Subject: [U-Boot] [U-Boot, 1/2] ti: armv7: enable EXT support in SPL (using ti_armv7_common.h) In-Reply-To: References: <1434459610-6429-2-git-send-email-guillaume.gardet@free.fr> <20150619202520.GE28577@bill-the-cat> <20150724140459.GL25532@bill-the-cat> Message-ID: <55B65EB4.4070303@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, Le 24/07/2015 17:22, Ash Charles a ?crit : > On Fri, Jul 24, 2015 at 7:04 AM, Tom Rini wrote: >> Can you give us more details on the exact nature of the failure? Thanks! > Oh sorry--that wasn't clear! The boards appear to get stuck in SPL > before anything can be printed to the console. Basically, I power on, > see gunk from the boot rom on the console port, and then...nothing. gunk? I think ROM should display nothing if MLO/SPL is found and if nothing is found, you get a '60' for UART boot. > Happy to test further if there is a way to narrow down what precisely > is failing. I have no original beagle, only a xM version with DM3730 which seems to be unaffacted. But, in Overo config, There are those lines : #undef CONFIG_SPL_MAX_SIZE #define CONFIG_SPL_MAX_SIZE (64*1024) #undef CONFIG_SPL_TEXT_BASE #define CONFIG_SPL_TEXT_BASE 0x40200000 Which bump SPL size from 54*1024 to 64*1024 and moves SPL text base from 0x40200800 to 0x40200000. Any reason for that? What happens if you use original values? What is the size of your MLO? Guillaume > > --Ash >