AnsweredAssumed Answered

Can not boot up by MfgTool

Question asked by Carmili Li on Jan 19, 2014
Latest reply on Jan 19, 2014 by Yuri Muhin

Hello

My board is imx6q-sdb.

I have a question about how to make an uImage for MfgTool.
Before MfgTool burn image to flash, CPU will boot up first.

The MfgTool use two uImages,one for bootint up, another using to burn flash.

Now,I use the uImage which be compiled by myself.

When the MfgTool make the CPU boot up,it can not mount file system.

When I use the origin uImage include by MfgTool,CPU will start UTP when it finish initializing kernel.

Q:

What is UTP?

What do I need to modify my linux kernel?

 

UART print the blow information.

Using origin uImage:

......

VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

Bus freq driver module loaded

Bus freq driver Enabled

mxc_dvfs_core_probe

DVFS driver module loaded

regulator_init_complete: PFUZE100_VGEN6: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN3: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN2: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN1: incomplete constraints, leaving on

regulator_init_complete: SPKVDD: incomplete constraints, leaving on

snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)

Freeing init memory: 200K

Starting UTP

ln: /etc/mtab: File exists

disable turn off display

Starting the hotplug events dispatcher udevd

udevd (2001): /proc/2001/oom_adj is deprecated, please use /proc/2001/oom_score_

adj instead.

 

Using my uImage:

......

DVFS driver module loaded

regulator_init_complete: PFUZE100_VGEN6: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN3: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN2: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN1: incomplete constraints, leaving on

snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)

List of all partitions:

1f00            1024 mtdblock0  (driver?)

1f01           31744 mtdblock1  (driver?)

b300         7757824 mmcblk0  driver: mmcblk

  b301         7747584 mmcblk0p1 00000000-0000-0000-0000-000000000000

b310            2048 mmcblk0boot1  (driver?)

b308            2048 mmcblk0boot0  (driver?)

No filesystem could mount root, tried:  jffs2

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

[<80044854>] (unwind_backtrace+0x0/0xf8) from [<805067d4>] (panic+0x74/0x18c)

Outcomes