[U-Boot] U-Boot SPL 2016.09-rc1 on NTC C.H.I.P.

[Tom Rini]

On Tue, Aug 23, 2016 at 08:05:59PM +0200, Marcus Glocker wrote:
> On Mon, Aug 22, 2016 at 09:55:01AM +0200, Boris Brezillon wrote:
> 
> > +Glaucio who is facing the same problem but on a cubieboard2.
> > 
> > On Sun, 21 Aug 2016 16:14:39 +0200
> > Boris Brezillon <boris.brezillon at free-electrons.com> wrote:
> > 
> > > Hi,
> > > 
> > > On Sun, 21 Aug 2016 12:03:19 +0200
> > > Hans de Goede <hdegoede at redhat.com> wrote:
> > > 
> > > > Hi,
> > > > 
> > > > On 21-08-16 11:01, Marcus Glocker wrote:  
> > > > > On Sat, Aug 20, 2016 at 03:05:38PM -0400, Tom Rini wrote:
> > > > >    
> > > > >> On Sat, Aug 20, 2016 at 07:26:19AM +0200, Marcus Glocker wrote:    
> > > > >>> Hello,
> > > > >>>
> > > > >>> While U-Boot SPL 2015.10 works fine on my allwinner,sun5i-r8 board I
> > > > >>> face following issue with U-Boot SPL 2016.09-rc1 on it:
> > > > >>>
> > > > >>> 	bash-4.3# cu -l /dev/cuaU0 -s 115200
> > > > >>> 	Connected to /dev/cuaU0 (speed 115200)
> > > > >>>
> > > > >>> 	U-Boot SPL 2016.09-rc1 (Jul 31 2016 - 16:37:00)
> > > > >>> 	DRAM: 512 MiB
> > > > >>> 	CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
> > > > >>> 	Trying to boot from NAND
> > > > >>> 	### ERROR ### Please RESET the board ###
> > > > >>>
> > > > >>> Any ideas what change did cause this or where to start looking after?    
> > > 
> > > Markus, can you share your .config?
> > > I tested the different bits while submitting the NAND driver and the
> > > SPL NAND driver improvements and it was working fine.
> > > I'll try to test 2016.09-rc1 tomorrow.
> > 
> > Just tried to boot a mainline uboot on my CHIP and it boots fine [1].
> > Here is my .config [2], can you compare yours with this one?
> > 
> > Can you also detail how you flash the images?
> 
> Thanks for sharing your configuration!  Based on that I was able to
> narrow down the configuration parameter which makes SPL 2016.09-rc1 now
> work on my allwinner,sun5i-r8 board as well:
> 
> 	+CONFIG_USE_PRIVATE_LIBGCC=n
> 
> When I don't set it explicitly I get 'CONFIG_USE_PRIVATE_LIBGCC=y' in
> my .config.  Could it be that it was set to 'n' by default in previous
> releases?

What toolchain exactly are you using?  Thanks!

-- 
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/20160823/362ad097/attachment.sig>