Using MFG Tools with I.MX6U

powerprince — Wed, 25 Feb 2015 01:32:46 GMT

Using the MFG Tool to try to EMMC writing.

But this is a kernel panic occurs as follows.

Main chip : I.MX6U

os : Linux

Making the RAMDISK image and to use the MFG Tool, the boot arguments following the u-boot has been passed to the kernel.

mfg ucl2.xml file

<LIST name="GNSD-3D-SVM-eMMC" desc="Choose eMMC Linux as media">
<CMD state="BootStrap" type="boot" body="BootStrap" file ="u-boot.imx" >Loading U-boot...</CMD>
<CMD state="BootStrap" type="load" file="uImage" address="0x10800000" loadSection="OTH" setSection="OTH" HasFlashHeader="FALSE" >Loading Kernel...</CMD>
<CMD state="BootStrap" type="load" file="initrd-2.image" address="0x20000000" loadSection="OTH" setSection="OTH" HasFlashHeader="FALSE" >Loading Initrd....</CMD>

2. U-boot boot arguments

As defined in the above file MFG ucl2.xml file as a uimageaddr =0x10800000, ramdiskaddr = 0x20000000.
ramdisksize is 36864.
mfg_args=setenv bootargs console=${console},${baudrate} mem=940M root=/dev/ram0 rw rootfstype=ext2 initrd=${ramdiskaddr},36M ramdisk=${ramdisksize} video=${videoopts} ip=dhcp eth=${usbethaddr}
boot_mfg=echo Booting from mfg ...;run mfg_args; bootm ${uimageaddr} ${ramdiskaddr}

3.Kernel command line

kernel command line: console=ttymxc0,115200 mem=940M root=/dev/ram0 rw rootfstype=ext2 initrd=20000000,36M ramdisk=36864 video=mxcfb0:dev=lcd,GNSD-WVGA@30,if=BGR24,bpp=16 consoleblank=0 ip=dhcp eth=

Kernel panic occurs when the ramdisk mount, as shown below.

----------------------------------------------------------------------

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

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

mmc0: new high speed DDR MMC card at address 0001

mmcblk0: mmc0:0001 SEM08G 7.28 GiB

mmcblk0boot0: mmc0:0001 SEM08G partition 1 2.00 MiB

mmcblk0boot1: mmc0:0001 SEM08G partition 2 2.00 MiB

mmcblk0: unknown partition table

mmcblk0boot1: unknown partition table

mmcblk0boot0: unknown partition table

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

[<80045834>] (unwind_backtrace+0x0/0xf8) from [<804bd4d4>] (panic+0x74/0x18c)

[<804bd4d4>] (panic+0x74/0x18c) from [<80008d3c>] (mount_block_root+0x170/0x224)

[<80008d3c>] (mount_block_root+0x170/0x224) from [<80008fc4>] (mount_root+0xe8/0x108)

[<80008fc4>] (mount_root+0xe8/0x108) from [<80009148>] (prepare_namespace+0x164/0x1bc)

[<80009148>] (prepare_namespace+0x164/0x1bc) from [<80008a04>] (kernel_init+0x108/0x13c)

[<80008a04>] (kernel_init+0x108/0x13c) from [<8003faa4>] (kernel_thread_exit+0x0/0x8)

CPU1: stopping

[<80045834>] (unwind_backtrace+0x0/0xf8) from [<80039324>] (do_IPI+0x150/0x17c)

[<80039324>] (do_IPI+0x150/0x17c) from [<8003ea0c>] (__irq_svc+0x4c/0xe8)

Exception stack(0xb8061cf8 to 0xb8061d40)

1ce0: ffffffff b800c7f0

1d00: 8bf9025c ffffffff 80a37b00 b800c7f0 8bf9025c b800c7f0 80a37b00 ffffffff

1d20: 00000000 b8061e34 00000000 b8061d40 80069c60 8022a440 20000113 ffffffff

[<8003ea0c>] (__irq_svc+0x4c/0xe8) from [<8022a440>] (cpumask_next_and+0x14/0x68)

[<8022a440>] (cpumask_next_and+0x14/0x68) from [<80069c60>] (find_busiest_group+0x1ac/0xa30)

[<80069c60>] (find_busiest_group+0x1ac/0xa30) from [<8006a5a4>] (load_balance+0xc0/0x67c)

[<8006a5a4>] (load_balance+0xc0/0x67c) from [<8006ac00>] (rebalance_domains+0xa0/0x18c)

[<8006ac00>] (rebalance_domains+0xa0/0x18c) from [<8006ad30>] (run_rebalance_domains+0x44/0x11c)

[<8006ad30>] (run_rebalance_domains+0x44/0x11c) from [<80075294>] (__do_softirq+0xac/0x140)

[<80075294>] (__do_softirq+0xac/0x140) from [<800757d0>] (irq_exit+0x94/0x9c)

[<800757d0>] (irq_exit+0x94/0x9c) from [<800392e0>] (do_IPI+0x10c/0x17c)

[<800392e0>] (do_IPI+0x10c/0x17c) from [<8003ea0c>] (__irq_svc+0x4c/0xe8)

Exception stack(0xb8061f90 to 0xb8061fd8)

1f80: 80a7b7c0 80000093 00000001 00000000

1fa0: b8060000 80a743e4 804c56b0 80a3b584 1000406a 412fc09a 00000000 00000000

1fc0: 00000000 b8061fd8 8004d708 8003fb04 40000013 ffffffff

[<8003ea0c>] (__irq_svc+0x4c/0xe8) from [<8003fb04>] (default_idle+0x24/0x28)

[<8003fb04>] (default_idle+0x24/0x28) from [<8003fd08>] (cpu_idle+0xc8/0x108)

[<8003fd08>] (cpu_idle+0xc8/0x108) from [<104ba314>] (0x104ba314)

ucl2.xml : mfg tool Settings file

Log.txt : console log file

Original Attachment has been moved to: log.txt.zip

Original Attachment has been moved to: ucl2.xml.zip

Re: Using MFG Tools with I.MX6U

igorpadykov — Sat, 28 Feb 2015 01:07:32 GMT

Hi ryan

had you run DDR tests and rebuild MFG Tools firmware

with new DDR settings found in DDR tests

https://community.freescale.com/docs/DOC-96412

Best regards

igor

i.MX ProcessorsのトピックRe: Using MFG Tools with I.MX6U

Using MFG Tools with I.MX6U

Re: Using MFG Tools with I.MX6U