From mboxrd@z Thu Jan 1 00:00:00 1970 From: ba_f Date: Mon, 12 Oct 2015 15:52:28 +0200 Subject: [U-Boot] U-Boot version issue In-Reply-To: References: <5c515fb3b2f956768d10d2e2c2e9402e@rbg.informatik.tu-darmstadt.de> <20150924055526.0F0B1380905@gemini.denx.de> <2e2178cf246f80c4f9098dce357e5528@rbg.informatik.tu-darmstadt.de> <20150929161543.8D8C0380905@gemini.denx.de> <9bdc7ea10b3133177ed8106a8df76fc9@rbg.informatik.tu-darmstadt.de> Message-ID: <5167cf5319666ef3c0df793c9d1db0ea@rbg.informatik.tu-darmstadt.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 2015-10-09 15:02, schrieb Simon Glass: > +Marcel who is the maintainer > > Hi, > > On 8 October 2015 at 14:56, ba_f > wrote: >> >> Hello, >> >> >> i have an issue with different U-Boot versions, and i have no clue >> what's >> the problem. >> Maybe someone's got an idea? >> >> Working on Xilinx' ARM Platform i use U-Boot version >> u-boot-xlnx-xilinx-v14.6.01, and it's all good with that one and even >> lower >> versions. >> But, using u-boot-xlnx-xilinx-v14.7 or higher results in serious CPU >> errors: >> >> uboot> fatload mmc 0 0x00ffffc0 bootstrap.uimage >> reading bootstrap.uimage >> 6139968 bytes read in 528 ms (11.1 MiB/s) >> uboot> go 0x01000000 > > What is that bootstrap program? Maybe you need to turn off the cache > before starting it with the 'dcache off' command? > Indeed DCache is the problem. The old u-boot had CONFIG_SYS_DCACHE_OFF=y. Thanks, ba_f