topic Re: Strange error in i.MX Processors

Strange error

enaud — Fri, 16 Mar 2012 14:36:16 GMT

hi,

i have installed VMware with image from Freescale site.

I builded Kernel and after I compressed rootfs directory and put it on USB.. On my pc with linux extract rootfs directory and flash sd:

But i have this error:

Freeing init memory: 172K
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
See Linux Documentation/init.txt for guidance.
[<80038538>] (unwind_backtrace+0x0/0xf0) from [<8041cb34>] (panic+0x6c/0xe0)
[<8041cb34>] (panic+0x6c/0xe0) from [<80033598>] (init_post+0xac/0xd4)
[<80033598>] (init_post+0xac/0xd4) from [<800084a4>] (kernel_init+0x124/0x168)
[<800084a4>] (kernel_init+0x124/0x168) from [<800349e0>] (kernel_thread_exit+0x0
/0x8)

Re: Strange error

snirnisim — Fri, 16 Mar 2012 14:47:17 GMT

make sure you set the enviroment variables correctly. that was the problem when i got that error recently...

you can see example vars in the disscusion of creating new uSD i posted.

if that doesn't help try run ./ltib on your host again and make sure your kernel is being built correctly.

try also rebuild it:

./ltib -m prep -p kernel

./ltib -m scbuild -p kernel

./ltib -m scdeploy -p kernel

hope you will succeed,

snir

Re: Strange error

DonaldR_PooleJr — Fri, 16 Mar 2012 15:05:39 GMT

Does your rootfs have an /bin/init, /sbin/init, /etc/init or /bin/sh? Does your rootfs also have an /etc/inittab file? Also, what does your boot command look like?

Re: Strange error

enaud — Fri, 16 Mar 2012 15:12:10 GMT

i have put hello world application from ltib package list

Re: Strange error

RandyKrakora — Fri, 16 Mar 2012 15:18:28 GMT

Can you give the commands you are using to burn the card and send your uboot environment? I believe I see this error every time my boot config isn't using the proper partition on the SD card to load the rfs from.

Re: Strange error

enaud — Fri, 16 Mar 2012 15:43:12 GMT

sudo dd if=u-boot.bin of=/dev/sdb bs=512 && sync && sync
sudo dd if=uImage of=/dev/sdb bs=512 seek=2048 && sync && sync
sudo fdisk /dev/sdb

8192

enter

w
sudo mkfs.ext3 /dev/sdb1
mkdir /home/giuseppe/mountpoint
sudo mount /dev/sdb1 /home/giuseppe/mountpoint
sudo cp -rpa [A-z]* /home/giuseppe/mountpoint
sudo umount /home/giuseppe/mountpoint

Re: Strange error

DonaldR_PooleJr — Fri, 16 Mar 2012 15:46:10 GMT

Your procedure looks fine. I would alway perform another sync before unmounting though. What does your u-boot environment look like?

Re: Strange error

RandyKrakora — Fri, 16 Mar 2012 15:48:43 GMT

What about your uboot params? ( print )

Not syncing after writing the rfs has bitten me a few times when I am in a hurry, and can be especially annoying if your writing Ubuntu rfs. :)

Re: Strange error

enaud — Fri, 16 Mar 2012 16:00:55 GMT

for environment variable i set this in u-boot>

setenv lvds 'video=mxcdi0fb:RGB666,XGA ldb'
setenv lcd 'video=mxcdi0fb:RGB24,SEIKO-WVGA'
setenv vga 'video=mxcdi1fb:GBR24,VGA-XGA di1_primary tve'
setenv hdmi 'video=mxcdi0fb:RGB24,1024x768M@60'

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

setenv bootargs_base 'setenv bootargs console=ttymxc0,115200 ${vga}'
setenv bootargs_nfs 'setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp'

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

setenv bootargs_mmc 'set bootargs ${bootargs} root=/dev/mmcblk0p1 rw rootwait'

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

setenv bootcmd 'run bootcmd_mmc'

saveenv

Re: Strange error

DonaldR_PooleJr — Fri, 16 Mar 2012 16:05:50 GMT

Hmm, your bootcmd_mmc looks a little different than mine. I don't think that you need the mmc dev 0 and the mmc read should be:

mmc read 0 ${loadaddr} 0x800 0x1800

You could try that to see where that gets you.

Re: Strange error

enaud — Fri, 16 Mar 2012 16:06:12 GMT

I have recompiled kernel on my pc with ubuntu and it start correctly.

How i can lunch helloworld? where is?

thanks

enaud said:

for environment variable i set this in u-boot>
setenv lvds 'video=mxcdi0fb:RGB666,XGA ldb'
setenv lcd 'video=mxcdi0fb:RGB24,SEIKO-WVGA'
setenv vga 'video=mxcdi1fb:GBR24,VGA-XGA di1_primary tve'
setenv hdmi 'video=mxcdi0fb:RGB24,1024x768M@60'
setenv bootcmd_obds 'ext2load mmc 0:1 0x70800000 /unit_tests/obds.bin; go 70800000'
setenv bootargs_base 'setenv bootargs console=ttymxc0,115200 ${vga}'
setenv bootargs_nfs 'setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp'
setenv bootcmd_net 'run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm'
setenv bootargs_mmc 'set bootargs ${bootargs} root=/dev/mmcblk0p1 rw rootwait'
setenv bootcmd_mmc 'run bootargs_base bootargs_mmc; mmc dev 0; mmc read ${loadaddr} 0x800 0x1800; bootm'
setenv bootcmd 'run bootcmd_mmc'
saveenv

Re: Strange error

DonaldR_PooleJr — Fri, 16 Mar 2012 16:09:34 GMT

Not sure, but you could try executing this command on the target to see where it is:

locate helloworld

Assuming helloworld is the executable name and that you have the locate utility installed.