From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Mon, 6 Apr 2015 20:48:45 +0200
Subject: [U-Boot] printf("%d") breaks u-boot 2015.01+
In-Reply-To: <20150406181444.GB23259@amd>
References: <1427752878-18426-1-git-send-email-dinguyen@opensource.altera.com>
 <201504061659.55725.marex@denx.de> <20150406181444.GB23259@amd>
Message-ID: <201504062048.45467.marex@denx.de>
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

On Monday, April 06, 2015 at 08:14:44 PM, Pavel Machek wrote:
> On Mon 2015-04-06 16:59:55, Marek Vasut wrote:
> > On Monday, April 06, 2015 at 04:40:09 PM, Pavel Machek wrote:
> > > Hi!
> > > 
> > > In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
> > > hangs. (Usually, that's after "DRAM: " message).
> > 
> > printf("%d") expects an argument, so could it be that it touches
> > random piece of memory and thus hangs?
> 
> It had an argument, sorry for confusion. I was actually doing this:
> the test with %s works, the one with %d kills it.
> 
> I suspect too small stack...?

Does this happen in the SPL ? You can check the stack placement and
utilization with BDI to verigy your hypothesis.

Best regards,
Marek Vasut