Cirrus Logic EP9302 (ARM9) Board

I just bought this board and when I cabled it up and applied power,
the hyperterm display showed Redboot progress getting as far as
uncompressing the Linux image before apparently rebooting from the start.

The quickstart guide claims that after loading the linux kernel and root
filesystem into memory,  linux will starts up, and booting will be
completed, and a shell prompt for linux will appear.

Well it aint happening.

Should I try to reload the linux image memory, or
just send the damn board back.

Anybody had this problem??


Start up messages appear below:


RedBoot(tm) bootstrap and debug environment [ROMRAM], Aug 22 2006         
                             
Non-certified release, version v2_0 - built 08:14:43, Aug 22 2006ARM920T)
Rev A                                                   

Platform: Cirrus Logic EDB9302 Board (ARM920T) Rev A
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x02000000, 0x00041e68-0x01fdd000 available
FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
== Executing boot script in 5.000 seconds - enter ^C to abort
RedBoot> fis load ramdisk.gz
RedBoot> fis load zImage
RedBoot> exec -r 0x800000 -s 0x800000 -c "console=ttyAM root=/dev/ram"
Using base address 0x00080000 and length 0x000df2ac
Uncompressing Linux...+Ethernet eth0: MAC address 00:00:00:00:54:33
IP: 192.168.0.93/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.0.13, DNS server IP: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version v2_0 - built 08:14:43, Aug 22 2006

Platform: Cirrus Logic EDB9302 Board (ARM920T) Rev A
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x02000000, 0x00041e68-0x01fdd000 available
FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
== Executing boot script in 5.000 seconds - enter ^C to abort

On Feb 1, 3:08=A0pm, "embedded07" <palapa...@excite.com> wrote:
> I just bought this board and when I cabled it up and applied power,
> the hyperterm display showed Redboot progress getting as far as
> uncompressing the Linux image before apparently rebooting from the start.
>
> The quickstart guide claims that after loading the linux kernel and root
> filesystem into memory, =A0linux will starts up, and booting will be
> completed, and a shell prompt for linux will appear.
>
> Well it aint happening.
>
> Should I try to reload the linux image memory, or
> just send the damn board back.
>
> Anybody had this problem??
>
> Start up messages appear below:
>
> RedBoot(tm) bootstrap and debug environment [ROMRAM], Aug 22 2006 =A0 =A0 =
=A0 =A0
>
> Non-certified release, version v2_0 - built 08:14:43, Aug 22 2006ARM920T)
> Rev A =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
>
> Platform: Cirrus Logic EDB9302 Board (ARM920T) Rev A
> Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
>
> RAM: 0x00000000-0x02000000, 0x00041e68-0x01fdd000 available
> FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
> =3D=3D Executing boot script in 5.000 seconds - enter ^C to abort
> RedBoot> fis load ramdisk.gz
> RedBoot> fis load zImage
> RedBoot> exec -r 0x800000 -s 0x800000 -c "console=3DttyAM root=3D/dev/ram"=

> Using base address 0x00080000 and length 0x000df2ac
> Uncompressing Linux...+Ethernet eth0: MAC address 00:00:00:00:54:33
> IP: 192.168.0.93/255.255.255.0, Gateway: 0.0.0.0
> Default server: 192.168.0.13, DNS server IP: 0.0.0.0
>
> RedBoot(tm) bootstrap and debug environment [ROMRAM]
> Non-certified release, version v2_0 - built 08:14:43, Aug 22 2006
>
> Platform: Cirrus Logic EDB9302 Board (ARM920T) Rev A
> Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
>
> RAM: 0x00000000-0x02000000, 0x00041e68-0x01fdd000 available
> FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
> =3D=3D Executing boot script in 5.000 seconds - enter ^C to abort


Assuming the board is loaded with the working linux kernel &
environment;

---------
if you are connecting the board through serial port:
Linux kernel serial port settings "may be" different from redboot's
serial settings.

try to change baudrate.

115200,8,1,n
9600,8,1,n
---------
if you are connecting the board through ethernet:

linux ip address "may be" different from redboot's ip address,
try to find default ip address.
---------

yusuf