i.MX ProcessorsのトピックRe: Unable to read device tree blob

Unable to read device tree blob

aliismail — Wed, 27 Jul 2016 21:43:46 GMT

I did a core-image-minimal build for the SCM quick start board. I attempted to write the kernel, rootfs, and bootloader to an SD card using the instructions in the i.MX_Linux_User's_Guide. The bootloader seems to load fine and looks like it is able to find the kernel, however, it is not able to find the .dtb. I get the following error:

Normal Boot

Hit any key to stop autoboot: 0

switch to partitions #0, OK

mmc1 is current device

reading boot.scr

** Unable to read file boot.scr **

reading zImage

6041144 bytes read in 293 ms (19.7 MiB/s)

Booting from mmc ...

reading imx6dqscm-1gb-qwks-rev2-fix-ldo.dtb

** Unable to read file imx6dqscm-1gb-qwks-rev2-fix-ldo.dtb **

Kernel image @ 0x12000000 [ 0x000000 - 0x5c2e38 ]

No gpc device node -9, force to ldo-enable.

Is the issue that the .dtb is not in the location the bootloader is looking for?

Re: Unable to read device tree blob

igorpadykov — Sun, 31 Jul 2016 23:19:32 GMT

Hi Ali

one can try Mfg Tool (it also has core-image-minimal image)

Updates and Patches (2)

SCM-i.MX 6Dual/6Quad Manufacturing Toolkit for Linux 3.14.52 Patch Release (REV 1)

http://www.nxp.com/products/single-chip-modules/quick-start-board-for-scm-i.mx-6dq:QWKS-SCM-IMX6DQ?fpsp=1&tab=Design_Tools_Tab

please use documentation and linux L3.14.52 on

http://www.nxp.com/products/single-chip-modules/quick-start-board-for-scm-i.mx-6dq:QWKS-SCM-IMX6DQ?fpsp=1&tab=Documentation_Tab

http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/arch/arm/mach-imx?h=imx_3.14.52_1.1.0_ga

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

Re: Unable to read device tree blob

aliismail — Mon, 01 Aug 2016 22:28:55 GMT

Hi Igor,

After installing the mfg tool and modifying the scripts for the SCM board, the tool fails on the following command:

UTP: received command '$ mkfs.vfat /dev/mmcblk1p1'

UTP: executing "mkfs.vfat /dev/mmcblk1p1"

mkfs.vfat 2.11 (12 Mar 2005)

/dev/mmcblk1p1: No such file or directory

UTP: sending Non-success to kernel for command $ mkfs.vfat /dev/mmcblk1p1.

utp_poll: exit with status 256

It is trying to format a partition that was created earlier by the tool, however it looks like the OS does not recognize the partition on the SD card.

Re: Unable to read device tree blob

igorpadykov — Mon, 01 Aug 2016 23:20:44 GMT

Hi Ali

could you try fresh SD (not partitioned before), also is mfg tool working

without script modifications? As there is special mfg tool for SCM:

SCM-i.MX 6Dual/6Quad Manufacturing Toolkit for Linux 3.14.52 Patch Release:

Updates and Patches (2)

http://www.nxp.com/products/single-chip-modules/quick-start-board-for-scm-i.mx-6dq:QWKS-SCM-IMX6DQ?fpsp=1&tab=Design_Tools_Tab

Best regards

igor

Re: Unable to read device tree blob

aliismail — Mon, 01 Aug 2016 23:51:07 GMT

Yes, that is the exact tool I am using. I modified the cfg.ini as the following:

[profiles]

chip = Linux

[platform]

board = QWKS-rev2

[LIST]

name = SCM-SDCard

[variable]

initramfs = fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot

board = qwks-rev2

memsize = 1gb

mmc = 0

mem-mode = -fix-

ldo = ldo

I continue to get an error that a partition cannot be made on the SD. I have tried many SD cards and have re-formatted them. I am not sure if my cfg.ini is incorrect or the dip switches are incorrect.

Re: Unable to read device tree blob

igorpadykov — Tue, 02 Aug 2016 00:43:32 GMT

could you try *.vbs files, without any changes :

mfgtool2-yocto-mx6scm-1gb-qwks-rev1-sdcard-bottom.vbs,

mfgtool2-yocto-mx6scm-1gb-qwks-rev1-sdcard-top.vbs

~igor

Re: Unable to read device tree blob

aliismail — Tue, 02 Aug 2016 17:56:23 GMT

Hi igor,

I wiped clean my SD card and took a look at what the scripts were doing. When mmc is 2, then the image gets written and works fine. When mmc is 1, then it errors out. I think since it worked for mmc = 2, then it should be fine right? The image was written onto the SD and runs. So it looks like the *-botton.vbs script works and not the other.

Re: Unable to read device tree blob

aliismail — Tue, 02 Aug 2016 19:03:32 GMT

Also, I tried using the kernel that I built using the fml-community environment and I get "UTP: Waiting for device to appear". I am not sure if my kernel is defective or if I need to convert the binary file into something else.

Re: Unable to read device tree blob

igorpadykov — Wed, 03 Aug 2016 01:18:23 GMT

I am afraid communities releases may not work with scm,

suggest to use linux and tools from official scm product web page, links

were given on first answer.

~igor

Re: Unable to read device tree blob

aliismail — Wed, 03 Aug 2016 17:28:28 GMT

So I found an answer to my problem. An sdcard image can be generated by adding the following to the local.conf file:

IMAGE_FSTYPES="ext3 tar.bz2 sdcard"

This gave me the sdcard image I was looking for.