Image generating by LTIB don't work

[DeanHuang]

Hi,

I was building a image by LTIB and flash into microSD, but there is no any output on my screen.

The following is my step:

1. Using ubuntu virtual machine  image offered by FreeScale imx53 QSB DVD.

2. run litb and change the settings

1. imx25_stack   ->  imx5x
2. u-boot : mx53_loco

others use the default value.

And I have the files:

<ltib>/rootfs/boot/u-boot.bin

<ltib>/rootfs/boot/uImage

<ltib>/rootfs.jffs2

3. mount jffs2

1. modprobe  mtdblock
2. modprobe mtdram total_size=5120 erase_size=256
3. dd if=rootfs.jffs2 of=/dev/mtdblock0
4. mkdir jffs_dir
5. mount -t jffs2 /dev/mtdblock0 jffs_dir

4. copy file to microSD, named /dev/sdb

1. dd if=rootfs/boot/u-boot.bin of=/dev/sdb bs=512
2. dd if=rootfs/boot/uImageof=/dev/sdb bs=512 seek=2048

partition:

1. fdisk /dev/sdb
2. u
3. n
4. p
5. 1
6. 8192
7. <enter>
8. w

copy rootfs.jffs2

1. mount /dev/sdb /mnt/hgfs
2. cd jffs_dir
3. cp -rpa * /mnt/hgfs
4. umount //mnt/hgfs
5. eject /dev/sdb

Are any step is wrong? Please tell me, thanks.

Attachment is the image file I build.

Original Attachment has been moved to: 326-rootfs.jffs2

[DeanHuang]

Hi,

Attachment is the original message and 'printenv' when booting.

Are you sure that you placed your SD_Card in a proper slot?

I use microSD.

Are you sure, If there are any configuration Switches, You have set them to boot from SD/MMC?

Default setting of i.MX53 QSB is microSD so I don't set anything.

About partition, I use the commands:

4. copy file to microSD, named /dev/sdb

1. dd if=rootfs/boot/u-boot.bin of=/dev/sdb bs=512
2. dd if=rootfs/boot/uImageof=/dev/sdb bs=512 seek=2048

partition:

1. fdisk /dev/sdb
2. u
3. n
4. p
5. 1
6. 8192
7. <enter>
8. w

Does the partition table match the picture?

Thanks.

[KrishnaPavan]

Hi,

When you get MX53-LOCO U-Boot>>

Can you do a "printenv" and add the log as a text file(easy to have a look at).

Are you sure that you placed your SD_Card in a proper slot?

Are you sure, If there are any configuration Switches, You have set them to boot from SD/MMC?

Regarding SD Card Partitions::

Follow this ( Image by Daiane )

[DeanHuang]

Hi Krishna,

I set some environment variables and it still doesn't work.

How should I solve this  problem?

Here is my message:

bootdelay=3

baudrate=115200

loadaddr=0x70800000

netdev=eth0

ethprime=FEC0

uboot=u-boot.bin

kernel=uImage

nfsroot=/opt/eldk/arm

bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp

bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm

ethact=FEC0

serverip=10.192.225.216

bootfile=uImage

bootcmd_mmc=run bootargs_base bootargs_mmc; mmc dev 0; mmc read ${loadaddr} 0x800 0x1800; bootm

bootcmd=run bootcmd_mmc

bootcmd_obds=ext2load mmc 0:1 0x70800000 /unit_tests/obds.bin; go 70800000

bootargs_base=setenv booargs console=ttymxc0,11520

bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p1 rootwait rw video=mxcdi1fb:GBR24,VGA-XGA di1_primary vga

stdin=serial

stdout=serial

stderr=serial
booargs=console=ttymxc0,11520

bootargs=console=ttymxc0,115200 ip=dhcp root=/dev/mmcblk0p1 rootwait root=/dev/mmcblk0p1 rootwait rw video=mxcdi1fb:GBR24,VGA-XGA di1_primary vga


Environment size: 943/131068 bytes

MX53-LOCO U-Boot > boot

** Too many args (max. 16) **

Usage:

MMC sub system

MMC Device 1887436800 not found

Wrong Image Format for bootm command

ERROR: can't get kernel image!

[KrishnaPavan]

Hi Deanhuang,

Supply necessary environment variables.

When it asks for "Hit any key to stop auto boot" do it and set the environment variables as required and provided in the User's guide.

link_in_above_post

Is irrelevant as that is a problem with the Serial Cable.

Regards :: Krishna Pavan

[DeanHuang]

thank you,

Attachment is the message I got when power on.

This problem seem had been discuss in  http://imxcommunity.org/group/ltib/forum/topics/ltib-problem-with-the-kernel-image .

I'll check it :)

[KrishnaPavan]

@ DeanHuang

but there is no any output on my screen

Have you configured your minicom properly?

Regards :: Krishna Pavan

[snirnisim]

I experienced the same issue. After checking the above suggestion you might want try the script that Steve G posted in my last disscusion. Just make sure you are following all modifications needed.

[MarioMedinaArza]

Hi Dean,

Im running in similar issues. But maybe the little experience i've gathered could help. The first thing i should do is to see if there is any output on serial port when booting up the card.

If u-boot.bin is working fine, you should see at least the initial prompt that is seen in console. After that, you should configure u-boot.bin to run the kernel (uImage). If there's any issue with the kernel, you shall be notified by the console.

Then the kernel loads the file system.

You can discard which of them in not working by taking a look to the console.

Regards,

[DeanHuang]

This is uboot and uImage