public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] pine64 and "sunxi: Move the SPL stack top to 0x1A000 on Allwinner A64/A80"
Date: Thu, 4 Aug 2016 11:36:01 -0400	[thread overview]
Message-ID: <20160804153601.GF9942@bill-the-cat> (raw)
In-Reply-To: <62b2fd60-f427-b58c-bdef-90e0605f9415@arm.com>

On Thu, Aug 04, 2016 at 04:14:21PM +0100, Andre Przywara wrote:
> Hi,
> 
> On 04/08/16 16:01, Tom Rini wrote:
> > Hey guys,
> > 
> > I just started trying out my Pine64 1GB and mainline U-Boot and I've
> > found that:
> > commit 1a83fb4a17d959d7b037999ab7ed7e62429abe34
> > Author: Siarhei Siamashka <siarhei.siamashka@gmail.com>
> > Date:   Tue May 31 01:48:06 2016 +0300
> > 
> >     sunxi: Move the SPL stack top to 0x1A000 on Allwinner A64/A80
> > 
> > is breaking boot for me.  boot0 seems to run fine and then the last bit
> > of output that I get is:
> > boot0: start load other image
> > boot0: Loading BL3-1
> > Loading file 0 at address 0x40000000,size 0x00000200 success
> > boot0: Loading scp
> > Loading file 2 at address 0x00040000,size 0x0000c200 success
> > set arisc reset to de-assert state
> > Ready to disable icache.
> > Jump to secend Boot.
> > NOTICE:  BL3-1: Running in SRAM A2 (@0x44000)
> > NOTICE:  Configuring SPC Controller
> > NOTICE:  BL3-1: v1.0(debug):d697594
> > NOTICE:  BL3-1: Built : 09:15:57, Aug  4 2016
> > NOTICE:  Configuring AXP PMIC
> > NOTICE:  PMIC: already configured for RSB
> > NOTICE:  PMIC: setup successful
> > INFO:    BL3-1: Initializing runtime services
> > INFO:    BL3-1: Preparing for EL3 exit to normal world
> > INFO:    BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9
> > 
> > I'm using d697594 from
> > https://github.com/apritzel/arm-trusted-firmware.git for ATF and
> > boot0.img from the 20160701 Debian "longsleep" image.  Any ideas?
> 
> Yes, we were experiencing similar issues, basically it's stuck in
> start.S, as far as I could quickly check.
> Siarhei and I were doubtful that this commit (which we eyed at before)
> could be the culprit, as it _should_ affect only SPL code, which we
> don't use atm.

It's not touching SPL code tho.  You're changing CONFIG_SYS_INIT_SP_ADDR
which is the start of _main in arch/arm/lib/crt0_64.S

> Tom, can you try reboot several times? You can short pin 4 and 6 on the
> "EXP" connector (for instance with a screwdriver ;-), if you don't have
> a reset button soldered.
> I experienced it works occasionally, which gives me the creeps, tbh.

I'm using the official UART adapter so my EXP connector is full :)

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160804/3c12bc36/attachment.sig>

  reply	other threads:[~2016-08-04 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 15:01 [U-Boot] pine64 and "sunxi: Move the SPL stack top to 0x1A000 on Allwinner A64/A80" Tom Rini
2016-08-04 15:14 ` Andre Przywara
2016-08-04 15:36   ` Tom Rini [this message]
2016-08-04 15:40     ` Tom Rini
2016-08-04 19:58       ` Siarhei Siamashka
2016-08-04 20:43         ` André Przywara
2016-08-04 21:05         ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160804153601.GF9942@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox