From mboxrd@z Thu Jan  1 00:00:00 1970
From: Shawn Jin <shawnxjin@gmail.com>
Date: Mon, 20 Dec 2004 11:40:27 -0800
Subject: [U-Boot-Users] u-boot and linux-2.6.9
In-Reply-To: <OFA94675DE.B9E9439A-ONC1256F70.004A5D92-C1256F70.004AEC93@philips.com>
References: <OFA94675DE.B9E9439A-ONC1256F70.004A5D92-C1256F70.004AEC93@philips.com>
Message-ID: <c3d0340b041220114018ecf2ca@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

> Integrator-AP # bootm 24400000                                              

What core mdoule are you using?

>    Image Name:   Linux-2.6.9                                                
>    Image Type:   ARM Linux Kernel Image (uncompressed)                      
>    Data Size:    1216080 Bytes =  1.2 MB                                    
>    Load Address: 00008000 
>    Entry Point:  00008000                                                   

By default IntegratorAP has SDRAM starting at 0. 

> data abort                                                                  
>     
> pc : [<0000801c>]    lr : [<0100bcbc>]                                      
> sp : 00fd7bd4  ip : 00fd7bc4  fp : 00fd7c10                                 
> r10: 00000000  r9 : 00fd7c84  r8 : 00fd7fdc                                 
> r7 : 0100f1b4  r6 : 0100f1b4  r5 : 00000000  r4 : 24400040                  
> r3 : e1a00001  r2 : 00000100  r1 : e1a00000  r0 : 00000000                  
> Flags: nZCv  IRQs off  FIQs off  Mode SVC_32                                
> Resetting CPU ...   

The data abort may not be caused by linux code, though the PC shows
execution is at 0x801c. Instead incompatible cache clear instruction
will cause this abort. Check the implementation of
cleanup_before_linux() on your CPU and make sure the cache is disabled
using the right instruction.

Regards,
-Shawn.