Even if I add your recommending code to linux/arch/arm/boot/compressed/head.
S, the result is unchanged.

I'd like to tell you more information of my environment for exact point.

1. Target system: Ebsa285 & Backplane b/d
2. bios 1.06, angelboot 1.10, linux 2.2.12rmk are used.
3. I've succeeded in booting off flash. Flash configuration is as followings
   Image 0: bios
   Image 1,2: linux kernel
   Of course, I've modified bios for booting from flash.
   
In this configuration, I've seen boot message from linux kernel well at my
monitor.
So I've decided to try download kernel using angelboot for removing rom
burning.
In my knowlege, angelboot just downloads image to base address in target
b/d & jumps to entry point, doesn't it?
As I told you previous mail, I could know that kernel image started well
using angelboot with LED check before problem happened.
Is there any more actions to be needed? I think If I put some codes of bios
in head.S, it can work. How do you think about it?

Or I'd like to know the other development environment the other engineer is
using. 
Please help ...




-----Original Message-----
From: Nicolas Pitre [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 24, 2000 11:53 PM
To: James Kim(Jin-Soo)
Cc: [EMAIL PROTECTED]
Subject: Re: How to download kernel using angelboot.




On Fri, 24 Mar 2000, James Kim(Jin-Soo) wrote:

> Hello!
> 
> Is there anybody to let me execute kernel using angelboot utility? My
> target b/d is ebsa285.
> Please check my procedure for downloading.
> 
> 1) Build kernel image using "make zImage" : kernel version is 2.2.12rmk1
> 2) Download kernel using "angelboot -v -d /dev/cua0 -S 115200 -e 8000 -b
> 8000 -0 0 -1 4 zImage"
> 3) I've checked whether it works or not with LED. It worked well until
> flush I,D cache instruction starts in .Larmv4_flush_early.
>    So I've removed 3 lines "mcr p15, 0 , r0, c7, c7" , "mcr p15, 0, r0,
c7,
> c10, 4", "mcr p15, 0, r0, c8, c7".
>    After removing 3 lines, I could know it's working until MMU on. 
>    After MMU enabled, I can't trace anymore...
> 
> Is there any missing part for downloading or building image?

In the entry code somewhere (in linux/arch/arm/boot/compressed/head.S),
you must get control from angel.  Add the following code:

---
                @ need to enter SVC mode
#define angel_SWIreason_EnterSVC 0x17   /* from arm.h, in angel source */
#define angel_SWI_ARM 0x123456
                mov     r0, #angel_SWIreason_EnterSVC
                swi     #angel_SWI_ARM

                @ turn off interrupts to prevent the angel from running
                mrs     r0, cpsr
                orr     r0, r0, #0xc0
                msr     cpsr, r0
---


Nicolas


unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++        Please use [EMAIL PROTECTED] for
++
++                        kernel-related discussions.
++

unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++        Please use [EMAIL PROTECTED] for           ++
++                        kernel-related discussions.                      ++

Reply via email to