Image Loading Issue

[narreddisivapra]

Hi,

        At present I am working on MPC8323E-RDB development board. I had shipped with a cd containig bsp for respective board. In board bring-up processes, I followed Readme.txt. At first time I loaded uboot.bin and kernel image (through tftp) successfully, but now I am trying to load linux image over tftp.. I am getting following display..

........

........

TFTP from server 192.168.1.14; our IP address is 192.168.1.232
Filename '/uImage'.
Load address: 0x200000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#########################################
done
Bytes transferred = 1536489 (1771e9 hex)
Using FSL UEC0 device
TFTP from server 192.168.1.14; our IP address is 192.168.1.232
Filename '/mpc832x_rdb.dtb'.
Load address: 0x400000
Loading: #
done
Bytes transferred = 5070 (13ce hex)
## Booting image at 00200000 ...
Image Name: Linux-2.6.20.6-rt8
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1536425 Bytes = 1.5 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
=>

Please help me in understanding this issue.

Thanks and Regards,

Siva Prakash Reddy N

[Pavel]

Your dump does not show command for rootfs loading.

test your board using the following command sequence.

1. Load images from TFTP

Tftp images to the board, then boot it up.

=>tftp 2000000 uImage

=>tftp 2400000 rootfs.ext2.gz.uboot

=>tftp 400000 /mpc832x_rdb.dtb

2. Boot up board

=>bootm 2000000 2400000 400000

It looks like that your RAM disk incorrectly prepared

Use the following command sequence for adding file to RAM disk image.

1. rename your RAM disk image to rootfs.ext2.gz.uboot
2. sudo apt-get install u-boot-tools

Following are the steps for adding files into rootfilesystem:

2. dd if=rootfs.ext2.gz.uboot of=rootfs.ext2.gz bs=64 skip=1
3. gunzip rootfs.ext2.gz
4. mkdir /mnt/iso_1
5. sudo mount -oloop rootfs.ext2 /mnt/iso_1
6. Now, one can copy files into appropriate location under “./mnt/iso_1” directory.
7. sudo umount /mnt/iso_1
8. gzip -9 rootfs.ext2
9. mkimage -A ppc -O linux -T ramdisk -C gzip -n 'rootfs.ext2.gz.uboot' -d rootfs.ext2.gz rootfs.ext2.gz.uboot

Have a great day,
Pavel Chubakov

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[narreddisivapra]

Hi,

    I tried to load kernel and RootFS in to MPC8323E-RDB and it loaded successfully. I given my network IP settings to the board and tried for ping to it from my pc, but it is not reacting. I observed two things.,

1. Upon bootup, if I type "ping <ip address>" it is replying with "Host is alive".

2. After loading Kernel and RootFS images into board (via TFTP), I tried "ping <ipaddress>" but I am getting "ping: sendto: Network is unreachable".

What is the difference between point 1 and 2 .?

And also I observed the following thing before login into the Board..

physmap-flash flash: Using OF partition information
Creating 4 MTD partitions on "flash":
0x00000000-0x00080000 : "U-Boot"
0x00080000-0x000a0000 : "dtb"
0x000a0000-0x00220000 : "Kernel"
0x00220000-0x01000000 : "rootfs"
usbmon: debugfs is not available
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
i2c /dev entries driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RAMDISK: Compressed image found at block 0
Time: timebase clocksource has been installed.
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 124k init
Setting the hostname to MPC_8323
Mounting filesystems
Starting syslogd and klogd
Running sysctl
Setting up networking on loopback device:
Setting up networking on eth0:
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device
Adding static route for default gateway to 192.168.1.100:
SIOCADDRT: No such device
Setting nameserver to 192.168.1.13 in /etc/resolv.conf:
Starting inetd:
Starting the boa webserver:
/sbin/ip
/etc/rc.d/init.d/dhcp: Network interface not present

Welcome to Freescale Semiconductor Embedded Linux Environment

!!!!! WARNING !!!!!!!

The default password for the root account is: root
please change this password using the 'passwd' command
and then edit this message (/etc/issue) to remove this message

MPC_8323 login: root
Password:
~ #

What is the meaning for "/etc/rc.d/init.d/dhcp: Network interface not present".?

Please respond as soon as possible.

Thanks and Regards,

Siva Prakash Reddy N

[narreddisivapra]

Hello,

    Please, respond to my query.

Thanks and Regards,

Siva Prakash Reddy N

[narreddisivapra]

Hi,

    I am able to creating Kernel Image, RootFs and DTB files for MPC8323E-RDB board using LTIB. When I am trying to load images into the board, "RAMDisk Image" is giving following issue...

TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RAMDISK: Compressed image found at block 0
Time: timebase clocksource has been installed.
RAMDISK: incomplete write (16384 != 32768) 30703616
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 136k init
attempt to access beyond end of device
ram0: rw=0, want=72892, limit=60000
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=
1121, block=36445
Warning: unable to open an initial console.
attempt to access beyond end of device
ram0: rw=0, want=72936, limit=60000
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=
1297, block=36467
Kernel panic - not syncing: Attempted to kill init!
Call Trace:
[C0405E60] [C0008208] (unreliable)
[C0405EA0] [C0026EF8]
[C0405EF0] [C002B43C]
[C0405F30] [C002B474]
[C0405F40] [C000F5F8]
--- Exception: c01 <0>Rebooting in 180 seconds..

Why this warning is coming and which factors effecting this.? Please reply as soon as possible.

Thanks and Regards,

Siva Prakash Reddy N