Re: [Ltib] (no subject)

We changed uBoot to boot from SD card something like this:

We boot Freescale target via NFS or TFTP:

On the target, SCP from the host to the target:

Run: scp <SSH_SERVER_NAME>@<IPADDRESS>:<SUBDIR of uImage>/uImage . (. Is current directory on the target. Must be R/W.)

Run: cat uImage > /dev/sda1

You need a partition (mount point) for each of uboot, uboot-env, uimage, dtb, filesystem.

When you copied all to SD card, reboot and stop uboot.

Change the uboot env to boot from SD card.

>setenv bootargs root=b301 rootfstype=ext2 (or squashfs) rootdelay=3 console=ttyS0,115200

>saveenv

>boot

From: address@hidden [mailto:address@hidden On Behalf Of Giuseppe Ventura
Sent: Thursday, March 08, 2012 10:58 AM
To: address@hidden
Subject: Re: [Ltib] (no subject)

I have create with LTIB kernel, bootloader and rootfs.

Now how to flash SD?

I have finding this script, but dont work. WHY?

thanks

Date: Thu, 8 Mar 2012 09:29:44 +0530
From: address@hidden
To: address@hidden
Subject: [Ltib] (no subject)

hi..

i tried to setup nfsroot command on my target board(MCF5475) but i got this problem

U-Boot 1.3.3 (Mar 2 2012 - 13:54:30)

CPU: Freescale MCF5485

CPU CLK 200 Mhz BUS CLK 100 Mhz

Board: Freescale FireEngine 5475 EVB

I2C: ready

DRAM: 64 MB

FLASH: 8 MB

In: serial

Out: serial

Err: serial

Net: FEC0, FEC1

Hit any key to stop autoboot: 0

## Booting kernel from Legacy Image at ff850000 ...

Image Name: Linux Kernel Image

Image Type: M68K Linux Kernel Image (uncompressed)

Data Size: 2285568 Bytes = 2.2 MB

Load Address: 00020000

Entry Point: 00020000

Verifying Checksum ... OK

Loading Kernel Image ... OK

Linux version 2.6.25 (address@hidden) (gcc version 4.2.3 (Sourcery G++ Lite 4.2-125)) #20 Wed Mar 7 16:28:05 IST 2012

starting up linux startmem 0x288000, endmem 0x4000000, size 61MB

console [ttyS0] enabled

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8156

Kernel command line: root=/dev/nfs rw nfsaddrs=192.168.0.1:/tftpboot/ltib ip=192.168.0.254:192.168.0.1:192.168.0.1:255.255.255.0::eth

0:off mtdparts=physmap-flash.0:2560k(kernel)ro,5376k(root)

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

Console: colour dummy device 80x25

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

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

Memory: 62544k/62544k available (1704k kernel code, 1208k data, 72k init)

SLUB: Genslabs=13, HWalign=16, Order=0-2, MinObjects=8, CPUs=1, Nodes=1

Mount-cache hash table entries: 1024

net_namespace: 152 bytes

NET: Registered protocol family 16

MCF5485x INIT_DEVICES

NET: Registered protocol family 2

IP route cache hash table entries: 2048 (order: 0, 8192 bytes)

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

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

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

m547x_8x DMA: Initialize Multi-channel DMA API v1.0

io scheduler noop registered

io scheduler anticipatory registered

io scheduler deadline registered

io scheduler cfq registered (default)

IPCPLD1 Driver Registered with MAJOR no = 249

IPCPLD2 Driver Registered with MAJOR no = 250

IPGPIO Driver Registered with MAJOR no = 246

RTS driver registered with MAJOR no = 248

LINK STAT Driver Registered with MAJOR no = 245

ColdFire internal UART serial driver version 1.00

ttyS0 at 0xf0008600 (irq = 99) is a builtin ColdFire UART

ttyS1 at 0xf0008700 (irq = 98) is a builtin ColdFire UART

ttyS2 at 0xf0008800 (irq = 97) is a builtin ColdFire UART

ttyS3 at 0xf0008900 (irq = 96) is a builtin ColdFire UART

brd: module loaded

loop: module loaded

FEC ENET (DMA) Version 0.20

eth0: ethernet 00:60:72:00:00:01

eth1: ethernet 00:60:72:00:00:02

physmap platform flash device: 007fffff at ff800000

physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank

NOR chip too large to fit in mapping. Attempting to cope...

Amd/Fujitsu Extended Query Table at 0x0040

physmap-flash.0: CFI does not contain boot bank location. Assuming top.

number of CFI chips: 1

cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.

Reducing visibility of 8192KiB chip to 8191KiB

2 cmdlinepart partitions found on MTD device physmap-flash.0

Creating 2 MTD partitions on "physmap-flash.0":

0x00000000-0x00280000 : "kernel"

0x00280000-0x007c0000 : "root"

mice: PS/2 mouse device common for all mice

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

NET: Registered protocol family 15

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

IP-Config: Complete:

device=eth0, addr=192.168.0.254, mask=255.255.255.0, gw=192.168.0.1,

host=192.168.0.254, domain=, nis-domain=(none),

bootserver=192.168.0.1, rootserver=192.168.0.1, rootpath=

Looking up port of RPC 100003/2 on 192.168.0.1

*** LINE 1111 *** FORMAT=4

Current process id is 0

BAD KERNEL TRAP: 00000000

PC: [<00156058>] dev_hard_start_xmit+0x0/0x260<0>

SR: 2000 SP: 0024de50 a2: 00228410

d0: 00000000 d1: 00000000 d2: 00000000 d3: ffff8c8d

d4: 00156058 d5: 0002b89a a0: 00156058 a1: 03052d8c

Process swapper (pid: 0, stackpage=0022a410)

Stack from 0024de50:

<0> 00000000<0> 00000000<0> ffff8c8d<0> 00156058<0> 0002b89a<0> 00156058<0> 03052d8c<0> 00228410

<0> 00000000<0> ffffffff<0> 00000000<0> 0024df8c<0> 00000002<0> 402c2000<0> 00156058<0> 001636ce

<0> 03110f00<0> 03061800<0> 00000000<0> c0a80001(0xc0a80001)<0> 00000004<0> 00273338<0> 00273538<0> 00273738

<0> 03061800<0> 03110f00<0> 03096fc0<0> 03061800<0> 00158d56<0> 03061800<0> 03022200<0> c0a800fe(0xc0a800fe)

<0> 03096fc4<0> 0018dbd6<0> 03110f00<0> 00000806<0> c0a80001(0xc0a80001)<0> 03061800<0> c0a800fe(0xc0a800fe)<0> 00000000

<0> 0306192a<0> 00000000<0> ffff8cf1<0> 00000000<0> 0024df6c<0> 03022248<0> 03110e60<0> 03022200

Call Trace:

<0> [<0003307c>]<0> [<0015e41a>]<0> [<0015e2e0>]<0> [<00033306>]

<0> [<0002fd12>]<0> [<00022504>]<0> [<001c55a0>]<0> [<0002fd68>]

<0> [<0002b89a>]<0> [<00023adc>]<0> [<0002b89a>]<0> [<0002160c>]

<0> [<0002161c>]<0> [<000214fa>]<0> [<0002b89a>]

Kernel panic - not syncing: Aiee, killing interrupt handler!

can any one give solution for this problem...................................

_______________________________________________ LTIB home page: http://ltib.org Ltib mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/ltib

From:	Reer, Carolyn (SA-1)
Subject:	Re: [Ltib] (no subject)
Date:	Thu, 8 Mar 2012 12:22:39 -0500