topic Re: Re: Booting mainline kernel with mainline u-boot from SD on RIoTboard in i.MX Processors

Booting mainline kernel with mainline u-boot from SD on RIoTboard

michaeloberle — Wed, 08 Apr 2015 11:43:05 GMT

I am trying to boot an SD card image with a mainline u-boot (10.2014), mainline kernel (3.19) and debian rootfs all of which I have cross-compiled in a debian VM.

Since I am not a linux guru I am trying to give you as much information as I can for the process of creating the image, u-boot and the kernel.

This is the output I am receiving from u-boot now:

CPU: Freescale i.MX6SOLO rev1.1 at 792 MHz

Reset cause: POR

Board: RIoTboard

I2C: ready

DRAM: 1 GiB

MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2

*** Warning - bad CRC, using default environment

No panel detected: default to HDMI

Display: HDMI (1024x768)

In: serial

Out: serial

Err: serial

Net: FEC [PRIME]

Error: FEC address not set.

Hit any key to stop autoboot: 0

switch to partitions #0, OK

mmc2(part 0) is current device

** Unrecognized filesystem type **

Booting from net ...

FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !

*** ERROR: `ethaddr' not set

FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !

*** ERROR: `ethaddr' not set

FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !

Bad Linux ARM zImage magic!

=> Bad Linux ARM zImage magic!

Unknown command 'Bad' - try 'help'

And this is the output of printenv:

baudrate=115200
boot_fdt=try
bootargs=console=ttymxc1,115200 root=/dev/nfs ip=dhcp nfsroot=:,v3,tcp
bootcmd=mmc dev ${mmcdev};if mmc rescan; then if run loadbootscript; then run bootscript; else if run loadimage; then run mmcboot; else run netboot; fi; fi; else run netboot; fi
bootdelay=1
bootscript=echo Running bootscript from mmc ...; source
console=ttymxc1
ethact=FEC
ethprime=FEC
fdt_addr=0x18000000
fdt_file=imx6dl-riotboard.dtb
fdt_high=0xffffffff
get_cmd=dhcp
image=zImage
initrd_high=0xffffffff
ip_dyn=yes
loadaddr=0x12000000
loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}
mmcargs=setenv bootargs console=${console},${baudrate} root=${mmcroot}
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
mmcdev=2
mmcpart=1
mmcroot=/dev/mmcblk1p2 rootwait rw
netargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${image}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
script=boot.scr
update_sd_firmware=if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; if mmc dev ${mmcdev}; then if ${get_cmd} ${update_sd_firmware_filename}; then setexpr fw_sz ${filesize} / 0x200; setexpr fw_sz ${fw_sz} + 1; mmc write ${loadaddr} 0x2 ${fw_sz}; fi; fi
update_spi_firmware=if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; if ${get_cmd} ${update_spi_firmware_filename}; then if sf probe; then sf erase 0 0xc0000; sf write ${loadaddr} 0x400 ${filesize}; fi; fi

Environment size: 2228/8188 bytes

I guess that u-boot does not look for the kernel on the SD card but since I am new to u-boot I don't know what I need to change.

This is how I build the component which is a mixutre of (http://www.element14.com/community/community/designcenter/single-board-computers/riotboard/blog/2014/09/18/linux-on-the-…) and risc-a-day: Mainline Linux for RIoTBoard

U-boot

export ARCH=arm

export CROSS_COMPILE=arm-linux-gnueabihf-

export OUTPUT=/home/riotboard/linux/output

wget ftp://ftp.denx.de/pub/u-boot/u-boot-2014.10.tar.bz2

tar xf u-boot-2014.10.tar.bz2 && cd u-boot-2014.10

make distclean && make riotboard_defconfig && make u-boot.imx -j4

Kernel:

export ARCH=arm

export OUTPUT=/home/riotboard/linux/output

mkdir ~/riotboard

wget https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.17.tar.xz

tar xf linux-3.17.tar.xz && cd linux-3.17

make distclean && make imx_v6_v7_defconfig && make LOADADDR=0x10008000 uImage -j4

cp arch/arm/boot/uImage ~/riotboard/

cp arch/arm/boot/dts/imx6dl-riotboard.dtb ~/riotboard/

make modules_install INSTALL_MOD_PATH=~/riotboard

Side question: what does the LOADADDR argument to in the make command?

I will skip the rootfs here becuase these IMHO is not the problem here yet.

I have created the SD card image in the following way (http://www.element14.com/community/community/designcenter/single-board-computers/riotboard/blog/2014/09/19/linux-on-the-…)

apt-get install qemu-utils kpartx

cd /home/riotboard/linux/output

qemu-img create sdcard.img 3600M

sfdisk --force -uM sdcard.img << EOF

10,,83

EOF

kpartx -av sdcard.img

mkfs.ext2 -j /dev/mapper/loop0p1

mkdir -p /mnt/sdcard

mount -t ext2 /dev/mapper/loop0p1 /mnt/sdcard

tar --numeric-owner -C /mnt/sdcard -zxvf oneiric.tgz

tar --numeric-owner -C /mnt/sdcard -zxvf linux-kernel-3.19.tgz

umount /mnt/sdcard

kpartx -dv sdcard.img

dd if=u-boot.imx of=sdcard.img bs=512 seek=2 conv=notrunc

I hope someone can point me in the right direction!

Thank you!

Michael

Re: Booting mainline kernel with mainline u-boot from SD on RIoTboard

jimmychan — Thu, 09 Apr 2015 07:43:36 GMT

When the board is up, it will run the bootcmd first. So, in the bootcmd, there will loading the zImage to memory first. e.g. you can load the zImage from MMC or load from the network through tftp. Then create the final 'bootargs'. Then the 'bootargs' pass to the kernel. It will be the kernel command line.

In your case, the bootargs = console=ttymxc1,115200 root=/dev/nfs ip=dhcp nfsroot=:,v3,tcp

The board is booting from NFS. But the path of nfsroot is missing.

You can find more example and information from the i.MX Linux User Guide.

Re: Re: Booting mainline kernel with mainline u-boot from SD on RIoTboard

michaeloberle — Thu, 09 Apr 2015 11:17:02 GMT

Thank you for the answer. The guide is nice for giving more infos to the basics of i.MX6. But as far as I know the addresses for the riotbaord are different.

Nonetheless I have made some progress:

setenv bootargs $bootargs rootwait root=/dev/mmcblk0p1

mmc dev 0

ext2load mmc 0 10800000 /boot/uImage

bootm 10800000

It appears that the u-boot is loading the kernel now but the kernel cannot find the rootfs or the dtb file??

## Booting kernel from Legacy Image at 10800000 ...

Image Name: Linux-3.19.0

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 5583856 Bytes = 5.3 MiB

Load Address: 10008000

Entry Point: 10008000

Verifying Checksum ... OK

Loading Kernel Image ... OK

Starting kernel ...

Does anyone hvae suggestion?

Re: Booting mainline kernel with mainline u-boot from SD on RIoTboard

fabio_estevam — Thu, 09 Apr 2015 15:30:24 GMT

You are loading and booting only the kernel.

You also need to load the dtb into run and then boot like: bootm <kerneladdress> - <dtbaddress>

Regards,

Fabio Estevam

Re: Re: Booting mainline kernel with mainline u-boot from SD on RIoTboard

michaeloberle — Thu, 09 Apr 2015 17:14:06 GMT

Thank you Fabio! That was a very valuable hint!

I have loaded the dtb and now the kernle is booting!

setenv bootargs $bootargs rootwait root=/dev/mmcblk0p1

mmc dev 0

ext2load mmc 0 10800000 /boot/uImage

ext2load mmc 0 16800000 /boot/imx6dl-riotboard.dtb

bootm 10800000 - 16800000

Now it appears that the kernel cannot find the rootfs and tries to look for it on the network where of course there is not kernel - it is on the sd card.

Do I also need to load the rootfs?

=> bootm 10800000 - 16800000
## Booting kernel from Legacy Image at 10800000 ...
   Image Name:   Linux-3.19.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5583856 Bytes = 5.3 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 16800000
   Booting using the fdt blob at 0x16800000
   Loading Kernel Image ... OK
   Using Device Tree in place at 16800000, end 1680a6e1

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.19.0 (root@debian) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Mon Apr 6 14:36:46 EDT 2015
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: RIoTboard i.MX6S
[    0.000000] cma: Reserved 16 MiB at 0x4f000000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] PERCPU: Embedded 9 pages/cpu @be7b8000 s8064 r8192 d20608 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260096
[    0.000000] Kernel command line: console=ttymxc1,115200 root=/dev/nfs ip=dhcp nfsroot=:,v3,tcp rootwait root=/dev/mmcblk0p1 rootwait root=/dev/mmcblk0p1 rootwait root=/dev/mmcblk0p1
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1004364K/1048576K available (6963K kernel code, 415K rwdata, 2420K rodata, 372K init, 8344K bss, 27828K reserved, 16384K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc0800000 - 0xff000000   (1000 MB)
[    0.000000]     lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
[    0.000000]     pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
[    0.000000]     modules : 0x7f000000 - 0x7fe00000   (  14 MB)
[    0.000000]       .text : 0x80008000 - 0x8093201c   (9385 kB)
[    0.000000]       .init : 0x80933000 - 0x80990000   ( 372 kB)
[    0.000000]       .data : 0x80990000 - 0x809f7fc0   ( 416 kB)
[    0.000000]        .bss : 0x809f7fc0 - 0x8121e29c   (8345 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C-310 erratum 769419 enabled
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 16 ways, 512 kB
[    0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76050001
[    0.000000] Switching to timer-based delay loop, resolution 333ns
[    0.000007] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655765682ns
[    0.001077] Console: colour dummy device 80x30
[    0.001106] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[    0.001116] ... MAX_LOCKDEP_SUBCLASSES:  8
[    0.001125] ... MAX_LOCK_DEPTH:          48
[    0.001133] ... MAX_LOCKDEP_KEYS:        8191
[    0.001141] ... CLASSHASH_SIZE:          4096
[    0.001149] ... MAX_LOCKDEP_ENTRIES:     32768
[    0.001156] ... MAX_LOCKDEP_CHAINS:      65536
[    0.001164] ... CHAINHASH_SIZE:          32768
[    0.001172]  memory used by lock dependency info: 5167 kB
[    0.001180]  per task-struct memory footprint: 1152 bytes
[    0.001207] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000)
[    0.001226] pid_max: default: 32768 minimum: 301
[    0.001555] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001574] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.003482] CPU: Testing write buffer coherency: ok
[    0.004236] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.004330] Setting up static identity map for 0x106d2510 - 0x106d2580
[    0.008099] Brought up 1 CPUs
[    0.008117] SMP: Total of 1 processors activated (6.00 BogoMIPS).
[    0.008128] CPU: All CPU(s) started in SVC mode.
[    0.009850] devtmpfs: initialized
[    0.011641] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.013676] pinctrl core: initialized pinctrl subsystem
[    0.039089] NET: Registered protocol family 16
[    0.042263] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.044647] CPU identified as i.MX6DL, silicon rev 1.1
[    0.089785] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.089801] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.092710] imx6dl-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
[    0.122572] mxs-dma 110000.dma-apbh: initialized
[    0.127702] vgaarb: loaded
[    0.128703] SCSI subsystem initialized
[    0.129890] usbcore: registered new interface driver usbfs
[    0.130053] usbcore: registered new interface driver hub
[    0.130274] usbcore: registered new device driver usb
[    0.134923] i2c i2c-0: IMX I2C adapter registered
[    0.134950] of_dma_request_slave_channel: dma-names property of node '/soc/aips-bus@02100000/i2c@021a0000' missing or empty
[    0.134969] i2c i2c-0: can't use DMA
[    0.135759] i2c i2c-1: IMX I2C adapter registered
[    0.135783] of_dma_request_slave_channel: dma-names property of node '/soc/aips-bus@02100000/i2c@021a4000' missing or empty
[    0.135801] i2c i2c-1: can't use DMA
[    0.136553] i2c i2c-3: IMX I2C adapter registered
[    0.136575] of_dma_request_slave_channel: dma-names property of node '/soc/aips-bus@02100000/i2c@021f8000' missing or empty
[    0.136593] i2c i2c-3: can't use DMA
[    0.136745] Linux video capture interface: v2.00
[    0.137017] pps_core: LinuxPPS API ver. 1 registered
[    0.137029] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.137086] PTP clock support registered
[    0.137966] Advanced Linux Sound Architecture Driver Initialized.
[    0.143333] Switched to clocksource mxc_timer1
[    0.145343] cfg80211: Calling CRDA to update world regulatory domain
[    0.170850] NET: Registered protocol family 2
[    0.172516] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.172767] TCP bind hash table entries: 8192 (order: 6, 294912 bytes)
[    0.175806] TCP: Hash tables configured (established 8192 bind 8192)
[    0.176071] TCP: reno registered
[    0.176112] UDP hash table entries: 512 (order: 3, 40960 bytes)
[    0.176530] UDP-Lite hash table entries: 512 (order: 3, 40960 bytes)
[    0.177766] NET: Registered protocol family 1
[    0.178771] RPC: Registered named UNIX socket transport module.
[    0.178788] RPC: Registered udp transport module.
[    0.178799] RPC: Registered tcp transport module.
[    0.178809] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.180036] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.183489] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.201902] VFS: Disk quotas dquot_6.5.2
[    0.202375] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.209794] NFS: Registering the id_resolver key type
[    0.210002] Key type id_resolver registered
[    0.210017] Key type id_legacy registered
[    0.210206] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.212072] fuse init (API version 7.23)
[    0.215756] io scheduler noop registered
[    0.215783] io scheduler deadline registered
[    0.215910] io scheduler cfq registered (default)
[    0.216647] imx-weim 21b8000.weim: Driver registered.
[    0.224406] imx-sdma 20ec000.sdma: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2
[    0.224435] imx-sdma 20ec000.sdma: external firmware not found, using ROM firmware
[    0.232295] imx-sdma 20ec000.sdma: initialized
[    0.234893] pfuze100-regulator 0-0008: Full layer: 1, Metal layer: 1
[    0.235589] pfuze100-regulator 0-0008: FAB: 0, FIN: 0
[    0.235606] pfuze100-regulator 0-0008: pfuze100 found.
[    0.256830] 2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 21, base_baud = 5000000) is a IMX
[    0.258854] 21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 292, base_baud = 5000000) is a IMX
[    0.995392] console [ttymxc1] enabled
[    1.000544] 21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 293, base_baud = 5000000) is a IMX
[    1.010679] 21f0000.serial: ttymxc3 at MMIO 0x21f0000 (irq = 294, base_baud = 5000000) is a IMX
[    1.020755] 21f4000.serial: ttymxc4 at MMIO 0x21f4000 (irq = 295, base_baud = 5000000) is a IMX
[    1.031323] [drm] Initialized drm 1.1.0 20060810
[    1.044750] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.051393] [drm] No driver support for vblank timestamp query.
[    1.057876] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops ipu_crtc_ops)
[    1.065568] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops ipu_crtc_ops)
[    1.073920] imx-hdmi 120000.hdmi: Detected HDMI controller 0x13:0x1a:0xa0:0xc1
[    1.081466] imx-drm display-subsystem: bound 120000.hdmi (ops hdmi_ops)
[    1.088784] imx-drm display-subsystem: No connectors reported connected with modes
[    1.096428] [drm] Cannot find any crtc or sizes - going 1024x768
[    1.115183] Console: switching to colour frame buffer device 128x48
[    1.127168] imx-drm display-subsystem: fb0:  frame buffer device
[    1.133192] imx-drm display-subsystem: registered panic notifier
[    1.139282] [drm] Initialized imx-drm 1.0.0 20120507 on minor 0
[    1.145936] imx-ipuv3 2400000.ipu: IPUv3H probed
[    1.169947] brd: module loaded
[    1.184031] loop: module loaded
[    1.193223] CAN device driver interface
[    1.200092] 2188000.ethernet supply phy not found, using dummy regulator
[    1.224857] pps pps0: new PPS source ptp0
[    1.229306] fec 2188000.ethernet (unnamed net_device) (uninitialized): Invalid MAC address: 00:00:00:00:00:00
[    1.239310] fec 2188000.ethernet (unnamed net_device) (uninitialized): Using random MAC address: 2a:6d:20:e4:58:d9
[    1.257291] libphy: fec_enet_mii_bus: probed
[    1.263466] fec 2188000.ethernet eth0: registered PHC device 0
[    1.270616] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.277308] ehci-pci: EHCI PCI platform driver
[    1.281910] ehci-mxc: Freescale On-Chip EHCI Host driver
[    1.287708] usbcore: registered new interface driver usb-storage
[    1.304289] 2184200.usb supply vbus not found, using dummy regulator
[    1.315067] ci_hdrc ci_hdrc.1: EHCI Host Controller
[    1.320176] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
[    1.343383] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
[    1.352604] hub 1-0:1.0: USB hub found
[    1.356693] hub 1-0:1.0: 1 port detected
[    1.364335] mousedev: PS/2 mouse device common for all mice
[    1.374279] snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0
[    1.382819] i2c /dev entries driver
[    1.389415] IR NEC protocol handler initialized
[    1.394078] IR RC5(x/sz) protocol handler initialized
[    1.399159] IR RC6 protocol handler initialized
[    1.403744] IR JVC protocol handler initialized
[    1.408299] IR Sony protocol handler initialized
[    1.412937] IR SANYO protocol handler initialized
[    1.417684] IR Sharp protocol handler initialized
[    1.422410] IR MCE Keyboard/mouse protocol handler initialized
[    1.428285] IR XMP protocol handler initialized
[    1.434901] coda 2040000.vpu: unable to alloc iram
[    1.440403] coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6dl.bin failed with error -2
[    1.449452] coda 2040000.vpu: firmware request failed
[    1.457391] platform 2000000.aips-bus:tempmon: Driver imx_thermal requests probe deferral
[    1.468525] imx2-wdt 20bc000.wdog: timeout 60 sec (nowayout=0)
[    1.475182] Driver 'mmcblk' needs updating - please use bus_type methods
[    1.482017] sdhci: Secure Digital Host Controller Interface driver
[    1.488283] sdhci: Copyright(c) Pierre Ossman
[    1.492716] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.499825] sdhci-esdhc-imx 2194000.usdhc: could not get ultra high speed state, work on normal mode
[    1.509554] sdhci-esdhc-imx 2194000.usdhc: No vqmmc regulator found
[    1.553651] mmc0: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
[    1.566775] sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed state, work on normal mode
[    1.580070] sdhci-esdhc-imx 2198000.usdhc: No vqmmc regulator found
[    1.637199] mmc1: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
[    1.645596] mmc0: new high speed SDHC card at address b368
[    1.653508] sdhci-esdhc-imx 219c000.usdhc: could not get ultra high speed state, work on normal mode
[    1.663132] sdhci-esdhc-imx 219c000.usdhc: No vqmmc regulator found
[    1.669562] mmcblk0: mmc0:b368 SD    15.0 GiB
[    1.677636]  mmcblk0: p1
[    1.694291] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    1.723644] mmc2: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA
[    1.736433] usbcore: registered new interface driver usbhid
[    1.742062] usbhid: USB HID core driver
[    1.766640] sgtl5000 0-000a: sgtl5000 revision 0x11
[    1.828794] sgtl5000 0-000a: Using internal LDO instead of VDDD
[    1.834884] mmc2: BKOPS_EN bit is not set
[    1.850755] hub 1-1:1.0: USB hub found
[    1.854959] hub 1-1:1.0: 4 ports detected
[    1.860733] mmc2: new DDR MMC card at address 0001
[    1.872124] mmcblk1: mmc2:0001 MMC04G 3.57 GiB
[    1.877266] mmcblk1boot0: mmc2:0001 MMC04G partition 1 2.00 MiB
[    1.883882] mmcblk1boot1: mmc2:0001 MMC04G partition 2 2.00 MiB
[    1.890247] mmcblk1rpmb: mmc2:0001 MMC04G partition 3 128 KiB
[    1.902208] imx-sgtl5000 sound: sgtl5000 <-> 2028000.ssi mapping ok
[    1.911984]  mmcblk1: p1 p2 p3 < p5 p6 p7 > p4
[    1.923449] mmcblk1: p4 size 5324800 extends beyond EOD, truncated
[    1.930951] TCP: cubic registered
[    1.935974] NET: Registered protocol family 10
[    1.951542] sit: IPv6 over IPv4 tunneling driver
[    1.958431] NET: Registered protocol family 17
[    1.962935] can: controller area network core (rev 20120528 abi 9)
[    1.970706] NET: Registered protocol family 29
[    1.976048] can: raw protocol (rev 20120528)
[    1.980463] can: broadcast manager protocol (rev 20120528 t)
[    1.986211] can: netlink gateway (rev 20130117) max_hops=1
[    1.992458] Key type dns_resolver registered
[    2.002979] Registering SWP/SWPB emulation handler
[    2.016177] snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:29:24 UTC (1764)
[    2.144866] fec 2188000.ethernet eth0: Freescale FEC PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=2188000.ethernet:04, irq=-1)
[    2.157271] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.153386] Waiting up to 110 more seconds for network.
[   22.153387] Waiting up to 100 more seconds for network.
[   32.153386] Waiting up to 90 more seconds for network.
[   42.153383] Waiting up to 80 more seconds for network.
[   52.153383] Waiting up to 70 more seconds for network.
[   62.153381] Waiting up to 60 more seconds for network.
[   72.153380] Waiting up to 50 more seconds for network.
[   82.153382] Waiting up to 40 more seconds for network.
[   92.153397] Waiting up to 30 more seconds for network.
[  102.153382] Waiting up to 20 more seconds for network.
[  112.153381] Waiting up to 10 more seconds for network.
[  115.973564] random: nonblocking pool is initialized
[  122.153388] Waiting up to 0 more seconds for network.
[  122.173505] Sending DHCP requests ...... timed out!
[  213.315330] IP-Config: Retrying forever (NFS root)...
[  213.405870] fec 2188000.ethernet eth0: Freescale FEC PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=2188000.ethernet:04, irq=-1)
[  213.418539] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  223.423378] Waiting up to 110 more seconds for network.
[  233.423398] Waiting up to 100 more seconds for network.
[  243.423414] Waiting up to 90 more seconds for network.
[  253.423377] Waiting up to 80 more seconds for network.
[  263.423399] Waiting up to 70 more seconds for network.
[  273.423484] Waiting up to 60 more seconds for network.
[  283.423398] Waiting up to 50 more seconds for network.
[  293.423396] Waiting up to 40 more seconds for network.
[  303.423411] Waiting up to 30 more seconds for network.
[  313.423485] Waiting up to 20 more seconds for network.
[  323.423395] Waiting up to 10 more seconds for network.
[  333.423397] Waiting up to 0 more seconds for network.
[  333.443409] Sending DHCP requests .....

Re: Re: Booting mainline kernel with mainline u-boot from SD on RIoTboard

fabio_estevam — Thu, 09 Apr 2015 19:16:39 GMT

Michael,

Your command line looks confusing:

console=ttymxc1,115200 root=/dev/nfs ip=dhcp nfsroot=:,v3,tcp rootwait root=/dev/mmcblk0p1 rootwait root=/dev/mmcblk0p1 rootwait root=/dev/mmcblk0p1

It mixes NFS boot with mmc rootfs.

You could either try a NFS boot or to store the rootfs in the sd/mmc.

Regards,

Fabio Estevam

Re: Re: Re: Booting mainline kernel with mainline u-boot from SD on RIoTboard

michaeloberle — Thu, 09 Apr 2015 19:26:55 GMT

Yes, Fabio! You are right! I figured it out as well before the post was moderated.

I had altered the bootargs incorrectly.

setenv bootargs console=ttymxc1,115200 rootwait root=/dev/mmcblk0p1

This solved the issue!