From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Ruder Date: Thu, 24 Oct 2013 16:37:24 -0500 Subject: [U-Boot] ARM: interrupt_init before relocation, write fails In-Reply-To: References: Message-ID: <20131024213724.GA16569@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Oct 23, 2013 at 11:41:45AM -0600, Joe Kulikauskas wrote: > If I revert that patch, I don't see that problem. FWIW, I am working on a PXA270 target, and have had to revert this patch as well. I hadn't gotten around to tracking down where and why I was crashing though so hadn't emailed in a bug report yet. Now seeing as there's someone else now seeing it too I thought I would chime in with a "me too". Rob: CC'd you since you were the author and might have some insight. Full email in entirety below. - Andy On Wed, Oct 23, 2013 at 11:41:45AM -0600, Joe Kulikauskas wrote: > v2013.10-rc1 (and after) has a patch ( > http://lists.denx.de/pipermail/u-boot/2013-June/156298.html) which sets up > the abort stack before relocation. However, what I am seeing: > IRQ_STACK_START_IN > is in flash at that time, so this write fails. > > interrupt_init: > FF0A0FA8 e59f3010 LDR R3,ff0a0fc0 (ff0a0050=IRQ_STACK_START_IN) > > Before this patch, abort stack setup was done after relocation, so target > location is in RAM and writeable. > > interrupt_init: > 9FFB4020 e59f3010 LDR R3,9ffb4038 (9ffb3054=IRQ_STACK_START_IN) > > If I revert that patch, I don't see that problem. > > Joe Kulikauskas