Dear All,
I just started to work on iMX53 QSB board.
I am using the virtual machine setup for Ubuntu in my windows PC, as mentioned in the README_Ubuntu_VM.pdf.
I have 2 queries on this.
1. With that setup, I prepared the micro SD card and tried to boot the board.
The u-boot loaded properly and linux started to load, but while loading the file system it got stuck.
i.e. I am not getting the User Name and Password prompt. The VGA display shows the TUX symbol.
how to proceed on this?
(note: while updating the micro SD card with "dd" command, it took very long time)
2. I have gone through the LTIB script file and came to know the path of U-boot source. Linux source, rootfs. (rootfs - /home/lucid/ltib/rootfs)
As per my previous query, I got doubt in rootfs present in uSDcard (as the copy took very long time), now I formatted the uSD and copied the rootfs contents to it.
with this rootfs contents, in console output I can see the UserName and Password prompt.
But,
a. The password: lucid (as mentioned in the doc) is not matching. (what is the password?)
b. In the VGA display, only Tux symbol is there but no user name/pw prompt window.
how to overcome these issues?
any pointers and suggestions would be more helpful
thanks and regards,
jk
Jk:
Sorry for the late response. Here is how I set my environmental variables during the boot process for the i.mx53. Maybe you can use it for reference:
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
bootfile=dexter/uImage
filesize=2D47BC
fileaddr=70800000
bootcmd_mmc=run bootargs_base bootargs_mmc; mmc read 0 ${loadaddr} 0x800 0x1800; bootm
lvds=video=mxcdi0fb:RGB666,XGA ldb
bootcmd_obds=ext2load mmc 0:1 0x70800000 /unit_tests/obds.bin; go 70800000
lcd=video=mxcdi0fb:RGB24,SEIKO-WVGA
vga=video=mxcdi1fb:GBR24,XGA di1_primary tve
hdmi=video=mxcdi0fb:RGB24,1024x768M@60
bootcmd=run bootcmd_mmc
bootargs_mmc=set bootargs ${bootargs} root=/dev/mmcblk0p1 rw rootwait
wlcd=video=mxcdi0fb:RGB565,CLAA-WVGA
bootargs_base=setenv bootargs console=ttymxc0,115200 ${wlcd}
stdin=serial
stdout=serial
stderr=serial
As for kernel panic any interruption during the booting process could apparently cause it to happen. Here is an existing thread on how to resolve kernel panic:
One of the problems I had with kernel panic was because I didn't make my rootfile system correctly (I had an outdated rootfile system on the SD card). Can you check to see if that is causing the problem?
Dear Yinzhe,
while booting the kernel, I have got a kernel panic. can you provide some suggestion on that?
regulator_init_complete: incomplete constraints, leaving DA9052_LDO8 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO6 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO4 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO3 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO2 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO1 on
mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 00:06:06 UTC (366)
VFS: Mounted root (vfat filesystem) on device 179:1.
Freeing init memory: 168K
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[<8003711c>] (unwind_backtrace+0x0/0xe0) from [<803da040>] (panic+0x68/0xdc)
[<803da040>] (panic+0x68/0xdc) from [<803d9dbc>] (init_post+0xac/0xd4)
[<803d9dbc>] (init_post+0xac/0xd4) from [<80008a40>] (kernel_init+0x124/0x160)
[<80008a40>] (kernel_init+0x124/0x160) from [<800338b4>] (kernel_thread_exit+0x0/0x8)
I thought of issue with boot args and so, set the boot args again as
setenv bootargs_base 'setenv bootargs console=ttymxc0,115200 ${vga}'
setenv bootargs_mmc 'set bootargs ${bootargs} root=/dev/mmcblk0p1 rw rootwait'
setenv bootcmd_mmc 'run bootargs_base bootargs_mmc; mmc read 0 ${loadaddr} 0x800 0x1800; bootm'
setenv bootcmd 'run bootcmd_mmc'
let me know if there any inputs
-jk
Yes Yinzhe. only the Tux symbol there. Not the GUI display.
So you are not getting the UBUNTU graphic user interface to show up?
jk said:
Dear Yinzhe,
thanks. I can login as root.
But I did not get any display update on TV. only the TUX is displayed at left top corner.
any suggestions pls?
-jk
Dear Yinzhe,
thanks. I can login as root.
But I did not get any display update on TV. only the TUX is displayed at left top corner.
any suggestions pls?
-jk
I think what you need to do is to login as "root" for the login name. You don't need a password to get in.
jk said:
Dear Yinzhe Lu,
the it shows Login incorrect message.
How to resolve this?
regards,
jk
Dear Yinzhe Lu,
the it shows Login incorrect message.
How to resolve this?
regards,
jk
JK:
Does your login look like this?
Freescale Semiconductor, Inc.
freescale login: lucid
Password:
Login incorrect
freescale login:
The correct login screen should look like this, I believe:
* Enabling additional executable binary formats binfmt-support mount: mount point /
proc/sys/fs/binfmt_misc does not exist
mount.nfs: access denied by server while mounting 10.192.225.224:/nfsroot
Ubuntu 10.04 LTS lucid-desktop ttymxc0
lucid-desktop login: lucid
Password:
Last login: Fri Jun 1 06:09:48 CST 2012 on ttymxc0
Jk:
Did you get a Kernel panic error when the system got stuck?
It looks like this:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1)
[<80038524>] (unwind_backtrace+0x0/0xf0) from [<8040243c>] (panic+0x6c/0xe0)
[<8040243c>] (panic+0x6c/0xe0) from [<80008ddc>] (mount_block_root+0x1cc/0x20c)
[<80008ddc>] (mount_block_root+0x1cc/0x20c) from [<80009028>] (prepare_namespace+0x11c/0x174)
[<80009028>] (prepare_namespace+0x11c/0x174) from [<800084a0>] (kernel_init+0x120/0x168)
[<800084a0>] (kernel_init+0x120/0x168) from [<800349e0>] (kernel_thread_exit+0x0/0x8)