From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Andreas_Bie=C3=9Fmann?= Date: Wed, 17 Aug 2016 13:03:34 +0200 Subject: [U-Boot] Boot failure with a AT91RM9200 based custom board In-Reply-To: References: <0e253f4b-4583-84ec-c187-faa378e4ef4c@gmail.com> <01130678-3c4f-f56f-9f3c-db5af68165b3@biessmann.org> Message-ID: <6bb8a416bbfd3f4facce996959977d01@biessmann.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Peter, On 2016-08-17 11:31, Peter Kardos wrote: > On Mon, Aug 15, 2016 at 10:43 PM, Andreas Bie?mann > wrote: > >> Dear Peter, >> >> On 12.08.16 02:24, Peter Kardos wrote: >>> RAM Configuration: >>> Bank #0: 20000000 64 MiB >>> >>> DRAM: 64 MiB >>> initcall: 1000b424 >>> New Stack Pointer is: 23f23ed0 >>> initcall: 1000b6ac >>> initcall: 1000b640 >>> Relocation Offset is: 13f84000 >>> Relocating to 23f84000, new gd at 23f23ef0, sp at 23f23ed0 >> >> Could you please check, if the RAM initialisation is working >> properly? >> AFAIR there was some problem with the u-boot RAM initialisation >> for this >> board but never fixed (shame on me). Some set of known data and >> read >> back before relocation should do the check. > > Yeah, this is my guess as well, as things seem to work up to this > point (continue exec from RAM). > > Thanks for the pointer, i'll have a look at the init magic and compare > it with the old from v1.1.4. Would be great if you come with a solution, so I could fix the at91rm9200ek board too. > I guess the easiest way would be to mod the relocation routine and > read back what was written... sounds good as a quick test Andreas