From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Thu, 23 Feb 2012 16:24:15 +0100 Subject: [U-Boot] u-boot for SPEAr1310 In-Reply-To: <201202231622.28128.sr@denx.de> References: <20120223141718.GB18792@elf.ucw.cz> <201202231549.02184.marek.vasut@gmail.com> <201202231622.28128.sr@denx.de> Message-ID: <201202231624.15685.marek.vasut@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 Thursday 23 February 2012 15:49:02 Marek Vasut wrote: > > > My experience is mostly SPEAr600 only right now. Not sure if there are > > > bigger differences between those SoC's in the BootROM. > > > > I believe the spear600 is totally different from 1300. But, simple: > > > > reset halt ; load ... ; go ... > > > > combo should work I believe. In case you're loading some U-Boot SPL, it's > > very good idea to put an "asm volatile("x : b x");" line into the SPL to > > make the CPU loop instead of try loading uboot. Since if the CPU is > > looping, you can break it with BDI, if it isn't looping and jumps to some > > garbage, it usually ends in undefined state and bootrom might further > > tamper with the CPU configuration. > > Yes, good point. But a "STARTUP RESET ;no code is executed after reset" > seems to solve this problem as well. At least for me on SPEAr600. I know. > Since I broke my SPL from time to time. ;) Ah that's good idea indeed, though sometimes you might want to break the execution after the BootROM, since bootrom might be doing some mandatory chip init. M > > Best regards, > Stefan > > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de