Problem for install Linux SAML9260 Board

Hi Guys,

I am new in arm. Now I have the problem when I try to recovery the Linux System in SAML9260 Board. The system seems cannot find the kernel in the system. Can you please tell me how to fix the problem? The steps I have done and the corresponding output are displayed below. Thank you.

I have already installed the ATMEL AT91-ISP package; Reboot the computer after the installation and copy the NANDFLASH.tcl file from the ATMEL directory on the CD

to “C:\Program Files\ATMEL Corporation\AT91-ISP v1.9\SAM-BA v2.5\lib\AT91SAM9260-EK”; Remove the NANDF_E and DF_E jumpers on the SAM9-L9260 board and power it up; Connect an USB cable to the USB_D connector on the board and wait for the board to be

detected; Close the NANDF_E jumper and run the AT91SAM9260_demo_linux_NandFlash.bat file from the sam9-l9260-samba directory.

The output of the system is displayed below after I powered up.

/*********** System Output On Hyper Terminal *****************/

AT91Bootstrap loading from 0x8400…

U-Boot 1.2.0 (Apr 18 2008 - 12:47:19)

DRAM: 64 MB

NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,

3V 8-bit)

512 MiB

In: serial

Out: serial

Err: serial

KS8721 PHY Detected

No link

MAC: error during RMII initialization

Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x100000, size 0x1a2828

1714216 bytes read: OK

Booting image at 21500000 …

Image Name: Linux-2.6.23

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1714152 Bytes = 1.6 MB

Load Address: 20008000

Entry Point: 20008000

Verifying Checksum … OK

OK

Starting kernel …

Uncompressing Linux…

… done, booting the kernel.

Linux version 2.6.23 (ivan@debian.l123.org) (gcc version 4.1.2) #5 PREEMPT Sun O

ct 14 02:01:51 EEST 2007

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

Machine: Olimex SAM9-L9260

Memory policy: ECC disabled, Data cache writeback

Clocks: CPU 180 MHz, master 90 MHz, main 18.432 MHz

CPU0: D VIVT write-back cache

CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets

CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets

Built 1 zonelists in Zone order. Total pages: 16256

Kernel command line: mem=64M console=ttyS0,115200, noinitrd root=/dev/mtdblock1

rootfstype=jffs2

AT91: 96 gpio irqs in 3 banks

PID hash table entries: 256 (order: 8, 1024 bytes)

Console: colour dummy device 80x30

console [ttyS0] enabled

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory: 64MB = 64MB total

Memory: 61336KB available (2732K code, 686K data, 108K init)

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

NET: Registered protocol family 16

Generic PHY: Registered new driver

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

NetWinder Floating Point Emulator V0.97 (double precision)

audit: initializing netlink socket (disabled)

audit(0.560:1): initialized

JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.

io scheduler noop registered

io scheduler anticipatory registered

io scheduler deadline registered

io scheduler cfq registered (default)

atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL

atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL

atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL

RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize

loop: module loaded

MACB_mii_bus: probed

eth0: Atmel MACB at 0xfffc4000 irq 21 (00:00:00:00:00:00)

eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)

block2mtd: version $Revision: 1.30 $

NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bi

t)

Scanning device for bad blocks

Bad eraseblock 0 at 0x00000000

Bad eraseblock 1 at 0x00020000

Bad eraseblock 2 at 0x00040000

Bad eraseblock 3 at 0x00060000

Bad eraseblock 8 at 0x00100000

Bad eraseblock 9 at 0x00120000

Bad eraseblock 10 at 0x00140000

Bad eraseblock 11 at 0x00160000

Bad eraseblock 12 at 0x00180000

Bad eraseblock 13 at 0x001a0000

Bad eraseblock 14 at 0x001c0000

Bad eraseblock 15 at 0x001e0000

Bad eraseblock 16 at 0x00200000

Bad eraseblock 17 at 0x00220000

Bad eraseblock 18 at 0x00240000

Bad eraseblock 19 at 0x00260000

Bad eraseblock 20 at 0x00280000

Bad eraseblock 21 at 0x002a0000

Bad eraseblock 32 at 0x00400000

Bad eraseblock 33 at 0x00420000

Bad eraseblock 34 at 0x00440000

Bad eraseblock 35 at 0x00460000

Bad eraseblock 36 at 0x00480000

Bad eraseblock 37 at 0x004a0000

Bad eraseblock 38 at 0x004c0000

Bad eraseblock 39 at 0x004e0000

Bad eraseblock 40 at 0x00500000

Bad eraseblock 41 at 0x00520000

Bad eraseblock 42 at 0x00540000

Bad eraseblock 43 at 0x00560000

Bad eraseblock 44 at 0x00580000

Bad eraseblock 45 at 0x005a0000

Bad eraseblock 46 at 0x005c0000

Bad eraseblock 47 at 0x005e0000

Bad eraseblock 48 at 0x00600000

Bad eraseblock 49 at 0x00620000

Bad eraseblock 50 at 0x00640000

Bad eraseblock 51 at 0x00660000

Bad eraseblock 52 at 0x00680000

Bad eraseblock 53 at 0x006a0000

Bad eraseblock 54 at 0x006c0000

Bad eraseblock 55 at 0x006e0000

Bad eraseblock 56 at 0x00700000

Bad eraseblock 57 at 0x00720000

Bad eraseblock 58 at 0x00740000

Bad eraseblock 59 at 0x00760000

Bad eraseblock 60 at 0x00780000

Bad eraseblock 61 at 0x007a0000

Bad eraseblock 62 at 0x007c0000

Bad eraseblock 63 at 0x007e0000

Creating 2 MTD partitions on “NAND 512MiB 3,3V 8-bit”:

0x00000000-0x00a00000 : “Bootloader Area”

0x00a00000-0x20000000 : “User Area”

at91_ohci at91_ohci: AT91 OHCI

at91_ohci at91_ohci: new USB bus registered, assigned bus number 1

at91_ohci at91_ohci: irq 20, io mem 0x00500000

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 2 ports detected

Initializing USB Mass Storage driver…

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver libusual

udc: at91_udc version 3 May 2006

ether gadget: using random self ethernet address

ether gadget: using random host ethernet address

usb0: Ethernet Gadget, version: May Day 2005

usb0: using at91_udc, OUT ep2 IN ep1 STATUS ep4

usb0: MAC 4a:95:83:3a:d3:bb

usb0: HOST MAC ea:85:03:16:31:19

usb0: RNDIS ready

mice: PS/2 mouse device common for all mice

TCP cubic registered

Initializing XFRM netlink socket

NET: Registered protocol family 1

NET: Registered protocol family 17

NET: Registered protocol family 15

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

VFS: Mounted root (jffs2 filesystem).

Freeing init memory: 108K

Warning: unable to open an initial console.

Kernel panic - not syncing: No init found. Try passing init= option to kernel.

I’m having the same issue, did you ever get this fixed?