I tried to build image for imx6q-sabreauto with kernel 3.10.9-alpha.
It seem to be running into a few problems.
I am using a manifest.xml from meta-fsl-bsp-release.git - Freescale i.MX Yocto BSP Release Layer.
I got a new image without no build error. However, I met kernel panic after starting kernel.
(I have successfully run the image from kernel 3.0.35 using same microSD card.)
=====================================================================
U-Boot 2013.04 (Feb 07 2014 - 17:21:47)
CPU: Freescale i.MX6Q rev1.2 at 792 MHz
CPU: Temperature 32 C, calibration data: 0x5664b87d
Reset cause: POR
Board: MX6Q/SDL-Sabreauto revA
I2C: ready
DRAM: 2 GiB
NAND: No NAND device found!!!
0 MiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Found PFUZE100! deviceid=10,revid=11
Net: FEC [PRIME]
Warning: FEC using MAC address from net device
Hit any key to stop autoboot: 0
mmc0 is current device
reading boot.scr
** Unable to read file boot.scr **
reading uImage
5237688 bytes read in 247 ms (20.2 MiB/s)
Booting from mmc ...
reading imx6q-sabreauto.dtb
44626 bytes read in 19 ms (2.2 MiB/s)
## Booting kernel from Legacy Image at 12000000 ...
Image Name: Linux-3.10.9-1.0.0_alpha+d
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5237624 Bytes = 5 MiB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 18000000, end 1800de51
Starting kernel ...
Booting Linux on physical CPU 0x0
...............
mmc0: no vqmmc regulator found
mmc0: no vmmc regulator found
mmc0: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
ata1: SATA link down (SStatus 0 SControl 300)
mmc0: Problem setting current limit!
mmc0: new ultra high speed DDR50 SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU32G 29.7 GiB
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 0
mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
mmcblk0: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 1
mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
mmcblk0: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
mmcblk0: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 7
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0
mmcblk0: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
mmcblk0: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
mmcblk0: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
mmcblk0: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0
mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
mmcblk0: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
mmcblk0: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0
mmcblk0: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
mmcblk0: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
mmcblk0: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
mmcblk0: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0
mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: unable to read partition table
...........
...........
platform sound-fm.32: Driver imx-tuner-si476x requests probe deferral
ALSA device list:
#0: cs42888-audio
#1: imx-spdif
#2: imx-hdmi-soc
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -6
Please append a correct "root=" boot option; here are the available partitions:
b300 31166976 mmcblk0 driver: mmcblk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
.......
Seongjoon
This discussion is closed since no activity. If you still need help, please feel free to reply with an update to this discussion, or create another discussion.
Thanks,
Seongjoon
We have not got your response yet and will close the discussion in 3 days. If you still need help, please feel free to reply with an update to this discussion.
Thanks,
Yixing
Seongjoon
We are sorry for getting back to you so late. Are you still stuck with the issue? If you have somehow to resolved the issue, can we close the discussion? If you still need help, please feel free to reply with an update to this discussion.
Thanks,
Yixing