Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
4,050 Views

Quark_v1.2.1.1 board not bootup.

Hello everyone.

I follow the chapter 6 of X1000_BSP_BuildGuide_329687_010US.pdf .

Making the sdcard images and port on sdcard.

but board id not bootup .

it is stop after below message

[Linux-EFI, setup=0x10be, size=0x22dc30]

[Initrd, addr=0xd60c000, size=0x361ea5]

so please help to solve this ....

Thanks in indvance

0 Kudos
22 Replies
idata
Community Manager
166 Views

Hi,

 

 

In what OS did you build this image? Did the boot process hangs or was it completed? Did you updated the board's firmware? Did you see any errors while building the image?

 

 

-Sergio

 

idata
Community Manager
166 Views

1) I am using the 14.04.1-Ubuntu OS. 

2) Please check below is my log

Found layout.conf @ 0xffcff000 len 0x00000c14

# WARNING: this file is indirectly included in a Makefile where it

# defines Make targets and pre-requisites. As a consequence you MUST

# run "make clean" BEFORE making changes to it. Failure to do so may

# result in the make process being unable to clean files it no longer

# has references to.

[main]

size=8388608

type=global

[MFH]

version=0x1

flags=0x0

address=0xfff08000

type=mfh

[Flash Image Version]

type=mfh.version

meta=version

value=0x01000200

[ROM_OVERLAY]

address=0xfffe0000

item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKII_BOOTROM_OVERRIDE.Fv

type=some_type

[signed-key-module]

address=0xfffd8000

item_file=config/SvpSignedKeyModule.bin

svn_index=0

type=some_type

in_capsule=no

# On a deployed system, the SVN area holds the last known secure

# version of each signed asset.

# TODO: generate this area by collecting the SVN from the assets

# themselves.

[svn-area]

address=0xfffd0000

item_file=config/SVNArea.bin

type=some_type

# A capsule upgrade must implement some smart logic to make sure the

# highest Security Version Number always wins (rollback protection)

in_capsule=no

[fixed_recovery_image]

address=0xfff90000

item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKII_RECOVERY_IMAGE1.Fv

sign=yes

type=mfh.host_fw_stage1_signed

svn_index=2

# in_capsule=no

[NV_Storage]

address=0xfff30000

item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKII_NVRAM.bin

type=some_type

[RMU]

address=0xfff00000

item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/RMU.bin

type=none_registered

[boot_stage1_image1]

address=0xffec0000

item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKII_BOOT_STAGE1_IMAGE1.Fv

sign=yes

boot_index=0

type=mfh.host_fw_stage1_signed

svn_index=1

[boot_stage1_image2]

address=0xffe80000

item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKII_BOOT_STAGE1_IMAGE2.Fv

sign=yes

boot_index=1

type=mfh.host_fw_stage1_signed

svn_index=1

[boot_stage_2_compact]

address=0xffd00000

item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKII_BOOT_STAGE2_COMPACT.Fv

sign=yes

type=mfh.host_fw_stage2_signed

svn_index=3

[Ramdisk]

address=0xffa60000

item_file=../../meta-clanton/yocto_build/tmp/deploy/image-spi-galileo/image-spi-galileo-clanton.cpio.lzma

sign=yes

type=mfh.ramdisk_signed

svn_index=7

[LAYOUT.CONF_DUMP]

address=0xffcff000

type=mfh.build_information

meta=layout

[Kernel]

address=0xff852000

item_file=../../meta-clanton/yocto_build/tmp/deploy/image-spi-galileo/bzImage

sign=yes

type=mfh.kernel_signed

svn_index=6

[grub.conf]

address=0xff851000

item_file=grub/grub-spi.conf

sign=yes

type=mfh.bootloader_conf_signed

svn_index=5

[grub]

address=0xff800000

item_file=../../meta-clanton/yocto_build/tmp/deploy/image-spi-galileo/grub.efi

sign=yes

fvwrap=yes

guid=B43BD3E1-64D1-4744-9394-D0E1C4DE8C87

type=mfh.bootloader_signed

svn_index=4

[Linux-EFI, setup=0x10be, size=0x22dc30]

[Initrd, addr=0xd60c000, size=0x361ea5]

at here it is stop

3) No I have not update the board's firmware..

4) no there is no any error. but some warning regarding EFL..........

Please check above answer and reply as soon as fast.

Thanks in advance..

idata
Community Manager
166 Views

First, I'd recommend you to update the board's firmware. You can see instructions here https://downloadmirror.intel.com/24748/eng/IntelGalileoFirmwareUpdaterUserGuide-1.0.4.pdf https://downloadmirror.intel.com/24748/eng/IntelGalileoFirmwareUpdaterUserGuide-1.0.4.pdf .

 

 

Can you list all the steps you followed to build this image?

 

 

-Sergio

 

idata
Community Manager
166 Views

I follow below command to make the images.

# tar -xvf meta-clanton_v1.2.1.1.tar.gz

# cd meta-clanton_v1.2.1.1

# ./setup.sh

# source ./oe-init-build-env yocto_build

# bitbake image-full

from above command there wil creat the blow images in tmp/deploy/images/quark directory.

file Names SIZEbzImage--3.14-r0-quark-20160726103211.bin 2.3 MBboot/grub/grub.conf 946 bytescore-image-minimal-initramfs-quark-20160726103211.rootfs.cpio.gz 3.5 MBimage-full-quark-20160726124629.rootfs.ext3 314.6 MB

i rename the above file as below

bzImage

boot/grub/grub.conf

core-image-minimal-initramfs-quark.cpio.gz

image-full-quark.ext3

and put these all 4 files in sdcard.

also note that my current board version is 1.0.2

please tell me it is must require to change the firmware 1.0.2 to 1.0.4?

ans please tell me why?

thanks in advance

Padraig_C_Intel
Employee
166 Views

Hi Nikunj_Patel,

I have two questions for you:

1. Do you have access to a Debian distro?

2. Are you working behind any proxy?

idata
Community Manager
166 Views

Hello;

1) I have no access to a Debian distro?

2) No I have direct use of internet.

Thanks in advance.

idata
Community Manager
166 Views

It's recommended you update your board's firmware version. You can see instructions here https://downloadcenter.intel.com/download/24748/Intel-Galileo-Firmware-Updater-and-Drivers-1-0-4 https://downloadcenter.intel.com/download/24748/Intel-Galileo-Firmware-Updater-and-Drivers-1-0-4 .

 

 

Additionally, there's a thread with a very similar issue to yours. You can see it here /thread/100732 https://communities.intel.com/thread/100732 . The user managed to build the Quark BSP 1.2.1.1. Check the suggestions and let us know your results.

 

 

-Sergio

 

idata
Community Manager
166 Views

Do you still need help with this thread, were you able to build the BSP?

 

 

-Sergio

 

idata
Community Manager
166 Views

Upon reviewing the Quark BSP I noticed that you need to do some changes to the names of the files in /tmp/deploy/images/quark/.

 

You renamed some of these files but I wanted to check if you still kept the proper extensions such as in bzImage.bin. The file names should look like this:

 

image-full-quark.ext3

 

core-image-minimal-initramfs-quark.cpio.gz

 

bzImage.bin

 

grub.efi (This file was not in the files you mention after renaming)

 

boot (directory)

Can you attach a picture of the contents of the SD card?

-Sergio

idata
Community Manager
93 Views

Hi Nikunj,

 

 

Do you still need assistance with this thread? What was the result of following @Padraigc's suggestion? If you still need assistance, please answer our questions from our latest reply /message/415517# 415517 https://communities.intel.com/message/415517# 415517 .

 

 

We'll be waiting for your response.

 

 

-Sergio

 

idata
Community Manager
166 Views

Hello;

I have update the firmware from 1.0.2 to 1.1.0.

but still problem is not solve.

when I run the bit-bake image-full command there is some warning as below.

nikunj.patel.369@slade001:~/workspace/1.2.1/build$ bitbake image-full

Loading cache: 100% |# | ETA: 00:00:00

Loaded 5 entries from dependency cache.

Parsing recipes: 100% |# | Time: 00:00:22

Parsing of 906 .bb files complete (2 cached, 904 parsed). 2209 targets, 182 skipped, 0 masked, 0 errors.

NOTE: Resolving any missing task queue dependencies

Build Configuration:

BB_VERSION = "1.24.0"

BUILD_SYS = "x86_64-linux"

NATIVELSBSTRING = "Ubuntu-14.04"

TARGET_SYS = "i586-poky-linux"

MACHINE = "quark"

DISTRO = "iot-devkit"

DISTRO_VERSION = "1.5"

TUNE_FEATURES = "m32 i586"

TARGET_FPU = ""

meta

meta-yocto

meta-intel-iot-devkit

meta-intel-iot-middleware

meta-intel-quark

meta-intel-galileo

meta-netcontiki

meta-networking = "master:6c4237fcb4dec474f6275c36a85012fa8e2fa10f"

NOTE: Preparing runqueue

NOTE: Executing SetScene Tasks

NOTE: Executing RunQueue Tasks

WARNING: radvd: No generic license file exists for: radvd in any provider

NOTE: validating kernel config, see log.do_kernel_configcheck for details

WARNING: QA Issue: ELF binary '/home/nikunj.patel.369/workspace/1.2.1/build/tmp/work/i586-poky-linux/systemd/1_216+gitAUTOINC+5d0ae62c66-r0/packages-split/udev/bin/udevadm' has relocations in .text [textrel]

WARNING: QA Issue: ELF binary '/home/nikunj.patel.369/workspace/1.2.1/build/tmp/work/i586-poky-linux/systemd/1_216+gitAUTOINC+5d0ae62c66-r0/packages-split/systemd-vconsole-setup/lib/systemd/systemd-vconsole-setup' has relocations in .text [textrel]

WARNING: QA Issue: ELF binary '/home/nikunj.patel.369/workspace/1.2.1/build/tmp/work/i586-poky-linux/systemd/1_216+gitAUTOINC+5d0ae62c66-r0/packages-split/systemd-analyze/usr/bin/systemd-analyze' has relocations in .text [textrel]

WARNING: QA Issue: ELF binary '/home/nikunj.patel.369/workspace/1.2.1/build/tmp/work/i586-poky-linux/systemd/1_216+gitAUTOINC+5d0ae62c66-r0/packages-split/systemd-binfmt/lib/systemd/systemd-binfmt' has relocations in .text [textrel]

WARNING: QA Issue: ELF binary '/home/nikunj.patel.369/workspace/1.2.1/build/tmp/work/i586-poky-linux/systemd/1_216+gitAUTOINC+5d0ae62c66-r0/packages-split/systemd-ptest/usr/lib/systemd/ptest/test-udev' has relocations in .text [textrel]

WARNING: QA Issue: ELF binary '/home/nikunj.patel.369/workspace/1.2.1/build/tmp/work/i586-poky-linux/systemd/1_216+gitAUTOINC+5d0ae62c66-r0/packages-split/systemd/bin/systemd-sysusers' has relocations in .text [textrel]

WARNING: The postinstall intercept hook 'update_icon_cache' failed (exit code: 127)! See log for details!

WARNING: The postinstall intercept hook 'update_pixbuf_cache' failed (exit code: 2)! See log for details!

WARNING: The postinstall intercept hook 'update_icon_cache' failed (exit code: 127)! See log for details!

WARNING: The postinstall intercept hook 'update_pixbuf_cache' failed (exit code: 2)! See log for details!

NOTE: Tasks Summary: Attempted 3054 tasks of which 19 didn't need to be rerun and all succeeded.

Please help me to solve the problem.

Thanks in advance

idata
Community Manager
166 Views

According to the output you posted you don't have any errors, just warning messages. The tasks summary says all tasks succeeded. Are you able to boot the image after running bitbake?

 

The warning messages mention a cache fail and a suggestion to check log for details. What are the contents of this log?

 

 

-Sergio

 

idata
Community Manager
166 Views

Thanks for answer

I am not able to boot the image after running bitbake.

Please help to solve the problem.

Thanks in advance.

idata
Community Manager
166 Views

Pleae check out both images.

I have try with both these options.

but still board not bootup.

Thanks in advance.

idata
Community Manager
166 Views

Did you do any modifications or performed additional steps to what's in the guide? If you did, name those modifications.

 

 

Also, take a look at this note on the BSP and make sure you're avoiding cross-pollution: Remove all previous versions of the software before installing the current version. Individual components require very different environments (compiler options and others). To avoid cross-pollution, the commands in each section that follows must be run in a new command line window every time.

 

 

At the beginning of section 6, the dependencies are listed, how did you install these dependencies? Did you receive any errors?

 

 

-Sergio

 

Padraig_C_Intel
Employee
166 Views

Hi Nikunj_Patel,

What type of filesystem are you using on the SD card? (i.e. is it FAT32?)

Padraig

idata
Community Manager
166 Views

Yes I am using the FAT32 file system on sdcard.

I also note down that the 1.1.0 version is runs fine on my board.

Thanks in advance.

Padraig_C_Intel
Employee
166 Views

Hi Nikunj_Patel,

Ok, that's what you need, after messing around a bit I can get these warnings:

WARNING: The postinstall intercept hook 'update_pixbuf_cache' failed (exit code: 2)! See log for details!

WARNING:The postinstall intercept hook 'update_icon_cache' failed (exit code: 127)! See log for details!

WARNING:The postinstall intercept hook 'update_pixbuf_cache' failed (exit code: 2)! See log for details!

WARNING:The postinstall intercept hook 'update_icon_cache' failed (exit code: 127)! See log for details!

And the image still runs, which points towards the other warning messeges you received to be what's causing your problem.

Can you please check what version of gcc you have?

Thanks,

Padraig

idata
Community Manager
166 Views

Hello

Thanks for your reply.

i use the SDK 1.2.1.

i had not any change in sdk. so the default sdk is run from sdk 1.2.1

Thanks in advance.

Padraig_C_Intel
Employee
166 Views

Hi Nikunj_Patel,

Ok perfect, could you also try and type this into the command line:

gcc --version

Thanks,

Padraig

Reply