Error when loading the fsl-image-virt image on the t1040 RDB

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error when loading the fsl-image-virt image on the t1040 RDB

Jump to solution
1,557 Views
jrodrigo
Contributor II

It is required kvm-qemu to be available on a linux OS running on the T1040 RDB. So a fsl-image-virt image was created following SDK Technical Documentation. We deploy the image using the following commands:

=>tftp 1000000 < uImage_name>

=>tftp 2000000 fsl-image-core-<platform>.ext2.gz.u-boot

=>tftp c00000 <platform_dtb_name>

=>bootm 1000000 2000000 c00000

And we get the following errors:

RAMDISK: gzip image found at block 0

VFS: Mounted root (ext2 filesystem) on device 1:0.

devtmpfs: mounted

Freeing unused kernel memory: 284K (c0871000 - c08b8000)

EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #3889: : rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #3734: : rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.7+g6619b8b #1

Call Trace:

[e7083e80] [c0006f50] show_stack+0x40/0x150 (unreliable)

[e7083ec0] [c06a186c] dump_stack+0x78/0xa0

[e7083ed0] [c069fbac] panic+0xd8/0x1fc

[e7083f20] [c000295c] kernel_init+0x16c/0x170

[e7083f40] [c000fe0c] ret_from_kernel_thread+0x5c/0x64

Rebooting in 180 seconds..

How can we solve this?

Thanks in advance.

Tags (1)
1 Solution
944 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Juan Rodrigo,

Please download the filesystem at 4000000.

Please refer to the following definition in include/configs/T104xRDB.h, the command line is allocated backward from 64M, if the ramdiskaddr starts at 32M, fsl-image-virt  rootfs image is larger than 32M(about 44M), the command line data will be written in the middle of it, which causes the rootfs filesystem corrupted, so you will get filesystem setting up error.

/*

* For booting Linux, the board info and command line data

* have to be in the first 64 MB of memory, since this is

* the maximum mapped by the Linux kernel during initialization.

*/

#define CONFIG_SYS_BOOTMAPSZ    (64 << 20)      /* Initial map for Linux*/

#define CONFIG_SYS_BOOTM_LEN    (64 << 20)      /* Increase max gunzip size *


Have a great day,
Yiping

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

View solution in original post

2 Replies
945 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Juan Rodrigo,

Please download the filesystem at 4000000.

Please refer to the following definition in include/configs/T104xRDB.h, the command line is allocated backward from 64M, if the ramdiskaddr starts at 32M, fsl-image-virt  rootfs image is larger than 32M(about 44M), the command line data will be written in the middle of it, which causes the rootfs filesystem corrupted, so you will get filesystem setting up error.

/*

* For booting Linux, the board info and command line data

* have to be in the first 64 MB of memory, since this is

* the maximum mapped by the Linux kernel during initialization.

*/

#define CONFIG_SYS_BOOTMAPSZ    (64 << 20)      /* Initial map for Linux*/

#define CONFIG_SYS_BOOTM_LEN    (64 << 20)      /* Increase max gunzip size *


Have a great day,
Yiping

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

944 Views
jrodrigo
Contributor II

Hi Yiping.

Thank you for your answer. I followed your suggestions and everything went OK.

Juan.

0 Kudos