[yocto] dd to nand flash chip?

2017-08-17 Thread Riko Ho
Dear Yocto Team Members, I tried to dd *.wic to nand flash but always got kernel panic, it can not find rootfs when I dd the same file to sd card, it worked. I copy only *.wic file to usb drive n dd it. Do I need the whole directory of images for dd? or I need hddimg? Regards, Riko -- _

Re: [yocto] dd to nand flash chip?

2017-08-17 Thread Leonardo Sandoval
On Thu, 2017-08-17 at 18:37 +0800, Riko Ho wrote: > Dear Yocto Team Members, > > I tried to dd *.wic to nand flash but always got kernel panic, it can > not find rootfs > when I dd the same file to sd card, it worked. > from the bootloader command prompt, you may need to change the root kernel p

Re: [yocto] dd to nand flash chip?

2017-08-17 Thread Riko Ho
How can I edit boot loader command prompt ? On Aug 17, 2017 10:07 PM, "Leonardo Sandoval" < leonardo.sandoval.gonza...@linux.intel.com> wrote: > On Thu, 2017-08-17 at 18:37 +0800, Riko Ho wrote: > > Dear Yocto Team Members, > > > > I tried to dd *.wic to nand flash but always got kernel panic, it

Re: [yocto] dd to nand flash chip?

2017-08-17 Thread Riko
Here's the boot messages : === VFS: PARTUUID= is invalid. Expected PARTUUID=[/PARTNROFF=%d] Disabling rootwait; root= is invalid. VFS: Cannot open root device "PARTUUID=" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 0100

Re: [yocto] dd to nand flash chip?

2017-08-18 Thread Ed Bartosh
On Fri, Aug 18, 2017 at 11:40:58AM +0800, Riko wrote: > Here's the boot messages : > > === > > VFS: PARTUUID= is invalid. > Expected PARTUUID=[/PARTNROFF=%d] > Disabling rootwait; root= is invalid. > VFS: Cannot open root device "PARTUUID=" or unknown-block(0,0): error -6 Looks like you have emp

Re: [yocto] dd to nand flash chip?

2017-08-18 Thread Riko Ho
I'm confused, what is wks ? what layers do you want to know? I was bitbaking core image minimal xfce. How can I see my bootloader config? Thanks and regards, Riko On Aug 18, 2017 5:22 PM, "Ed Bartosh" wrote: > On Fri, Aug 18, 2017 at 11:40:58AM +0800, Riko wrote: > > Here's the boot messages : >

Re: [yocto] dd to nand flash chip?

2017-08-18 Thread Riko
Is it related with : https://stackoverflow.com/questions/43211384/how-to-get-to-menuconfig-for-u-boot-in-yocto-environment ? Thanks On 18/08/17 16:58, Ed Bartosh wrote: On Fri, Aug 18, 2017 at 11:40:58AM +0800, Riko wrote: Here's the boot messages : === VFS: PARTUUID= is invalid. Expected

Re: [yocto] dd to nand flash chip?

2017-08-18 Thread Riko
Is it related with linux-yocto kernel config ? Please see attachment, thanks On 18/08/17 16:58, Ed Bartosh wrote: On Fri, Aug 18, 2017 at 11:40:58AM +0800, Riko wrote: Here's the boot messages : === VFS: PARTUUID= is invalid. Expected PARTUUID=[/PARTNROFF=%d] Disabling rootwait; root= is in

Re: [yocto] dd to nand flash chip?

2017-08-18 Thread Riko
When I did fdisk -l here was what I got : Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors

Re: [yocto] dd to nand flash chip?

2017-08-21 Thread Ed Bartosh
Hi Riko, Sorry for this confusion. You can see used wks file On Fri, Aug 18, 2017 at 07:56:46PM +0800, Riko Ho wrote: > I'm confused, what is wks ? what layers do you want to know? Sorry for the confusion. You can read about wic and wks in the documentation: To understand which wks file was

Re: [yocto] dd to nand flash chip?

2017-08-21 Thread Ed Bartosh
On Sat, Aug 19, 2017 at 10:08:06AM +0800, Riko wrote: > Is it related with : > > https://stackoverflow.com/questions/43211384/how-to-get-to-menuconfig-for-u-boot-in-yocto-environment > I don't think so. It's about kernel build configuration. > ? > > Thanks > > > On 18/08/17 16:58, Ed Bartosh

Re: [yocto] dd to nand flash chip?

2017-08-21 Thread Ed Bartosh
On Sat, Aug 19, 2017 at 10:31:32AM +0800, Riko wrote: > When I did fdisk -l here was what I got : > > Disk /dev/mmcblk0: 14.6 GiB, 15640559616 bytes, 30547968 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 b