ConnectCore dont boot from tftp

Embedded Devices Linux
1

Hi, we have working on a ConnectCore Wi-iMX53 on a JumpStart Kit Development Board

I make a Kernel/Rootfs/UBoot project. I build all of them so I have this images:

  • uImage-ccwmx53js (I put it in the folder host:/tftpboot)
  • u-boot-ccwmx53js.bin
  • rootfs-ccwmx53js-128.jffs2 (I put it in the folder host:/exports)
  • rootfs-ccwmx53js-512.jffs2 (I put it in the folder host:/exports)

Net Info:

  • host: 192.168.1.102
  • taget: 192.168.1.112
  • netmask: 255.255.255.0

I configure UBoot network

U-Boot 2009.08 - DUB-1.4.0.3 - (Jul 12 2012 - 13:40:22) - GCC 4.4.6
for ConnectCore Wi-i.MX53 on a JumpStart Kit Development Board

CCWMX53 # printenv
bootdelay=4
baudrate=115200
loadaddr=0x70800000
silent=no
ethprime=FEC0
ethact=FEC0
wdmode=1
bootcmd=dboot linux flash
video=displayfb:LCD@LQ070Y3DG3B
ipaddr=192.168.1.112
ipaddr_wlan=192.168.43.30
ipaddr1=192.168.1.112
netmask=255.255.255.0
netmask_wlan=255.255.255.0
netmask1=255.255.255.0
serverip=192.168.1.102
gatewayip=192.168.1.1
dnsip=0.0.0.0
dnsip2=0.0.0.0
dhcp=off
dhcp_wlan=off
dhcp1=off
mtdids=nand0=onboard_boot
mtdparts=mtdparts=onboard_boot:0x100000(U-Boot),0x80000@0x100000(NVRAM),0x300000@0x180000(Kernel),0x7800000@0x480000
(RootFS),0x18380000@0x7c80000(UserFS)
hostname=CCWMX53-701CF1

then i execute:
CCWMX53 # dboot linux tftp

The linux start but i have this error
Looking up port of RPC 100005/1 on 192.168.1.102
Root-NFS: Server returned error -2 while mounting /exports/nfsroot-ccwmx53js
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device “nfs” or unknown-block(2,0)
Please append a correct “root=” boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 512 mtdblock1 (driver?)
1f02 3072 mtdblock2 (driver?)
1f03 122880 mtdblock3 (driver?)
1f04 396800 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<8000c5a8>] (dump_backtrace+0x0/0x10c) from [<80345c78>] (dump_stack+0x18/0x1c)
r7:803e85b8 r6:00008000 r5:cfa58000 r4:804c3a10
[<80345c60>] (dump_stack+0x0/0x1c) from [<80345cdc>] (panic+0x60/0xd4)
[<80345c7c>] (panic+0x0/0xd4) from [<80455d5c>] (mount_block_root+0x1dc/0x21c)
r3:00000000 r2:00000000 r1:cf029f58 r0:803e865f
[<80455b80>] (mount_block_root+0x0/0x21c) from [<80455e60>] (mount_root+0xc4/0xf8)
[<80455d9c>] (mount_root+0x0/0xf8) from [<80456000>] (prepare_namespace+0x16c/0x1d0)
r5:804719f4 r4:804c0478
[<80455e94>] (prepare_namespace+0x0/0x1d0) from [<8045528c>] (kernel_init+0x118/0x158)
r5:80481ab4 r4:804c0240
[<80455174>] (kernel_init+0x0/0x158) from [<80030cd8>] (do_exit+0x0/0x5c4)
r5:80455174 r4:00000000

then I try renaming both rootfs files to rootfs-ccwmx53js.jffs2 in the folder host:/exports, but it didnt work

2

CCWMX53 # printenv_dynamic
console=console=ttymxc0,115200
androidloadaddr=0x70800000
aimg=uImage-android-ccwmx53js
ebootaddr=0x70800000
eimg=eboot-CCXMX53
sata_rpart=/dev/sda2
hostname=CCWMX53-701CF1
ip=ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off
loadaddr=0x70800000
loadaddr_initrd=CONFIG_INITRD_LOAD_ADDR
kimg=uImage-ccwmx53js
npath=/exports/nfsroot-ccwmx53js
linuxloadaddr=0x70800000
loadzipaddr=CONFIG_ZIP_LOAD_ADDR
loadbootsc=yes
bootscript=ccwmx53js-bootscript
mmc_rpart=/dev/mmcblk0p2
netosloadaddr=CONFIG_NETOS_LOAD_ADDR
rimg=rootfs-ccwmx53js-128.jffs2
arimg=android-ccwmx53js-128.jffs2
rootdelay=10
smtd=
snfs=root=nfs nfsroot=${serverip}:
std_bootarg=
uimg=u-boot-ccwmx53js.bin
usrimg=userfs-ccwmx53js-128.jffs2
video=displayfb:LCD@LQ070Y3DG3B
video2=displayfb:disabled
wceloadaddr=0x74000000
wimg=wce-CCXMX53
wzimg=wcez-CCXMX53

I create the folder host:/exports/nfsroot-ccwmx53js and I put there the file rootfs-ccwmx53js-128.jffs2

and refresh the nfs system doing:
sudo service nfs-kernel-server stop
sudo service nfs-kernel-server start

it was mounted but now, i have another error

Looking up port of RPC 100005/1 on 192.168.1.102
VFS: Mounted root (nfs filesystem) on device 0:13.
devtmpfs: error mounting -2
Freeing init memory: 184K
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for
guidance.
Backtrace:
[<8000c5a8>] (dump_backtrace+0x0/0x10c) from [<80345c78>] (dump_stack+0x18/0x1c)
r7:00000013 r6:80030cd8 r5:80481ab4 r4:804c3a10
[<80345c60>] (dump_stack+0x0/0x1c) from [<80345cdc>] (panic+0x60/0xd4)
[<80345c7c>] (panic+0x0/0xd4) from [<8000880c>] (init_post+0xa8/0xcc)
r3:00000000 r2:cfa54200 r1:cfa54300 r0:803e8316
[<80008764>] (init_post+0x0/0xcc) from [<80455290>] (kernel_init+0x11c/0x158)
r5:80481ab4 r4:804c0240
[<80455174>] (kernel_init+0x0/0x158) from [<80030cd8>] (do_exit+0x0/0x5c4)
r5:80455174 r4:00000000

3

Lets check step by step

1.Are you using Digi shipped Kubuntu ? If so NFS server and TFTP server will be configured by default
2. After building project , did you install it?
Right click on project and install.
When you install flash images will be copied to /tftpboot folder and filesystem will be copied to /exports/nfsroot-ccwmx53js folder.

  1. After this check whether you have /exports/nfsroot-ccwmx53js exists? If not create it manually.

  2. Make sure that you are building a project for wireless variant of module and flashing on wireless variant.

  3. Your uboot seems to be old. Build a uboot project and flash onto module.

  4. in env variables i see that you have set same ipaddress of ipaddr and ipaddr1 which could be an issue if you connect both FEC and secondary ethernet interface to same network.

–>>Kernel panic - not syncing: VFS: Unable to mount root
This error is mostly due to the error when kernel is not able to find filesystem in NFS folder

1 Like
4

I didn’t the step 2, i did it and the system works. Thanks