Re: [OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

2017-04-05 Thread Leonardo Sandoval 
wrong list, you may have better luck at the meta-fsl mailing list.

BTW, the kernel expects a filesystem on a partition and the latter must
be defined in the kernel command line, using the root parameter.






On Wed, 2017-04-05 at 09:25 +, Zheng, Ruoqin wrote:
> 32be_rootfs boot from sdcard (ls1046)
> 
>  
> 
> I used source code provided by nxp  QorIQ-Linux-SDK-v2.0-SOURCE.iso +
> SDK-V2.0-1701 to build the kernel and rootfs , then it can’t boot from
> sdcard.
> 
>  
> 
> I tried to put kernel(32be) and rootfs(32be) in SD card , and boot it
> follow the SDK2.0, it was fail to mount the rootfs(while 64be kernel
> is normal),and here is part of log:
> 
> mmcblk0: mmc0:0007 SL32G 29.0 GiB
> 
>  mcblk0: p1
> 
> VFS: Mounted root (ext2 filesystem) on device 1:0.
> 
> VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error
> -6
> 
> Please append a correct "root=" boot option; here are the available
> partitions:
> 
> 0100  262144 ram0  (driver?)
> 
> 0101  262144 ram1  (driver?)
> 
> 0102  262144 ram2  (driver?)
> 
> 0103  262144 ram3  (driver?)
> 
> 0104  262144 ram4  (driver?)
> 
> 0105  262144 ram5  (driver?)
> 
> 0106  262144 ram6  (driver?)
> 
> 0107  262144 ram7  (driver?)
> 
> 1f00  524288 mtdblock0  (driver?)
> 
> b30030375936 mmcblk0  driver: mmcblk
> 
>   b30130371936 mmcblk0p1 -01
> 
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> 
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2
> 
> Hardware name: Freescale LAYERSCAPE
> 
>  
> 
> The entire log is in atachments, do anyone have any idea about this
> problem? 
> 
>  
> 
> By the way, I tried to boot the kernel with command “bootm
> a000:kernel@1 - a000:fdt@1”
> 
> And the log show as below, you can see that mmcblk0 device is missed,
> do anyone know the reason?
> 
>  
> 
> ALSA device list:
> 
>   No soundcards found.
> 
> VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error
> -6
> 
> Please append a correct "root=" boot option; here are the available
> partitions:
> 
> 0100  262144 ram0  (driver?)
> 
> 0101  262144 ram1  (driver?)
> 
> 0102  262144 ram2  (driver?)
> 
> 0103  262144 ram3  (driver?)
> 
> 0104  262144 ram4  (driver?)
> 
> 0105  262144 ram5  (driver?)
> 
> 0106  262144 ram6  (driver?)
> 
> 0107  262144 ram7  (driver?)
> 
> 1f00  524288 mtdblock0  (driver?)
> 
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> 
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2
> 
> Hardware name: Freescale LAYERSCAPE
> 
>  
> 
>  
> 
> Zheng Ruoqin
> 
> Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
> 
> ADDR.: No.6 Wenzhu Road, Software Avenue,
> 
>Nanjing, 210012, China
> 
> MAIL : zhengrq.f...@cn.fujistu.com
> 
>  
> 
> 
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

2017-04-05 Thread Zheng, Ruoqin 
32be_rootfs boot from sdcard (ls1046)

I used source code provided by nxp  QorIQ-Linux-SDK-v2.0-SOURCE.iso + 
SDK-V2.0-1701 to build the kernel and rootfs , then it can’t boot from sdcard.



I tried to put kernel(32be) and rootfs(32be) in SD card , and boot it follow 
the SDK2.0, it was fail to mount the rootfs(while 64be kernel is normal),and 
here is part of log:

mmcblk0: mmc0:0007 SL32G 29.0 GiB

 mcblk0: p1

VFS: Mounted root (ext2 filesystem) on device 1:0.

VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:

0100  262144 ram0  (driver?)

0101  262144 ram1  (driver?)

0102  262144 ram2  (driver?)

0103  262144 ram3  (driver?)

0104  262144 ram4  (driver?)

0105  262144 ram5  (driver?)

0106  262144 ram6  (driver?)

0107  262144 ram7  (driver?)

1f00  524288 mtdblock0  (driver?)

b30030375936 mmcblk0  driver: mmcblk

  b30130371936 mmcblk0p1 -01

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

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2

Hardware name: Freescale LAYERSCAPE



The entire log is in atachments, do anyone have any idea about this problem?



By the way, I tried to boot the kernel with command “bootm a000:kernel@1 - 
a000:fdt@1”

And the log show as below, you can see that mmcblk0 device is missed, do anyone 
know the reason?



ALSA device list:

  No soundcards found.

VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:

0100  262144 ram0  (driver?)

0101  262144 ram1  (driver?)

0102  262144 ram2  (driver?)

0103  262144 ram3  (driver?)

0104  262144 ram4  (driver?)

0105  262144 ram5  (driver?)

0106  262144 ram6  (driver?)

0107  262144 ram7  (driver?)

1f00  524288 mtdblock0  (driver?)

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

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2

Hardware name: Freescale LAYERSCAPE


Zheng Ruoqin
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
   Nanjing, 210012, China
MAIL : zhengrq.f...@cn.fujistu.com



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

2017-04-05 Thread Zheng, Ruoqin 
32be_rootfs boot from sdcard (ls1046)



I tried to put kernel and rootfs in SD card , and boot it follow the SDK 
note(ls1046), it was fail to mount the rootfs(while 64be kernel is good),and 
here is part of log:

mmcblk0: mmc0:0007 SL32G 29.0 GiB

 mcblk0: p1

VFS: Mounted root (ext2 filesystem) on device 1:0.

VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:

0100  262144 ram0  (driver?)

0101  262144 ram1  (driver?)

0102  262144 ram2  (driver?)

0103  262144 ram3  (driver?)

0104  262144 ram4  (driver?)

0105  262144 ram5  (driver?)

0106  262144 ram6  (driver?)

0107  262144 ram7  (driver?)

1f00  524288 mtdblock0  (driver?)

b30030375936 mmcblk0  driver: mmcblk

  b30130371936 mmcblk0p1 -01

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

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2

Hardware name: Freescale LAYERSCAPE



The entire log is in atachments, do anyone have any idea about this problem?



By the way, I tried to boot the kernel with command “bootm a000:kernel@1 - 
a000:fdt@1”

And the log show as below, you can see that mmcblk0 device is missed, do anyone 
know the reason?



ALSA device list:

  No soundcards found.

VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:

0100  262144 ram0  (driver?)

0101  262144 ram1  (driver?)

0102  262144 ram2  (driver?)

0103  262144 ram3  (driver?)

0104  262144 ram4  (driver?)

0105  262144 ram5  (driver?)

0106  262144 ram6  (driver?)

0107  262144 ram7  (driver?)

1f00  524288 mtdblock0  (driver?)

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

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2

Hardware name: Freescale LAYERSCAPE


Zheng Ruoqin
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
   Nanjing, 210012, China
MAIL : zhengrq.f...@cn.fujistu.com



=> setenv bootcmd "ext2load mmc 0 a000 kernel.itb && bootm a000"
=> setenv bootargs "root=/dev/mmcblk0p1 rw earlycon=uart8250,0x21c0500 
console=ttyS0,115200"
=> boot  
67991979 bytes read in 5829 ms (11.1 MiB/s)
## Loading kernel from FIT Image at a000 ...
   Using 'config@1' configuration
   Trying 'kernel@1' kernel subimage
 Description:  ARM32 Linux kernel
 Type: Kernel Image
 Compression:  uncompressed
 Data Start:   0xa0e0
 Data Size:4468048 Bytes = 4.3 MiB
 Architecture: ARM
 OS:   Linux
 Load Address: 0x80008000
 Entry Point:  0x80008000
   Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at a000 ...
   Using 'config@1' configuration
   Trying 'ramdisk@1' ramdisk subimage
 Description:  LS1046 Ramdisk
 Type: RAMDisk Image
 Compression:  uncompressed
 Data Start:   0xa0448e1c
 Data Size:63498311 Bytes = 60.6 MiB
 Architecture: ARM
 OS:   Linux
 Load Address: unavailable
 Entry Point:  unavailable
   Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at a000 ...
   Using 'config@1' configuration
   Trying 'fdt@1' fdt subimage
 Description:  Flattened Device Tree blob
 Type: Flat Device Tree
 Compression:  uncompressed
 Data Start:   0xa0442ee0
 Data Size:24245 Bytes = 23.7 KiB
 Architecture: ARM
   Verifying Hash Integrity ... OK
   Loading fdt from 0xa0442ee0 to 0x9000
   Booting using the fdt blob at 0x9000
   Loading Kernel Image ... OK
   Using Device Tree in place at 9000, end 90018eb4

Starting kernel ...

Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Linux version 4.1.30-rt34+ (zhengrq@okura) (gcc version 5.2.0 (GCC) ) #2 SMP 
Fri Mar 31 11:04:46 JST 2017
CPU: ARMv7 Processor [410fd082] revision 2 (ARMv7), cr=32c5383d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine model: LS1046A RDB Board
earlycon: Early serial console at MMIO 0x21c0500 (options '')
earlycon: earlycon_map: Couldn't map 0x21c0500
Malformed early option 'earlycon'
Reserved memory: initialized node bman-fbpr, compatible id fsl,bman-fbpr
Reserved memory: initialized node qman-fqd, compatible id fsl,qman-fqd
Reserved memory: initialized node qman-pfdr, compatible id fsl,qman-pfdr
cma: Reserved 16 MiB at 0x0009fb00
Forcing write-allocate cache policy for SMP
Memory policy: Data cache writealloc
PERCPU: Embedded 12 pages/cpu @dc7a s18688 r8192 d22272 u49152
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 2093072
Kernel command line: root=/dev/mmcblk0p1 rw earlycon=uart8250,0x21c0500 
console=ttyS0,115200